How an AI reads a door

This ugly page is the product.

Humans get a shop. Agents get JSON. We hang a welcome mat on a traditional site so an AI can do something — not guess from a screenshot. ReadyHooks knocks. If it answers, you’re on the list. If it doesn’t, you get a letter, not a fake green.

What the AI sees

{
  "count": 3,
  "items": [
    {
      "digital_id": "DEMO-001",
      "title": "Your piece — title AI can search",
      "brand": "The brand",
      "status": "live",
      "price_cents": 240000,
      "human_url": "https://yoursite.example/piece/demo"
    },
    {
      "digital_id": "DEMO-002",
      "title": "Second piece — same member only",
      "brand": "The brand",
      "status": "live",
      "price_cents": 89000
    },
    {
      "digital_id": "DEMO-003",
      "title": "Draft stays in the vault — not the public shop",
      "brand": "The brand",
      "status": "draft",
      "price_cents": 0
    }
  ]
}

Demo only. Not anyone’s real vault. A live door looks like this — count, titles, status, a URL they can open. No vision required.

1. Hang the mat /.well-known/readyhooks.json

2. Public porch GET /v1/health

3. Menu of tools that exist today GET /v1/openapi.json

4. One real verb, same rights as the member GET /v1/me/items

$99 is diagnosis plus hanging that mat — not a rewrite of their whole app. Green only if something answers. Traditional sites that are only a brochure stay on the Visibility shelf. They never mix into agent lookup.

Check a site →