Overwing

Overwing Beacon

Is your product reachable by agents?

One payment by card, no account. You pay on Stripe and the report opens when payment completes.

See what you get first: a real report on our own site.

More and more of the visitors choosing software are agents. They do not see your landing page the way a person does: they look for an llms.txt, an MCP server, an agent card, an API description, and a page they can read without a browser. Beacon looks for the same things and tells you what it found, what is missing, and what to change first.

Three questions

Find, read, use. In the order an agent meets you.

01

Find

Can an agent discover the product and where its surfaces are?

  • robots.txt lets AI agents in
  • A sitemap lists the pages
  • llms.txt tells a model what the product is and where to go
  • The MCP server is in the official MCP Registry
02

Read

Can an agent read what the product is?

  • The home page is served to an automated client
  • The page has content without running JavaScript
  • The page has a title and a description
  • The page carries structured data
  • A markdown version of the page is offered
  • The text says what the product does · judged
03

Use

Can an agent call the product without a person?

  • An MCP server card is published
  • A hosted MCP endpoint answers
  • An A2A agent card is published
  • An OpenAPI document is at a well-known address
  • An agent can pay without an account
  • The text tells an agent how to start without a person · judged
  • The text states the price · judged

Most checks are facts: a file is there or it is not. Three are judgments a program cannot make, such as whether your text says what the product does; those are answered by TypeSafe’s Jev model and marked as judged. The check is read-only, about twenty requests, identified as OverwingBeacon. It never calls a tool on your MCP server and never messages your agent.

For agents

One call, one dollar. No account, no form.

An agent with a wallet calls one endpoint and pays $1 in USDC over x402. The report is the response. A site that cannot be checked is not charged.

An agent without one starts the check with POST /api/v1/beacon/checks, hands the checkout link to its person, and reads the report from the status address once it is paid.

Over MCP, the same calls are the tools beacon_start, beacon_report and beacon_sample on the hosted server at /mcp.

Reports can be kept. Download one as Markdown or JSON, print it to PDF, or save it to your dashboard; an agent adds ?format=md or sends its key.

Every failed check carries a fix written to be acted on, and top_fixes ranks them by how much each is worth, so an agent can open the pull request itself.

Described for machines at /api/v1/beacon, /beacon.md and /llms.txt.

GET /api/x402/beacon?url=yourproduct.com

402 Payment Required          # the terms: $1 USDC on Base
  …sign with any x402 client and resend…

200 OK
{ "status": "complete", "score": 57, "verdict": "partly",
  "categories": [
    { "key": "find", "answer": "yes",    "points": 23, "max": 23 },
    { "key": "read", "answer": "yes",    "points": 37, "max": 41 },
    { "key": "use",  "answer": "no",     "points": 3,  "max": 47 } ],
  "top_fixes": [
    { "check": "a2a_agent_card", "gain": 12,
      "fix": "Publish /.well-known/agent-card.json (A2A): name, …" },
    { "check": "mcp_endpoint", "gain": 10,
      "fix": "Host an MCP endpoint (Streamable HTTP) so an agent …" } ],
  "checks": [ { "id": "llms_txt", "status": "pass", "detail": "…" }, … ] }

Pricing

One price per check. Nothing to subscribe to.

$5
per check for people, by card, from the form above
$1
per check for agents, in USDC over x402
0
if your site does not answer at all: it is refused before payment