The bridge behind every Whatcanido product is an open MIT-licensed spec. Publish /.well-known/agent-actions.json on your own site and any AI assistant (ChatGPT, Claude, Cursor, Cody) can discover what your website does, ask for user consent, and call typed actions cleanly.
You already know the loop: a signed POST hits your server, you verify the signature, you call your existing service layer, you return JSON. AAM is the same loop, just with an AI assistant on the other end instead of a payment processor.
Your frontend, your login, your database schema, your deploy pipeline — none of it changes. You add a rewrite, one webhook receiver per action (about twenty lines each, calling your existing service), and a verifier helper. The integration footprint is a few small files. Ripping it out takes five minutes.
Chat-driven backend generator. Describe your service in plain English; Studio writes the resources, actions, manifest, and a working admin.
The full v0.1 wire format. Action discovery, consent flow, JWT scopes, signed manifest, x402 + Stripe payment hooks.
Federated sign-in for agents. The user approves their agent on one site; that approval works everywhere on the network.
Public directory of every site that speaks the spec. Your agent browses it the way you'd Google a place. Anyone can run their own and federate.
Tamper-evident log of every action call. Per-site filtering, agent vendor tags, payment trail. Optional cross-site reputation graph.
Two rails out of the box: Stripe Checkout (the link an agent forwards to the user) and x402 (HTTP 402 + USDC for autonomous spend).
Pre-built connectors for the platforms you already run on. WordPress plugin, Stripe Connect, Reservio (CZ). One install, every action lit up.
AAM vs MCP, Browserbase, Apify, Stripe Link Agent Wallet. What each actually does, and which problem you should pick which for.
A real manifest from a salon running on Whatcanido. An agent fetches this, picks an action, calls it.
{
"version": "0.1",
"site": {
"name": "Aurora Hair Salon",
"description": "Holešovice salon. Cuts, color, balayage.",
"city": "Praha",
"timezone": "Europe/Prague"
},
"actions": [
{
"id": "list_services",
"kind": "list",
"description": "Return the salon's service menu.",
"auth_required": false,
"url": "https://salon-aurora.example.com/api/actions/list_services",
"method": "POST",
"output_schema": { ... }
},
{
"id": "book_appointment",
"kind": "create",
"description": "Book an appointment. Requires consent.",
"auth_required": true,
"scopes": ["book:appointment"],
"url": "https://salon-aurora.example.com/api/actions/book_appointment",
"method": "POST",
"input_schema": { ... },
"output_schema": { ... }
}
],
"auth": {
"authorize_url": "https://salon-aurora.example.com/agent/authorize",
"token_url": "https://salon-aurora.example.com/agent/token"
}
}AAM is the merchant side. MCP is the agent runtime side. Browserbase drives a headless browser through your existing UI. Apify scrapes you. Stripe Link Agent Wallet handles the money. They're all complementary; we play nicely with each.
Full breakdown →Add the bridge to your existing site, or use a Whatcanido product that already has it built in. Both work; pick whichever costs you less time today.