A2A JSON-RPC 2.0 dispatch (per-agent)
Per-agent JSON-RPC 2.0 entry point. The agent ID is taken from
the path - params.id is ignored. Recognised methods include
message/send, message/stream, tasks/get, tasks/cancel,
tasks/sendSubscribe, agent/getCard, agent/getExtendedCard.
For first-class consumers the dedicated REST endpoints
(/messages/send, /messages/stream, /tasks/{taskId}, etc.)
are preferred - this endpoint exists for A2A interoperability.
Note: tasks/sendSubscribe directly streams Server-Sent Events
without a JSON-RPC wrapper - it does not produce the
application/json body documented here.
Authorizations
User-bound credential carrying an identity: either a session JWT
or a user access token (at:*) generated from the user settings UI.
Send as Authorization: Bearer <token>.
Org API keys (iak_*) are not accepted here - they carry
no user identity. Use the x-prismeai-api-key header instead
(see OrgApiKeyAuth).
Path Parameters
64