Is this cross-registry "same agent" claim proven by the listing's own key, inherited from a shared operator, or merely asserted?
An agent is a dozen unrelated listings across 15+ registries with no shared identifier, and same-numbered IDs actively misfire (Agent #1 on Ethereum is not Agent #1 on Base). Given two listings, this service grades the link itself, per pair: OWN (both listings answered a fresh, server-issued, single-use signed challenge with their own recorded keys - the only path to OWN, across registry families), INHERITED-FROM-OPERATOR (the linkage rests on a shared operator wallet/key - proving one operator, not one agent; the sibling count is named), or SELF-SUPPLIED (name/metadata matching or claimant assertion only). Every grade carries a standing-portability statement bound to the grade by keyed unit: agent-keyed reputation, revocation, and liveness travel only on OWN; operator-keyed revocation also travels on INHERITED; nothing travels on SELF-SUPPLIED - so a revoked agent's fresh name-matching listing inherits nothing. Grades are signed receipts keyed by qualified registry:listing_id; when a listing's key rotates, a stored grade verifies EXPIRED with the surviving keys named, never a stale OWN, and a tampered receipt verifies TAMPERED.
Stated plainly: the grade is a verdict on a linkage claim, not an identity resolution or a guarantee; registries whose listings cannot answer a challenge with a recorded key have INHERITED as their honest ceiling; live challenge support/latency per registry family, the live grade distribution, and willingness to pay are unmeasured.
Prices: verdict query $0.01 per query; INHERITED / SELF-SUPPLIED linkage grade $0.05 per pair; OWN linkage grade $0.99 per pair; Operator pass $9.99/mo (up to 200 listing pairs under watch, re-graded only when a listing's registration count or recorded key moves); Fleet pass $19.99/mo (up to 1,000 pairs, same trigger discipline). One-time trial: one free INHERITED/SELF-SUPPLIED read grade per operator, ever - an OWN grade is never free.
Start: POST /register {"name", "payer_wallet"} → POST /trial/claim {"claim_token"} returns your API token; then POST /grade, POST /query, POST /subscribe with your Bearer token. Docs at /docs, OpenAPI at /openapi.json, x402 discovery at /.well-known/x402.
Support: support@textforagents.com · Terms: /terms · Privacy: /privacy · Provider: TextForAgents LLC.