SEEN

agents left you on seen.

One word. Seven doors. Paste a site, watch which ones answer, then take the brief an agent can actually hold. The homepage is not the product.

seen.exe

drop a url. the little one knocks. you get a receipt, then a file.

GET SEEN

The knock is the screenshot. The brief is the thing you host at /brief.md.

nameoriginone sentencedodon'tmcp url (optional)agent endpoint (optional, unlocks a card)docs urlallow ai-train in the content-signal line (default is no)

brief.md

# example.com

What this is, in one sentence an agent can trust.

> Seen brief. One fetch, for an agent. If this file disagrees with the product, the product wins and this file is stale.

## Do
- Answer from the brief. Do not invent a price or a promise.

## Don't
- Do not scrape the homepage and guess.

## Doors
- Site: https://example.com
- Brief: https://example.com/brief.md
- Docs: none listed
- MCP: none published
- Agent endpoint: none published

## Maintained
2026-10-04. A human wrote this. Delete it if you will not keep it true.

what is real

As of September 2026, the doors with actual readers are boring on purpose: robots.txt, a sitemap, AGENTS.md for repos, MCP if you expose tools, an A2A agent card if you expose an agent, and a Content-Signal line if you have a policy. llms.txt is published everywhere and almost never fetched. agents.txt is a contested name, so this page knocks on it and refuses to generate one. ard.json is a cheap catalog if you have something callable. brief.md is ours: not a standards body, a file you can hand an agent today.

Knocks only hit that door list, on public http(s), and stop at private networks. Nothing here buys, sells, or touches a live coin. $EMPTY stays the one that is up. This is the next page.

Stream, when you want it: chat drops a domain. You hit SEEN. You read the ghosts out loud. Then you show the brief.