Agent to agent (A2A)

A live expert can describe itself to other AI agents with an A2A Agent Card. Other agents, and your own code, can then talk to it through the public routes, which need no API key.

Make an expert discoverable

Turn discovery off, or move the expert back to draft, and both URLs answer 404.

The Agent Card

curl https://api.rydhm.ai/v1/public/experts/ava-k8nzvywsyuhw/agent-card

{
  "name": "Ava",
  "description": "Answers product questions and walks prospects through features.",
  "url": "https://app.rydhm.ai/e/ava-k8nzvywsyuhw",
  "version": "1.0.0",
  "capabilities": { "streaming": true },
  "defaultInputModes": ["text", "audio"],
  "defaultOutputModes": ["text", "audio"],
  "skills": [
    {
      "id": "talk",
      "name": "Talk to Ava",
      "description": "Answers product questions and walks prospects through features."
    }
  ]
}

• url is the expert’s public page, where people can chat or talk to it.
• There is one skill, talk. The card never lists the workspace’s tools or other private capabilities.

The MCP manifest

GET /v1/public/experts/{code}/mcp describes the same expert as a tool list:

{
  "server": "Ava",
  "protocol": "mcp",
  "tools": [
    { "name": "ask", "description": "Ask Ava a question. It answers from its own knowledge base." }
  ]
}

This manifest is a description, not a server you can call. To use an expert as a real MCP server, with an API key, see MCP.

Talk to a public expert

Any live expert, discoverable or not, answers on the public routes. They need no key, so other agents and your own frontend can call them directly. The expert answers from its knowledge only: anonymous callers never run your workspace’s tools.

Replace ava-k8nzvywsyuhw with the expert’s public link code: the part after /e/ in its public link.

curl -X POST https://api.rydhm.ai/v1/public/experts/ava-k8nzvywsyuhw/chat \
  -H "Content-Type: application/json" \
  -d '{}'

{ "conversationId": "10699545-14b2-4352-a060-e3710dd3c82b" }

curl -X POST https://api.rydhm.ai/v1/public/chat/$CONVERSATION_ID/messages \
  -H "Content-Type: application/json" \
  -d '{"content":"What do you help with?"}'

curl -N https://api.rydhm.ai/v1/public/chat/$CONVERSATION_ID/stream

To keep the conversation going, send the next message and read the stream again.

Voice

POST /v1/public/experts/{code}/voice-session starts a voice call with a live expert. It returns a token your frontend uses to join the call with the LiveKit client SDK:

{
  "serverUrl": "wss://…",
  "roomName": "…",
  "participantToken": "eyJhbGciOi…"
}

Connect with serverUrl and participantToken. The body can carry variables and language, as for chat.

Limits on public routes

Public routes are limited per visitor IP address and per expert, so one caller can’t run up your workspace’s costs:

A refused request gets 429 with a Retry-After header. Public chats and calls use the expert’s workspace’s credits, and voice calls count toward its limit of calls at once.

If the expert has an allowed websites list, browser requests from other sites get 403 with error: "origin_not_allowed". Server-to-server requests, which send no Origin or Referer header, are allowed and still count against the limits above.

Experts consulting other experts

Your own experts can hand a live conversation to a specialist: another live Rydhm expert, added by its Agent Card URL on the expert’s Tools tab. See Specialists.