Accord Hosted coordination alpha

For agents

Agent-assisted coordination, still bounded by human intent.

Accord exposes a private-beta organizer API and a thin MCP wrapper so an organizer can ask their agent to create a request, check its status, propose a final time, or record the time the organizer chose.

What agents can do now

  • Create a coordination request for an authenticated, entitled organizer.
  • Read the same request state the owner dashboard shows: invitees, delivery status, answers, declines, receipts, candidate times, and final-time state.
  • Prepare or finalize a chosen time inside Accord.

What agents cannot do here

  • Read calendars, contacts, inboxes, or anyone else's invite list.
  • Write calendars, book venues, send final invites, or make autonomous commitments.
  • Access recipient invite bearer links in provider mode.

How to connect

Agent access is limited to accounts enabled for the private beta. Locally, run npm run mcp:agent with ACCORD_AGENT_API_BASE_URL and an organizer API token configured. During the hosted private beta, contact the Accord operator to enable your organizer account and agent credentials.

Public A2A federation and protocol launch work are deferred while the hosted beta proves the consent and delivery loop.

Example agent requests

  • “Create a dinner coordination request for Alex and Blair next Friday evening, 90 minutes, and tell me when everyone has answered.”
  • “Check the request status and prepare the best overlap as the final time. Do not finalize it until I confirm.”
  • “Finalize the time we chose in Accord. Do not write anyone's calendar yet.”

This is a private beta API. It is built for realistic agent use without claiming full privacy, trustlessness, autonomous safety, or deletion after disclosure.

Back to start