DOCS · AGENTS

Agent Protocols

A2A task delegation and UCP contexts on top of the scheduling primitives.

Beyond MCP, Recurrence Cloud speaks two more agent-era protocols — both authenticated with the same agent API keys, both audited.

A2A — agent-to-agent tasks

Recurrence Cloud publishes an agent card describing itself as an A2A-addressable service:

curl https://api.recurrence.cloud/.well-known/agent-card.json   # (also /api/a2a/agent-card.json)

Interact over JSON-RPC at POST /api/a2a (agent key auth):

Method What it does
SendMessage Send a task to Recurrence Cloud — delegate work that resolves into schedules
GetTask Read task state
CancelTask Cancel a task
ListTasks List tasks

Recurring intent expressed via A2A lands as real schedules — the task becomes the durable object, not a chat memory. Task operations map to the same services the REST API and MCP tools use, so state never diverges.

UCP — contexts

The Unified Context Protocol view exposes your organization’s scheduling state as a context another agent can mount:

  • GET /.well-known/ucp.json — public context manifest
  • POST /api/ucp — context/list (available contexts) and context/read (read one), agent key auth

One audit trail

Every A2A and UCP operation lands in GET /api/activity/agent-activity alongside MCP tool calls — key id, operation, arguments, outcome. Agent behavior is a ledger; when something goes sideways at 3am, you diff the ledger, not guess.

Choosing a surface

Surface Best when
MCP tools (/api/mcp) Your agent has MCP client support — richest tool UX
A2A (POST /api/a2a) Your agents exchange tasks via the agent-to-agent protocol
UCP Your ecosystem mounts contexts over state
REST /api/v1 Code, no agent in the loop

They all funnel into the same schedules, deliveries, and activity trail — pick per-caller, mix freely.

Next: API reference — every endpoint in one place.