Claim api.paylyte.ai
This origin is in the unclaimed index at 85/85 with 2 routes indexed from the Bazaar. Nobody submitted it. Claiming turns it into a seller record you control.
Human with a card? Claim for $5 at checkout →
One POST, $5 USDC on Base through x402 or MPP, no account, no form. Listing by pull request stays free; the claim buys speed and the skip of the proof-tx requirement, not points.
What a claim adds
- Your contact and your choice of up to five routes on the seller page, instead of the three the crawl picked.
- The README badge at /badge/x402/api-paylyte-ai and a shields.io endpoint.
- The weekly reprobe plus re-probe on demand, and a row in the machine feed buyers filter on.
- No proof transaction needed. The 15 proof points stay unearned until you add one by pull request, so a claimed row tops out at 85 until then.
The call
Any x402 client works. The first request answers 402 with the price and the fee wallet; pay and resend. Optional fields: name, description, homepage, endpoints (same origin), nominated_endpoint, manifest, llms_txt.
POST https://router.forgemesh.io/api/verified/claim
Content-Type: application/json
{
"slug": "api-paylyte-ai",
"contact": "mailto:[email protected]"
}Schema and examples: https://router.forgemesh.io/openapi.json. Slugs: /unclaimed.json.
Proving it is yours
- Pay from the row’s payTo wallet. The fee authorization is signed by the wallet that receives your sales, so ownership is settled on the spot. Status queued; the validator opens and merges the pull request within minutes.
- Or publish a token. Paid from any other wallet, the response carries a token. Put that string anywhere in your /.well-known/x402, your llms.txt, or the README (or a .forgemesh-claim file) of the GitHub repo your manifest declares in a repository field, whose README also names your host. The intake checks every five minutes for seven days, then proceeds. Status pending-proof until then.
- No wallet? Pay by card. A human can pay the same $5 at kit.forgemesh.io/claim and gets the same token to publish. Card claims are merged by a maintainer after the payment is confirmed, so allow a day.
Either way, poll the returned status_url. It is free. When it reads created, the pull request exists; when the check is green it merges itself and your page is live at /verified/api-paylyte-ai.
Rules
- The score is never for sale. It is recomputed from protocol facts on every probe, claimed or not.
- Endpoints and homepage must sit on the claimed origin. The payTo is the one the Bazaar recorded.
- A claim that fails validation gets its reasons at the status URL and three automatic retries. Nothing is refunded for a failed validation, so probe your own 402 first with the free scanner.
- Not in the index yet? Use the free pull request, or POST /api/verified/submit at $0.05 if you cannot open one.