For builders & vendors
Own software agents invoke? Get it verified.
If you publish an MCP server, an API, a library, a CLI, or a model, it is probably already in our corpus — we crawl the registries and specs weekly. Verification is what separates a listing from an answer: a machine-checked contract, a verification score, and an Ed25519-signed trust passport any agent can check before invoking you.
What a verified record gets
- A signed trust passport. An offline-verifiable Ed25519 certificate of what we checked and when — how passports work.
- Answer eligibility. Only verified records can be the answer; when any verified record qualifies for a query, an unverified one never outranks it.
- Your own evidence page.A permanent unfragile.ai/<slug> page rendering your verification evidence, and — for vendors’ own software — the official-door position on your entity page.
- Weekly re-checks. Freshness is part of the promise: the corpus is re-verified on a weekly cadence, and history is never reset.
How it works
- Find your record. Search your package or vendor name from the homepage. Most software is already listed; much is already verified automatically.
- Write to us with the link and proof of ownership (your domain, npm org, or GitHub org).
- We verify by machine and sign. Static verification — resolving your package, parsing your declared contract — is free. Deeper execution verification (we install and run it in a sandbox) is the future paid tier — pricing.
The line we never cross
Rankings are never for sale. Verification can make your record eligibleand deepen its evidence — it can never buy the answer. If a competitor matches a query better, they win it, verified badge or not. That neutrality is the entire value of the badge you’re asking for.