# Agent-ready, done for you

> Overwing makes a product findable, readable and usable by AI agents for a fixed price. The work is delivered as pull requests and measured by the same Beacon check before and after.

## Packages

| Package | Price | Time | What it is |
|---|---|---|---|
| Found and read | $1,500 | about 5 business days | Everything an agent needs to discover the product and understand it without a browser. |
| Found, read and used | $4,500 | about 10 business days | All of the above, plus a way for an agent to call the product without a person. |

### Found and read

- llms.txt written from your docs: what the product is, how to start, what it costs
- robots.txt and a sitemap that let AI agents in, with nothing opened that you want closed
- A markdown version of up to 10 key pages, by address and by Accept header
- Structured data, titles and descriptions on those pages
- Home page text that states what the product does, how to start and the price in words a model can lift
- Your OpenAPI document published at a well-known address, if you have one

### Found, read and used

- Everything in Found and read
- A hosted MCP server over up to 10 operations of your existing API, using your existing keys
- initialize and tools/list answer without credentials, so an agent can see what you offer before it signs up
- The server listed in the official MCP Registry under your domain
- An MCP server card (a proposed convention, not yet part of the standard) and an A2A agent card
- A short guide in your docs for connecting it to Claude, ChatGPT and Cursor

50% is invoiced to start and the rest when the re-check shows the agreed items passing. Invoices are sent by Stripe. Letting agents pay per request is not included; it is quoted separately.

## How it works

1. **Check.** Run Beacon on the site, free: https://overwing.ai/beacon. The report is the list of work.
2. **Agree.** The items are confirmed in writing before anything is invoiced. An item the stack makes impractical comes off the list and off the price.
3. **Build.** Pull requests into the customer's repository, or files and a deployable package without repository access. Overwing deploys nothing.
4. **Re-check.** Beacon runs again once the changes are live. The customer gets the before and the after.

## Said plainly

- The reference is overwing.ai itself: everything in both packages is live there, and https://overwing.ai/beacon/r/bcn_sample0000000000 is a real check of it. This is a new service with no customer list yet.
- It does not promise traffic. It makes sure an agent that comes looking finds a product it can read and call.
- llms.txt, the MCP Registry and the A2A agent card are in use today. The MCP server card is still a proposal.

## Ask for it

A person writes to support@overwing.ai with the site, the package, and where the code lives. There is no API for this; it is work done by people. Page: https://overwing.ai/services