Network · whatcanido

sources federated

2/6

reachable now

tenants in atlas

30s

revalidate window

RS256

manifest signing

01sources · awake or asleep

sourcebase urltenantskindstatus

whatcanidohttps://whatcanido.dev3native200

AAM Platformhttps://whatcanido.dev0wrappeddown

Bookiohttps://bookio-one.vercel.app7vertical200

OrderKithttps://orderkit-tadeas-raskas-projects.vercel.app0vertical401

PetKithttps://petkit-tadeas-raskas-projects.vercel.app0vertical401

BloomKithttps://bloomkit-tadeas-raskas-projects.vercel.app0vertical401

02register your site

Got an AAM-callable site? Submit its manifest URL and we federate you here. The endpoint validates against v0.1 before accepting and verifies the signature if your manifest is signed.

Errors fail the submission with diagnostics.
Warnings pass; you get scored on the validator page.
Re-submission updates your row instead of duplicating it.

POST /api/registry/sites

$ curl -X POST https://whatcanido.dev/api/registry/sites \
    -H 'content-type: application/json' \
    -d '{
      "manifest_url":
        "https://yoursite.com/.well-known/agent-actions.json"
    }'

→ 201 {
    ok: true,
    entry: {
      domain: "yoursite.com",
      name: "Your Site",
      action_count: 6,
      paid_action_count: 1,
      signature_verified: true
    }
  }

03how the federation works

Each source above runs its own AAM stack. whatcanido federates by pulling /api/registry/tenants (or the equivalent) on each revalidate, normalizing the shape, and merging into the atlas. There is no single point of authority — any site can run as a registry node, any node can mirror any other.

When a source 5xx's or times out, it's flagged here but old data still serves on /discover until the next successful pull. When it returns, fresh entries replace stale ones automatically.

Federation health, across the network.