Overwing services
Agent-ready, done for you.
People now ask an assistant which tool to use, and the assistant reads your site, or cannot. We make your product findable, readable and usable by agents for a fixed price, deliver it as pull requests, and measure it with the same check before and after.
From $1,500. About 5 business days. No retainer.
Two packages
A fixed price, a fixed list.
Everything an agent needs to discover the product and understand it without a browser.
- 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
All of the above, plus a way for an agent to call the product without a person.
- 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
Half is invoiced to start and half when the re-check shows the agreed items passing. Invoices are sent by Stripe. Not included: letting agents pay you per request. Few products need that yet, so it is quoted on its own when you do.
How it works
The report is the statement of work.
Check
Run Beacon on your site. It is free and takes about twenty seconds. The report is the list of work: every gap it names is an item we agree to close or leave.
Agree
You pick a package and we confirm the items in writing before anything is invoiced. If your stack makes an item impractical, it comes off the list and off the price.
Build
The work arrives as pull requests into your repository, small enough to review. With no repository access you get the files and a deployable package instead. Nothing is deployed by us.
Re-check
Beacon runs again once the changes are live. You get the before and the after, and the second invoice is sent only when the agreed items pass.
Said plainly
What this is, and is not.
The reference is this site. Everything in both packages is live on overwing.ai, and Beacon’s sample report is a real check of it, refreshed daily. This is a new service, so there is no customer list to show you yet. There is the work itself, which you can inspect.
It does not promise traffic. It makes sure that when an agent or an assistant comes looking, it finds a product it can read and call. How often they come is not something anyone can sell you honestly.
The conventions are young. llms.txt, the MCP Registry and the A2A agent card are in use today. The MCP server card is still a proposal. We build to what agents read now, say which parts are settled and which are not, and keep each one small enough to change.
What we need from you. A person who can review and merge, read access to the repository or the docs source, and an API key for a test account if the package includes the MCP server.