A few different rhythms, pick whichever matches the conversation. Debate the spec, show off a tenant, file a bug, or just lurk.
The source of truth — protocol spec, all SDK code, the agentic platform, demo apps, the WordPress plugin. Open issues if you find a bug, send PRs for the spec or the reference implementations.
Best for: Bug reports, spec PRs, code review.
github.com/Tedysek01/aam-sdk ↗Real-time chat with whatcanido devs and other people building on AAM. Channels for #help, #spec-discussion, #showcase (post your tenant), and #connector-requests.
Best for: Live questions, showcasing what you built, debating spec decisions.
Join the Discord ↗Lightweight updates, releases, agent-web news. Mostly Tadeáš shouting into the void about why AAM matters.
Best for: Watching announcements, low-touch engagement.
@whatcanido_dev ↗Direct line for partnership conversations, Scale-tier inquiries, press, security disclosures. Read by an actual human, not a queue.
Best for: Things that aren't a public conversation.
hello@whatcanido.devOpen a PR against landing/spec.md (the protocol authority) plus the spec mirror at apps/aamkit/content/spec/spec.md. We try to keep v0.1 tight; bias toward minimalism when proposing additions.
Want Notion / Slack / Shopify / your favorite SaaS? Implement an executor at apps/aamkit/lib/executors/<name>.ts plus a marketplace card. Open a PR; we'll review and ship.
/spec is currently English-only. AAM is built in Praha and we'd love translations — Czech, Slovak, German, French, Spanish. Open a content/spec/spec.<lang>.md.
Build a tenant on whatcanido and add it to /discover. The richer the public registry, the more agents have to play with. Best advertising for both you and us.