The first question every agent asks. The protocol for the agent web. When an AI agent calls your service, whatcanido hands it a manifest, a federated key, and a coin slot at the door. Five primitives. One JSON file at /.well-known/agent-actions.json. No platform between you and the agent.
whatcanido is one product made of five composable parts. Adopt any one without the others; or run the whole stack and ship in an afternoon.
Every AAM site publishes one file at a fixed path. The agent fetches it on demand — no platform installation, no agent-side memory pollution, no proprietary library.
aam_versionSpec version. v0.1 is the current contract.siteName, domain, description. What humans and agents see first.authIdentity proofs accepted: AAM ID JWKS, OAuth handoff, none.actions[]Each: id, params schema, scopes, optional pricing.aam_signatureDetached JWS over the canonical body. Tamper-evident.security_notesUntrusted-content marker convention for IPI defense.GET 200401Bearer402POST 200audit++Public reads, no setup. Curl them, paste them into Claude, run the included x402 demo script. See what an agent finds when it lands.
/b/tadeas-readspublic · auth · paidPersonal book log with public reads, AAM ID gated writes, and an x402 paid tip jar that stamps the payer on the row.
/b/tadeas-consultpublic · authBooking calendar with a required topic field. Public slot listing, gated booking via AAM ID. Booking acts on a per-resource scope.
/b/kitchen-vaultpublic · authTag-able, ingredient-search, prep-time-filter. The kind of thing you ask an agent at 7pm. Free-text search across title + ingredients + notes.