# Overwing Beacon

> Is your product reachable by agents? One lookup of a site that answers three questions: can an agent find it, read it, and use it. It returns a score, the three answers, every check with what was found, and the changes worth making.

## Price

| Who pays | Price | How |
|---|---|---|
| An agent with a wallet | $1 per check | `GET https://overwing.ai/api/x402/beacon?url=<site>`, paid in USDC over x402. No account. The report is the response. |
| A person | $5 per check | The form at https://overwing.ai/beacon, or `POST https://overwing.ai/api/v1/beacon/checks` for a card checkout link. |

One price per check, no subscription. A site that does not answer at all is refused before payment, and a paid request that fails is not settled.

## What is checked

### 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

### 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 by Jev)

### 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 by Jev)
- The text states the price (judged by Jev)

## For agents

```
GET https://overwing.ai/api/x402/beacon?url=example.com          # $1 in USDC over x402; answers 402 with the terms first
GET https://overwing.ai/api/v1/beacon/sample                     # a real report, free
GET https://overwing.ai/api/v1/beacon                            # this description as JSON
```

Without a wallet, start a check and hand the link to a person:

```
POST https://overwing.ai/api/v1/beacon/checks  {"url":"example.com"}   # -> {id, checkout_url, status_url}
GET  https://overwing.ai/api/v1/beacon/checks/{id}                      # 402 until paid, 202 while running, 200 with the report
```

The same three calls are MCP tools on the hosted server: `beacon_start`, `beacon_report`, `beacon_sample`.

## The report

`score` (0 to 100), `verdict` (yes, partly, no), `categories` (find, read, use, each with an answer), `checks` (each with `status`, `detail`, and a `fix` when it did not pass), and `top_fixes` (the three changes worth the most).

## Conduct

Read-only. About 20 requests per check, identified as `OverwingBeacon/1.0 (+https://overwing.ai/beacon)`. The MCP probe sends initialize and tools/list and never calls a tool. The A2A agent is never messaged.

Sample report: https://overwing.ai/beacon/r/bcn_sample0000000000. Guide: https://overwing.ai/llms.txt.
