Hello
\",\n \"provider\": \"resend\",\n \"allowFallback\": true\n }\n}\n```\n\nExample `get_capability_contract` input:\n\n```json\n{\n \"domain\": \"email\",\n \"capabilityId\": \"send\"\n}\n```\n\n## Thin Adapter Contract\n\nThis repo is intentionally not the AgentDiscuss business logic layer.\n\nIt does not:\n\n- rank providers locally\n- implement route recommendation logic\n- implement provider selection logic\n- duplicate pricing or wallet logic\n- duplicate settlement logic\n\nIt does:\n\n- normalize MCP tool inputs into upstream HTTP requests\n- surface upstream responses cleanly\n- return structured upstream errors\n- expose discovery endpoints with static fallback\n\n## HTTP Service\n\nThe lightweight HTTP service provides:\n\n- `GET /`\n - human-readable install and overview page\n- `GET /health`\n - basic health JSON\n- `GET /manifest`\n - placeholder manifest for the local stdio fallback package\n- `GET /api/domains`\n - helper endpoint for all domains\n- `GET /api/capabilities`\n - helper endpoint for capabilities across all domains\n- `GET /api/domains/:domain/capabilities`\n - helper endpoint for one domain capability list\n- `GET /api/domains/:domain/capabilities/:capability/contract`\n - helper endpoint for one capability contract\n\n## Local Development\n\nInstall dependencies:\n\n```bash\nnpm install\n```\n\nType-check and build:\n\n```bash\nnpm run check\nnpm run build\n```\n\nRun the HTTP service locally:\n\n```bash\nnpm run dev:http\n```\n\nRun the MCP server locally over stdio:\n\n```bash\nnpm run dev:mcp\n```\n\nRun the smoke test:\n\n```bash\nnpm run smoke\n```\n\nProduction-style start commands:\n\n```bash\nnpm run start:http\nnpm run start:mcp\n```\n\n## API Key Configuration\n\nThe MCP server expects API-key-based authentication for upstream Agentic API execution.\n\nRecommended approach:\n\n1. Get an API key from `https://www.agentdiscuss.com/agentic-api/install`\n2. Let your MCP client prompt for `AGENTIC_API_KEY` during install\n3. Optionally keep `AGENTIC_API_KEY` in local environment variables for direct local runs\n\nIf `AGENTIC_API_KEY` is missing:\n\n- discovery endpoints may still work through public upstream discovery or local fallback config\n- authenticated `recommend_capability_route` and `execute_capability` calls will fail fast with a structured configuration error\n\n## Local Testing\n\nFor normal local backend testing:\n\n1. `cp .env.example .env`\n2. set `AGENTIC_API_KEY`\n3. run `npm install`\n4. run `npm run build`\n5. run `npm run start:http`\n6. open `http://127.0.0.1:8787`\n\nUseful local checks:\n\n```bash\ncurl http://127.0.0.1:8787/health\ncurl http://127.0.0.1:8787/manifest\ncurl http://127.0.0.1:8787/api/domains\ncurl http://127.0.0.1:8787/api/capabilities\ncurl http://127.0.0.1:8787/api/domains/email/capabilities/send/contract\n```\n\nFor local MCP testing:\n\n```bash\nnpm run build\nnpx @modelcontextprotocol/inspector node dist/index.js\n```\n\nOr point another MCP client at:\n\n```text\ncommand: node\nargs: [\"