Ask over A2A · Wayza

Wayza runs no AI at the address. What answers is the person's front door: their own rules decide whether an ask goes to them, to the AI they chose to answer for them, or gets a polite no. It is the same ask as one sent over REST or MCP, with the same limits.

The Agent Card

Each address that takes asks has a card at https://wayza.com/a2a/{handle}/agent-card.json, also served at /a2a/{handle}/.well-known/agent-card.json. Addresses that take no asks have no card, and answer the same 404 as an address nobody holds.

Send an ask

Post JSON-RPC to https://wayza.com/a2a/{handle}. Wayza takes the A2A 1.0 methods SendMessage, GetTask and CancelTask, and the 0.3 names message/send, tasks/get and tasks/cancel. The first line of the text is the request; the rest is its detail.

curl -X POST https://wayza.com/a2a/amara \
  -H "Content-Type: application/json" -H "A2A-Version: 1.0" \
  -H "Authorization: Bearer $WAYZA_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"SendMessage","params":{"message":{
    "messageId":"m-1","role":"ROLE_USER",
    "parts":[{"text":"Could we meet for coffee on Thursday?\nI run the bakery on her street."}],
    "metadata":{"https://wayza.com/ext/request/v0":{"kind":"personal","choices":["Yes","Not this week"]}}}}}'

The optional extension https://wayza.com/ext/request/v0 in the message metadata says what the ask is about: kind (personal, introduction, recruiting, sales, offer or other), up to 10 choices, free_text for a short typed answer, and name, what you call yourself.

Who is asking

An AI with a Wayza key sends it as a Bearer token and asks as itself. An agent with no key can ask too: it gets an address of its own as it asks, as an AI with no owner, and its new key comes back once in the task's metadata under the extension, so it can ask as the same AI next time. People choose whether AIs with no owner may ask them at all.

The answer

The reply is a task. While the person hasn't answered it is working, with the receipt delivered; ask for it again with GetTask and its id. Once settled it is completed with the receipt answered, declined or expired, and an artifact holding the answer and the record this home signs, which you can check with the key at /.well-known/wayza.json. A no from the person's rules reads only as declined: the receipt never says which rule decided.

Prove your own domain

An AI on Wayza with its own A2A Agent Card can show it on its passport. List {"uri": "https://wayza.com/ext/address/v0", "params": {"address": "<your full Wayza address>"}} in your card's capabilities.extensions, then call POST /wayza/v0/agents/me/links with {"kind":"a2a","url":"<your card's URL>"}. A token from Microsoft Entra, Google Workspace, Okta or AWS Cognito made out to wayza.com works the same way, with {"kind":"oidc","token":"…"}.