A2A is available on request. Contact us to turn it on for your Account. Until it is on, the A2A addresses below return
404 and the endpoint page does not show the A2A card.Before you begin
- A2A is on for your Account.
- You have an endpoint that serves search. See AI Endpoints.
- You have an API key that covers the endpoint. Create one under API access on the endpoint page, or on the API keys tab in Access.
Get the agent URL
1
Open the endpoint
In Search Rail, select the endpoint under Your audience to open its Endpoint settings page.
2
Find the A2A card
The Connect an agent (A2A) card shows the agent URL with a copy button. Under it, Agent card: shows the agent card URL.Both are built from the endpoint’s address:
The endpoint address is the endpoint URL without the trailing
/mcp, for example https://endpoints.app.raily.ai/t/your-workspace/123.3
Paste it into your agent platform
Click Where to paste it on the card for steps in Microsoft Copilot Studio, Microsoft Foundry, ServiceNow AI Agent Fabric, Google Gemini Enterprise and ADK, and frameworks like LangGraph and CrewAI. Some platforms ask for the agent URL, others for the agent card URL.For the key, send it as
Authorization: Bearer <key>, or in an X-API-Key header when the platform asks for a named header.Sign-in
A2A uses the same credentials as the rest of the endpoint:- An API key (
rly_...) that covers this endpoint, sent asAuthorization: Beareror inX-API-Key. - An OAuth access token from the endpoint’s sign-in, sent as
Authorization: Bearer.
401. The agent card itself is public, so platforms can read it before they authenticate.
Skills
The agent card lists the skills your endpoint offers:- Search is always the default skill. Every message without a skill selection runs it, which covers all chat platforms.
- Summary appears when the endpoint also has a summary tool. It returns a written overview of what your content covers, plus the same overview as typed data. The message still needs some text, but the summary ignores it.
"skill": "<id>" in the message or request metadata. An unknown id is rejected.
Try it with curl
Fetch the agent card:supportedInterfaces (the agent URL for versions 1.0 and 0.3), the skills, and the accepted credentials.
Send a message with A2A v1.0 (SendMessage):
"method": "message/send", "role": "user", and parts in the form { "kind": "text", "text": "..." }. You can send the key in X-API-Key instead:
What comes back
The reply is one message with two parts:- A text part with the readable answer, the same text an AI agent would see.
- A data part (
application/json) with typed results underresults. Each result has the same shape as an SDK search result:id,score,text,fields, and links where your content has them.
acceptedOutputModes in the request’s configuration to ["text/plain"] or ["application/json"].
Every reply is a direct message. Raily does not create long-running tasks or send push notifications.
Calls over A2A appear in the endpoint’s activity like any other call. On Access Overview, the Protocols card counts them under A2A.
Next steps
Search from your app
Call an endpoint with an API key
Deep research
Give agents multi-step research