> For the complete documentation index, see [llms.txt](https://agentbadge.gitbook.io/agentbadge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agentbadge.gitbook.io/agentbadge-docs/documentation/engineering-capabilities.md). # Engineering Capabilities AgentBadge is an agency for the agentic web. We help businesses become agent-ready through consulting and development services across 8 practice areas. Each service has a clear problem statement, deliverables, and engagement model. You can engage with us in three ways: 1. **Contact form** — Fill out the form at [agentbadge.xyz/contact](https://agentbadge.xyz/contact) (Discord or Telegram). 2. **Work Request API** — Submit a structured `POST /api/work-requests` request (see examples below). 3. **Demand Registry** — Register interest in a capability via `POST /api/demand/request`. *** ## GEO Consulting **Problem:** Need your content discoverable by AI search engines and AI agents. **Keywords:** SEO, GEO, Generative Engine Optimization, Search Engine Optimization, llms.txt, AI Sitemap, Structured Data, JSON-LD, Agent-Readable, Discoverable, AEO, Answer Engine Optimization, WordPress, HTML, CSS. **Deliverables:** * GEO audit * llms.txt setup * AI sitemap * Agent knowledge layer * Content architecture recommendations **Engagement:** Fixed-scope, contract. *** ## AI Agent Consulting **Problem:** Need architecture guidance for making your product agent-ready. **Keywords:** AI Agent, Agent Architecture, Agent-Ready, Agent-Readable, MCP, Model Context Protocol, Agent API, Agentic Web, llms.txt, Agent Card, Agent Economy, Agent-to-Agent, A2A, Agent Commerce, Autonomous Agents, Agent Payments, x402, Machine Payments, Agent Marketplace, Agent Harness, Agent Orchestration, Agent Infrastructure, Agent Framework, Agent Tooling, Agent Deployment, Agent Observability. **Deliverables:** * Architecture assessment * Agent-readable API design * Knowledge layer setup * Implementation roadmap **Engagement:** Fixed-scope, contract, part-time. *** ## Backend Infrastructure **Problem:** Need backend systems, databases, or event-driven architecture. **Keywords:** Backend, Node.js, NestJS, PostgreSQL, Redis, REST API, Event-Driven, Microservices, Database, Server, React, Vue.js, HTML, CSS, Laravel, PHP, MySQL, MongoDB, Docker, GraphQL. **Deliverables:** * Backend services * Database schema * API endpoints * Documentation * Tests **Engagement:** Fixed-scope, contract, part-time. *** ## API Development **Problem:** Need a REST API or backend service for your product. **Keywords:** API, REST API, OpenAPI, Backend, Endpoints, Web Service, API Design, API Documentation, Hono, Express, React, Angular, HTMX, GraphQL, TypeScript, JavaScript, Blockchain API, Payment API, Web3 API. **Deliverables:** * API server * OpenAPI specification * Documentation * Tests **Engagement:** Fixed-scope, contract, part-time. *** ## Blockchain Infrastructure **Problem:** Need blockchain integration, wallet setup, or tokenization infrastructure. **Keywords:** Blockchain, Hedera, Ethereum, Solana, Base, Bitcoin, Lightning Network, Wallet, Tokenization, Web3, Smart Contracts, DeFi, HTS, HCS, EVM, Crypto Payments, Micropayments, Payment Systems, Payment Infrastructure, Payment Processing, x402, Machine Payments, Agent Economy, Agent Commerce, Agent Payments, Agent Harness, Agent Orchestration, Agent Infrastructure, NFT, Fungible Token, On-Chain Payments, Decentralized Finance, Multi-Chain, Cross-Chain. **Deliverables:** * Integration code * Wallet setup * Token configuration * Documentation **Engagement:** Fixed-scope, contract. *** ## Smart Contract Development **Problem:** Need Solidity or Hedera smart contracts for tokenization, DeFi, or on-chain logic. **Keywords:** Smart Contracts, Solidity, Hedera, Solana, Base, Bitcoin, Bitcoin Scripts, Tokenization, DeFi, On-Chain, EVM, HTS, NFT, Fungible Token, Multi-Chain Contracts, Cross-Chain Logic. **Deliverables:** * Smart contracts * Deployment scripts * Tests * Documentation **Engagement:** Fixed-scope, contract. *** ## MCP Server Development **Problem:** Need an MCP server for your AI agent to access existing APIs. **Keywords:** MCP, Model Context Protocol, MCP Server, AI Agent, Agent Tools, Tool Integration, Agent-to-API, Claude, Cursor, Windsurf. **Deliverables:** * MCP server * Tool definitions * Configuration * Documentation * Tests **Engagement:** Fixed-scope, contract, part-time. *** ## Web Development & Design **Problem:** Need a website built, redesigned, or fixed — frontend, UI, UX, or design work. **Keywords:** React, Angular, Vue.js, WordPress, HTML, HTMX, CSS, Tailwind, Design, UI, UX, Frontend, Website, Landing Page, Web Design, Responsive, Accessibility, Figma, Laravel, Next.js, Nuxt.js, Svelte, SvelteKit, JavaScript, TypeScript, PHP, Bootstrap, Sass, SCSS. **Deliverables:** * Website or web app * Responsive design * UI/UX improvements * Design system * Documentation **Engagement:** Fixed-scope, contract, part-time. *** ## How to Engage There are three ways to start working with us. Choose the one that fits your workflow. ### Option 1: Contact Form (Human-Friendly) Visit [agentbadge.xyz/contact](https://agentbadge.xyz/contact) and fill out the form: 1. **Select a channel** — Discord or Telegram. 2. **Write your message** — Describe what you need (up to 4096 characters). 3. **Add contact info** — Your Telegram/Discord nickname or email (optional). 4. **Attach a file** — Optional, max 1 MB. 5. **Send** — The message is delivered to our team instantly. The form uses HTMX for async submission. You can also submit via JSON API: ```json POST /contact Content-Type: application/json { "channel": "discord", "message": "We need an MCP server for our internal API.", "contactInfo": "@yourname" } ``` **Response (200):** ```json { "success": true, "channel": "discord" } ``` **Rate limit:** 1 request per minute per IP. ### Option 2: Work Request API (Structured) Submit a structured work request with title, summary, and optional requirements. Ideal for programmatic submissions and AI agents. **Example: Submit a work request** ```json POST /api/work-requests Content-Type: application/json { "request": { "title": "MCP Server for Internal API", "summary": "We need an MCP server that wraps our REST API for use with Claude and Cursor. The API has 12 endpoints across 3 services.", "requirements": [ "TypeScript", "Model Context Protocol", "OpenAPI 3.1 spec provided" ] }, "preferred_contact": { "channel": "discord" } } ``` **Response (202 Accepted):** ```json { "request_id": "wr_abc123def456", "status_url": "/api/work-requests/wr_abc123def456" } ``` **Check status:** ```json GET /api/work-requests/wr_abc123def456 // 200 { "id": "wr_abc123def456", "status": "pending", "title": "MCP Server for Internal API", "summary": "We need an MCP server...", "requirements": ["TypeScript", "Model Context Protocol", "OpenAPI 3.1 spec provided"], "preferred_contact": { "channel": "discord" }, "created_at": "2026-08-12T18:00:00Z" } ``` **Validation rules:** * `title` — required, max 200 characters. * `summary` — required, max 5000 characters. * `requirements` — optional, max 20 items. * Secrets, API keys, passwords, and HTML/JS content are automatically rejected. **Rate limit:** 5 POST requests per hour per IP. 100 GET requests per minute per IP. **Human review:** Each request is reviewed by a human at `/work-requests/:id` with three outcomes: * **Accept** — We start the engagement. * **Ask** — We request more details. * **Decline** — We decline with explanation. ### Option 3: Demand Registry (Capability Interest) Register demand for a capability you need. This is lighter than a work request — it signals interest without committing to a project. ```json POST /api/demand/request Content-Type: application/json { "capability_query": "MCP Server Development", "context": "Need MCP server for 12-endpoint REST API" } ``` **Response (202 Accepted):** ```json { "demand_id": "dm_xyz789", "capability_query": "MCP Server Development", "count": 1, "priority": "normal", "status": "accepted" } ``` **Validation rules:** * `capability_query` — required, max 200 characters. * `context` — optional, max 1000 characters. **Rate limit:** 10 requests per hour per IP. ### Engagement Models | Model | Description | Best For | | --------------- | --------------------------------------------- | ------------------------------------- | | **Fixed-scope** | Defined deliverables, milestone-based payment | Clear requirements, one-time projects | | **Contract** | Weekly demos, ongoing collaboration | Multi-week projects, evolving scope | | **Part-time** | Flexible hours, async communication | Ongoing support, maintenance | *** ## Capability Endpoints | Endpoint | Description | | ------------------------------------- | --------------------------------- | | `/agency.json` | Agency capability registry (JSON) | | `/agent-guide/team` | Team overview | | `/agent-guide/team/capabilities` | Capabilities (Markdown) | | `/agent-guide/team/capabilities.json` | Capabilities (JSON) | | `/agent-guide/team/services` | Services catalog (Markdown) | | `/agent-guide/team/availability` | Availability | | `/agent-guide/team/contact` | Contact channels | | `/agent-guide/team/match` | Matching criteria | | `/services` | Human-readable services catalog | | `/agents.txt` | Agent access policy | ## Demand & Work Requests | Endpoint | Description | | --------------------------------- | ------------------------------------------------------- | | `POST /api/work-requests` | Submit a work request (202 + request\_id + status\_url) | | `GET /api/work-requests/:id` | Check work request status | | `GET /work-requests/:id` | Human review UI (Accept / Ask / Decline) | | `POST /api/demand/request` | Register demand for a capability (202 + demand\_id) | | `/agent-guide/demand` | Demand Registry API docs (Markdown) | | `/agent-guide/demand/schema.json` | Demand request JSON schema | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://agentbadge.gitbook.io/agentbadge-docs/documentation/engineering-capabilities.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.