AI-readable profile and A2A
Your business as a machine-readable agent: a public profile, a JSON API, an agent card and a JSON-RPC endpoint that other AI assistants can call.
Besides the chat widget for people, Elvix publishes your business as a machine-readable agent for other AI assistants — ChatGPT, Claude, Gemini and agent platforms. They read your facts, prices and contacts without scraping your site, and can call your agent directly.
Where to find it
Open your dashboard and go to AI Agents. The section has three blocks: the public address, the profile, and the A2A test.
Public address
Every company gets a permanent address built from its handle (for example acme from acme.com). You do not need to configure anything — it works as soon as your profile is built. You only change the handle if you want a different short name in the link.
/pl/agent/for-ai?h=<handle>— a short readable page for assistants./pl/agent/for-ai.json?h=<handle>— the same facts as structured JSON./pl/agent/llms.txt?h=<handle>— a compact card with a link to the JSON./pl/agent/agent-card.json?h=<handle>— the A2A agent card: skills, transport and endpoint.
Profile
The profile is built automatically from the pages in Data Sources: services, prices with a link to the source page, key facts and contacts. Press Rebuild only after the content on your site changes. A profile with a green "live" badge means assistants can already read you — nothing else to do.
A2A endpoint
Your agent answers other agents over A2A (JSON-RPC, method message/send) at /pl/agent/a2a?h=<handle>. The reply contains facts from your profile with source links, plus your contact and booking links. The Test A2A button sends a real request the way another agent would and shows the raw answer — useful to confirm everything works after a rebuild.
How assistants find you
- The agent card is linked from your site through JSON-LD (
sameAs), so crawlers connect the site with the agent. - The for-ai page is intentionally
noindex— it is for machines, not for search results, so it never competes with your site. - JSON and llms.txt are public and cacheable, so assistants can read them without a browser.
- AI crawlers are allowed in robots.txt (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot and others).
Booking and leads over A2A
Your agent can do more than answer: it books meetings in Calendly and creates leads. Both happen only with the buyer's explicit consent, which the calling assistant confirms in the request.
What the calling agent sends
{
"method": "message/send",
"params": {
"contextId": "ctx-1",
"message": {
"role": "user",
"parts": [{ "kind": "text", "text": "Book a call please" }],
"metadata": {
"authorized_by_user": true,
"contact": { "email": "[email protected]", "name": "Alex" },
"booking": { "start_time": "2026-11-18T10:00:00Z" }
}
}
}
}What happens on our side
- A lead is created with the contact, the question and the source marked
a2a— it appears in Leads next to chat leads. - If
booking.start_timeis a free slot and Calendly is connected, the meeting is booked right away and the reply contains the confirmation. - The lead gets a green Booked badge, and the dashboard shows a live notification with the meeting time.
- Without
authorized_by_user: trueno contact is stored and nothing is booked — the agent only answers questions. - A repeat request for the same contact and slot returns “already booked” instead of creating a duplicate.
What you need to do
- Add your Main Website in Data Sources — the agent answers best when it knows the whole site.
- Build the profile once; rebuild it after major changes to your services or prices.
- Paste the public address into a chat with ChatGPT or Claude to see how it answers about your business.