x402-retire-git-feat-paid-indexing-gate-and-openapi-carbonmark.vercel.app

https://x402-retire-git-feat-paid-indexing-gate-and-openapi-carbonmark.vercel.app/api/catalog

Shares a payout wallet with 1 other endpoint — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Live snapshot of the most liquid carbon credits retirable on Base: the top 3 Klima Protocol carbon classes and the top 3 Carbonmark marketplace listings, with USDC-per-tonne prices and tonnes available. Additionally, the additional endpoints to quote and retire carbon are included; query those endpoints for further discovery, quotes, and retirements. Query /.well-known, /openapi, and /discover to get started.

59
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

100.0% avg
0% 50% 100% Tue 10 AMThu 3 PMSat 6 PMTue 8 AM

Response time

p50 91ms · p95 240ms
0ms 1350ms 2700ms Tue 10 AMThu 3 PMSat 6 PMTue 8 AM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/29/2026, 10:00:00 AM 100% 1 126ms
9/29/2026, 12:00:00 PM 100% 1 140ms
9/29/2026, 2:00:00 PM 100% 1 245ms
9/29/2026, 4:00:00 PM 100% 1 74ms
9/29/2026, 6:00:00 PM 100% 1 137ms
9/29/2026, 8:00:00 PM 100% 1 120ms
9/29/2026, 10:00:00 PM 100% 1 144ms
9/30/2026, 1:00:00 AM 100% 1 83ms
9/30/2026, 3:00:00 AM 100% 1 74ms
9/30/2026, 5:00:00 AM 100% 1 80ms
9/30/2026, 7:00:00 AM 100% 1 85ms
9/30/2026, 9:00:00 AM 100% 1 67ms
9/30/2026, 11:00:00 AM 100% 1 69ms
9/30/2026, 1:00:00 PM 100% 1 85ms
9/30/2026, 3:00:00 PM 100% 1 73ms
9/30/2026, 5:00:00 PM 100% 1 165ms
9/30/2026, 7:00:00 PM 100% 1 98ms
9/30/2026, 9:00:00 PM 100% 1 116ms
9/30/2026, 11:00:00 PM 100% 1 73ms
10/1/2026, 1:00:00 AM 100% 1 67ms
10/1/2026, 3:00:00 AM 100% 1 264ms
10/1/2026, 5:00:00 AM 100% 1 81ms
10/1/2026, 7:00:00 AM 100% 1 118ms
10/1/2026, 9:00:00 AM 100% 1 111ms
10/1/2026, 11:00:00 AM 100% 1 98ms
10/1/2026, 1:00:00 PM 100% 1 91ms
10/1/2026, 3:00:00 PM 100% 1 71ms
10/1/2026, 5:00:00 PM 100% 1 74ms
10/1/2026, 7:00:00 PM 100% 1 99ms
10/1/2026, 9:00:00 PM 100% 1 64ms
10/1/2026, 11:00:00 PM 100% 1 86ms
10/2/2026, 1:00:00 AM 100% 1 83ms
10/2/2026, 3:00:00 AM 100% 1 71ms
10/2/2026, 5:00:00 AM 100% 1 107ms
10/2/2026, 7:00:00 AM 100% 1 73ms
10/2/2026, 9:00:00 AM 100% 1 59ms
10/2/2026, 11:00:00 AM 100% 1 73ms
10/2/2026, 1:00:00 PM 100% 1 91ms
10/2/2026, 3:00:00 PM 100% 1 66ms
10/2/2026, 5:00:00 PM 100% 1 239ms
10/2/2026, 7:00:00 PM 100% 1 152ms
10/2/2026, 9:00:00 PM 100% 1 69ms
10/2/2026, 11:00:00 PM 100% 1 71ms
10/3/2026, 12:00:00 AM 100% 1 84ms
10/3/2026, 2:00:00 AM 100% 1 106ms
10/3/2026, 4:00:00 AM 100% 1 86ms
10/3/2026, 6:00:00 AM 100% 1 82ms
10/3/2026, 8:00:00 AM 100% 1 177ms
10/3/2026, 10:00:00 AM 100% 1 103ms
10/3/2026, 12:00:00 PM 100% 1 350ms
10/3/2026, 2:00:00 PM 100% 1 87ms
10/3/2026, 4:00:00 PM 100% 1 101ms
10/3/2026, 6:00:00 PM 100% 1 77ms
10/3/2026, 8:00:00 PM 100% 1 89ms
10/3/2026, 11:00:00 PM 100% 1 81ms
10/4/2026, 1:00:00 AM 100% 1 103ms
10/4/2026, 3:00:00 AM 100% 1 85ms
10/4/2026, 5:00:00 AM 100% 1 100ms
10/4/2026, 7:00:00 AM 100% 1 109ms
10/4/2026, 9:00:00 AM 100% 1 2648ms
10/4/2026, 1:00:00 PM 100% 1 74ms
10/4/2026, 3:00:00 PM 100% 1 91ms
10/4/2026, 5:00:00 PM 100% 1 96ms
10/4/2026, 7:00:00 PM 100% 1 164ms
10/4/2026, 9:00:00 PM 100% 1 69ms
10/5/2026, 2:00:00 AM 100% 1 124ms
10/5/2026, 7:00:00 AM 100% 1 107ms
10/5/2026, 9:00:00 AM 100% 1 83ms
10/5/2026, 11:00:00 AM 100% 1 85ms
10/5/2026, 1:00:00 PM 100% 1 187ms
10/5/2026, 2:00:00 PM 100% 1 92ms
10/5/2026, 4:00:00 PM 100% 1 78ms
10/5/2026, 6:00:00 PM 100% 1 68ms
10/5/2026, 8:00:00 PM 100% 1 98ms
10/5/2026, 10:00:00 PM 100% 1 132ms
10/6/2026, 1:00:00 AM 100% 1 132ms
10/6/2026, 2:00:00 AM 100% 1 115ms
10/6/2026, 5:00:00 AM 100% 1 212ms
10/6/2026, 8:00:00 AM 100% 1 109ms
59
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
61

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
2

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
Tucows Domains Inc
Domain registered
2020-01-28
Hosting network
VERCEL-05
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

35
payments (30d)
0.04
USD volume (30d)
8
paying wallets (30d)

Payments per day

last payment 10/6/2026
0 3 5 Sep 15Sep 25Oct 1Oct 6
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/15/2026 1 0 1
9/16/2026 1 0 1
9/17/2026 2 0 2
9/19/2026 1 0 1
9/24/2026 1 0 1
9/25/2026 2 0 2
9/26/2026 2 0 2
9/28/2026 1 0 1
9/29/2026 3 0 1
9/30/2026 3 0 1
10/1/2026 3 0 1
10/2/2026 4 0 2
10/3/2026 3 0 1
10/4/2026 3 0 1
10/5/2026 3 0 1
10/6/2026 2 0 2

Payout address changed 1 time, last on 10/6/2026

  • 0x6ada…2E39 → 0xf624…2d0e (base) · 10/6/2026

A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.

This payout wallet is shared: figures cover all 2 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

Response schema
{
  "$ref": "#/components/schemas/CatalogResponse"
}