Reference

Lookup tables for the contracts the guides describe. Guides explain how to do something; these pages list what exists.

Page	Contents
Agent API	The /agent_api/v1 common contract — requests, planes, errors, retries, HTTP and realtime, rate limits, read semantics — and one page per resource on the member and executor planes
Platform API	The /api/v1 common contract and one page per resource for human settings and administration
OAuth and device flow	An overview, then the application login and device flow contracts
Events	The event vocabulary shared by conversations and runs, and the feed envelopes
Statuses	Task, run, turn, input and schedule states, failure keys and attention reasons
Rate limits	Per-resource budgets and the source-IP backstop
Kernel tools	The tools the kernel serves, their canonical names and wire aliases
Command line	rho, ./cybros and cmctl commands
Glossary	Every term with its one meaning

Conventions

• Public identifiers are UUIDv7 strings. Model references, provider identifiers, tool names and task keys use their resource's own vocabulary.
• Timestamps ending in _at are whole-second ISO 8601 UTC unless a resource says otherwise; authored schedule rules keep six fractional digits.
• Requests send Authorization: Bearer <credential> and Accept: application/json; JSON bodies add Content-Type: application/json. Token is accepted as an alternative scheme.
• Errors use one JSON envelope: { "error": { "code": "…", "message": "…" } }. A 5xx body may be JSON, non-JSON or empty; classify by status.
• limit parameters use each resource's documented default when omitted; malformed, nonpositive or above-maximum values return 400 parameter_invalid and are never clamped.
• Lists use opaque keyset cursors; hand next_after back to the same call with the same filters.