Skip to main content
Every agent you define is served at its own route prefix. Clients use JSON-RPC over POST, in the A2A (Agent2Agent) style: agent card, messages, tasks, and optional streaming. That is separate from MCP—there are no MCP tool-list or prompt endpoints on these routes. For tools, prompts, and resources, use MCP transport at /mcp.
Configuration and permissions live in the agent guides. Start with Agents overview; for every method and curl example, see Runtime API.

​
How it fits next to MCP

MCP and A2A share one Hyperterse server and the same tool-access rules for agents, but the protocols and client contracts differ.

​
Endpoints

Replace {agentName} with your agent’s name (see Agents overview).

​
What the transport covers

  • Discovery — clients fetch the agent card before calling the JSON-RPC endpoint.
  • Messaging — SendMessage and SendStreamingMessage (SSE when using streaming).
  • Tasks — create, poll, list, cancel, and subscribe to task updates when responses include trackable work.
  • Push — list, create, or delete task push notification configuration when you use those flows.
Method names and payloads match the A2A-style contract in Runtime API.

​
Protocol

Requests use JSON-RPC 2.0 over HTTP POST on /agent/{agentName}. The surface is A2A-compatible so standard agent clients can integrate without a custom protocol. For the exact methods Hyperterse exposes, see Runtime API.

​
Session and reload

  • Task state is how you continue work across turns (not a legacy session-only API).
  • After a model reload, agent routes match your latest config; see Runtime API for behavior notes.

​
CORS

Hyperterse applies CORS on agent routes so browser and cross-origin clients can call them in development. Tighten rules in production like any HTTP API (see Production hardening).