About

agentscan

Name: Agentscan verified x402 settlement census
Creator: Agentscan
License: https://agents-trust.com/about

trust model v0.6.0 (provisional)

What is agentscan?

agentscan is an open observatory for verified agentic-commerce settlement and trust. It connects real on-chain payment activity to the individual services behind it, so buyers and builders can see which agentic services are active, live, and established — using public evidence, not self-reported claims.

The dashboard surfaces verified settlement volume, transaction history, endpoint liveness, and identity signals for every service in the x402 catalog — and rolls them into a single, auditable trust tier. The underlying data, the scoring methodology, and every per-signal breakdown are public.

agentscan is not an endorsement service. It observes and surfaces public evidence; it does not certify, recommend, or guarantee any service.

How the trust score works

What gets scored

The score is assigned to a service entity — a specific API or product — not to a wallet address or an operator. Every input is drawn from public, objective signals only. Proprietary contact details, outreach history, and any private intelligence are strictly excluded and never enter the score.

Three evidence pillars (v0.6.0)

Traction

Verified on-chain settlement, activity, payer diversity, recency, and integrity modifiers.

Liveness

Whether the service endpoint responds to HTTP 402 requests right now. Includes response speed, uptime across repeated probes, and x402 compliance breadth. A silent endpoint scores zero here regardless of historical volume.

Identity

Verifiable public identity: GitHub org presence, X handle, ERC-8004 on-chain agent registry, .well-known/agent.json, and SKILL.md declaration. No single signal is required; the pillar aggregates what is present.

Longevity is not a fourth pillar in v0.6.0; settlement age is part of Traction. Pillar weights are computed upstream and are not re-derived in this frontend.

NULL ≠ 0 — the honest part

A missing signal is recorded as null, not zero. The composite score is normalized over the pillars we actually have data for, so a lightly-measured service is not penalized for evidence we simply have not yet observed. This matters: many scoring systems collapse “unknown” and “zero” together, which understates some services and overstates others. We keep them separate.

Concretely: if a pillar is absent, the composite is computed across the available pillars only — the score reflects what we know, not what we don't.

Five evidence tiers

The composite score maps to one of five evidence tiers. These are observation categories, not quality certifications.

Corroborated

Multiple independent signals agree: settled on-chain, endpoint live, identity verifiable. The strongest tier.

Established

Strong evidence on most pillars; may have one gap (e.g. identity not fully verifiable yet).

Emerging

Active and live, but still building a longer track record or filling identity signals.

Listed

In the x402 catalog; some signals present but not yet enough to reach Emerging.

Unrated

Not enough evidence collected yet to assign a tier. Unrated does not mean untrustworthy — it means the data is not yet available.

The strongest signal for reaching Corroborated is independent corroboration: on-chain settlement, a live endpoint, and verifiable identity all agreeing — sourced separately, without trusting any single claim.

Versioned and auditable

This is trust model v0.6.0 (provisional). Every service card shows its per-pillar breakdown and per-signal checklist, so the tier assignment is fully auditable. Weights will evolve as coverage expands and the model is validated. The version is shown on every scorecard, and the methodology page you are reading now is the authoritative reference for the current version.

Paid delivery test (v0.6.0)

In trust model v0.6.0, a limited set of top services is verified by a paid first-party delivery test: we send a real micropayment, call the endpoint, and record whether it delivered a correct response.

The delivery result is a trump card, not a scored pillar:

A verified pass adds no composite points — it only unlocks the top-tier evidence gate, closing the “live + a GitHub → Established” loophole.
A quality issue (delivered but degraded) caps the tier at Emerging regardless of composite score.
A failed delivery caps the tier at Listed.
Services that are not yet paid-tested are strictly neutral — no penalty, no badge.

Coverage is the paid-tested top services only. On-chain receipt (tx hash, chain, price, response hash and body length) is shown on each service card. The raw response body is never surfaced.

Data sources

All inputs are public. No private data, no outreach intelligence, no paid data providers.

On-chain USDC settlement
Indexed mainnet settlement on Base, Solana, Algorand, and Polygon. Settlement events are derived from public on-chain data.
Endpoint liveness probes
HTTP 402 requests sent to each service endpoint. Measures reachability, response time, uptime consistency, and x402 compliance breadth across repeated checks.
x402 service catalog
The public directory of services that have registered or been observed using the x402 payment standard.
ERC-8004 on-chain agent registry
A Base and Ethereum on-chain registry of AI agents. Used as one identity signal in the Identity pillar.
Public identity signals
GitHub organization presence, X (Twitter) handle, .well-known/agent.json, and SKILL.md declaration. All verified from public URLs.

Current scope: Base, Solana, Algorand, and Polygon mainnet settlement are indexed. The dashboard marks additional chains active only when indexed settlement is observed.

What's different

A few concrete points on why the approach differs from generic reputation or listing services:

Entity-level settlement linkage

On-chain settlement is matched to individual services, not just wallet addresses. A wallet can be controlled by anyone; this observatory tracks which specific API or product has actually settled payments, at what volume, over what time period. That linkage is the foundation of every trust tier.

Evidence-honest tiers — unknown ≠ zero

Most scoring systems conflate a missing signal with a zero score, which penalizes new or lightly-indexed services unfairly. Here, an absent signal is explicitly 'unknown', the composite normalizes over available pillars, and the service card shows exactly which signals are present and which are not yet collected.

Transparent, versioned, and auditable

The model version is shown on every scorecard. The per-pillar breakdown and per-signal checklist are always visible — you can see exactly which signals contributed to a tier. When weights change, the version number changes and scores are recomputed forward cleanly.

Public-data-only

No proprietary outreach data, no private contact intelligence, no non-public signals. The score is computed entirely from data that any third party could independently verify from public sources. This is a deliberate design constraint, not a limitation.

Evidence tiers, not an endorsement · trust model v0.6.0 (provisional) · View the dashboard →