JSON-RPC 2.0 endpoint (all agent operations dispatch here)
Every write or read operation on tasks, messages, and contexts
uses this endpoint. The method field in the body selects the
operation. See the Error catalog in the top-level description
for every possible error.code.
Accepted methods: message/send, message/stream
(experimental), tasks/get, tasks/list, tasks/cancel,
tasks/feedback, contexts/list, contexts/clear.
Casing tolerance: the server accepts both camelCase
(taskId) and snake_case (task_id) in params — pick one
and stick with it per-call. Responses are always snake_case.
Size limit: request bodies over 10 MB return 413 Payload Too Large at the ASGI layer (does not use the
JSON-RPC error envelope).
Idempotency: message/send is NOT idempotent — a repeat
call creates a new task. If you need idempotency, have your
client generate a stable messageId and use contexts/list
tasks/listto check whether you’ve already sent it.
Documentation Index
Fetch the complete documentation index at: https://docs.getbindu.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
OAuth2 access token issued by Ory Hydra. Required for most operations.
Scopes:
agent:read— Read-only operations (tasks/get, tasks/list, contexts/list)agent:write— Write operations (message/send, tasks/cancel, contexts/clear)agent:execute— (legacy) Both read and write access
How to obtain:
- Register your client with Hydra
- Complete OAuth2 client credentials or authorization code flow
- Include token in
Authorization: Bearer <token>header
Body
JSON-RPC 2.0 request envelope. One of the per-method
params shapes must be supplied via the method field.
"2.0"message/send, message/stream, tasks/get, tasks/list, tasks/cancel, tasks/feedback, tasks/pushNotificationConfig/set, tasks/pushNotificationConfig/get, tasks/pushNotificationConfig/list, tasks/pushNotificationConfig/delete, contexts/list, contexts/clear Caller-chosen request id. The response echoes it back.
Method-specific params (see per-method schemas below)
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
Response
Successful JSON-RPC response. result contains the typed
output per method — see components/schemas/*Result.