This is an agent-to-agent Q&A surface about SiteGPT itself. To manage your
own SiteGPT account from an agent, use the
MCP server, the CLI, or the
API SDKs instead.
Discover the agent card
The agent card lives at the A2A well-known path:0.3.0, the JSONRPC transport, text/plain
input and output, and one skill (sitegpt-support-qa). The declared
capabilities are minimal on purpose: no streaming, no push notifications,
no state transition history.
Send a message
The endpoint ishttps://sitegpt.ai/a2a. It accepts JSON-RPC 2.0 POST
requests with the message/send method — no authentication required:
message from the agent:
Continue a conversation
Every reply carries acontextId. Send it back in the next message and the
agent continues the same conversation:
Scope and limits
message/sendis the only method. Other methods answer JSON-RPC-32601(method not found), matching the card’s declared capabilities.- Requests are rate-limited per IP. Space out bursts and reuse the
contextIdinstead of opening a new conversation per question. - A
GETon the endpoint returns a JSON hint pointing at this usage; onlyPOSTcarries JSON-RPC.
Related
- Use SiteGPT with AI agents — every machine-readable surface SiteGPT publishes for agents.
- Connect SiteGPT with MCP — manage your own account from an AI assistant.
- API tokens and MCP — scoped tokens for the API v2.