For developers and AI agents
Connect your agent to Complete AI Business
What a person can do on this site, an agent can do for them: read the offer and the case studies, make a free AI plan, and, once the person allows it, read their own plans. No API key needed for the public parts.
MCP server
Streamable HTTP with JSON responses. Public tools need no token.
https://completeaibusiness.com/mcp
A2A agent
JSON-RPC message/send, protocol 0.3. Deterministic answers, no open-ended chat.
https://completeaibusiness.com/a2a
OAuth 2.1
For a customer's own plans. PKCE, dynamic client registration, sign-in with an emailed code.
In the browser
Every page registers WebMCP tools for an agent running in the visitor's browser: the offer, the case studies, the questionnaire, and the plan the visitor has open.
Pages as Markdown
Send Accept: text/markdown to any public page and get Markdown at the same URL. There's also an index for language models.
MCP tools
| Tool | What it does | Needs |
|---|---|---|
get_offer | Prices, what's included, the 7 days, how to start, the FAQ | nothing |
list_case_studies, get_case_study | The 9 case studies (fictive examples) | nothing |
create_free_plan | Makes a free AI plan for the person you act for, from the questionnaire's questions. Ready in 1 to 3 minutes and emailed to them. | nothing |
get_plan_status | One plan by its id: still being written, or ready with the plan | the plan's id |
my_plans, get_my_plan | The signed-in customer's own plans | OAuth, plans:read |
request_start | Asks us to start the initial call ($770) or the 7 days ($7,700). Records the request and emails the customer and our team. Nothing is charged. | OAuth, plans:start |
Try it with curl:
curl -s https://completeaibusiness.com/mcp \
-H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_offer","arguments":{}}}'
Or with the MCP Inspector: npx @modelcontextprotocol/inspector, transport Streamable HTTP, URL https://completeaibusiness.com/mcp.
A customer's own plans: OAuth
- Register a client at
POST /oauth/register(RFC 7591). No key needed. - Send the customer to
/oauth/authorizewith PKCE (S256). They type the email address they used for their plan, enter the 6-digit code we email them, and choose Allow or Don't allow. - Exchange the code at
POST /oauth/token. Access tokens last an hour; refresh tokens 30 days and rotate on every use. - Send
Authorization: Bearer ...to/mcp,/a2aor/api/v1/me/.... Without it, you get a 401 that points at the protected resource metadata.
A token reaches only the plans made for that email address. Never ask the customer for the code: they type it on our page. The full guide is auth.md.
What stays private
- A plan belongs to the person who asked for it. It is never listed, indexed or put in llms.txt, and its page has no Markdown version. Reading it takes its id, or the owner's token.
- Nothing here reaches anyone's email address or phone number, our team's inboxes, the phone agent, or the work we do for paying customers.
- Making plans is limited per address, per email and per day, so please don't loop.
Discovery documents
- /.well-known/api-catalog (RFC 9727) and /openapi.json
- /.well-known/mcp/server-card.json and /.well-known/agent-card.json
- /.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource (RFC 9728)
- /.well-known/agent-skills/index.json, with one skill: SKILL.md
- /.well-known/ai-catalog.json and robots.txt (with Content Signals)
- /.well-known/http-message-signatures-directory: the key our website reader signs its requests with
Questions or a problem with the API: contact@completeaitraining.com.