mart402.com

https://mart402.com/v1/structured

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

Schema-driven extraction: fill YOUR JSON schema from any URL. Hybrid LLM + deterministic canonicalization. 0.02/call.

62
reliability

Reliability & health

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

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Jul 27Aug 4Aug 12Aug 20

Response time

p50 20ms · p95 25ms
0ms 50ms 100ms Jul 27Aug 4Aug 12Aug 20
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
7/27/2026, 12:00:00 AM 100% 1 22ms
7/28/2026, 12:00:00 AM 100% 1 22ms
7/29/2026, 12:00:00 AM 100% 1 22ms
7/30/2026, 12:00:00 AM 100% 1 21ms
7/31/2026, 12:00:00 AM 100% 1 18ms
8/1/2026, 12:00:00 AM 100% 1 19ms
8/2/2026, 12:00:00 AM 100% 1 21ms
8/3/2026, 12:00:00 AM 100% 1 19ms
8/4/2026, 12:00:00 AM 100% 1 20ms
8/5/2026, 12:00:00 AM 100% 1 19ms
8/6/2026, 12:00:00 AM 100% 1 20ms
8/7/2026, 12:00:00 AM 100% 1 20ms
8/8/2026, 12:00:00 AM 100% 1 20ms
8/9/2026, 12:00:00 AM 100% 1 19ms
8/10/2026, 12:00:00 AM 100% 1 23ms
8/11/2026, 12:00:00 AM 100% 1 23ms
8/12/2026, 12:00:00 AM 100% 1 19ms
8/13/2026, 12:00:00 AM 100% 1 23ms
8/14/2026, 12:00:00 AM 100% 1 17ms
8/15/2026, 12:00:00 AM 100% 1 21ms
8/16/2026, 12:00:00 AM 100% 1 23ms
8/17/2026, 12:00:00 AM 100% 1 20ms
8/18/2026, 12:00:00 AM 100% 1 18ms
8/19/2026, 12:00:00 AM 100% 21 20ms
8/20/2026, 12:00:00 AM 100% 19 21ms
62
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
6

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
Cloudflare, Inc.
Domain registered
2026-07-19
Hosting network
—
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)

63
payments (30d)
23.88
USD volume (30d)
1
paying wallets (30d)

Payments per day

last payment 8/20/2026
0 10 20 Jul 25Jul 30Aug 9Aug 20
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
7/25/2026 2 0 1
7/26/2026 1 0 1
7/27/2026 14 0.15 1
7/29/2026 3 0.01 1
7/30/2026 1 0 1
8/2/2026 1 0 1
8/3/2026 4 0.02 1
8/4/2026 6 0.06 1
8/5/2026 4 0.06 1
8/9/2026 12 23.25 1
8/10/2026 1 0.05 1
8/12/2026 1 0.03 1
8/19/2026 11 0.18 1
8/20/2026 2 0.07 1

This payout wallet is shared: figures cover all 6 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.

https://mart402.com/v1/enrich x402 endpoint https://mart402.com/v1/extract x402 endpoint https://mart402.com/v1/verify x402 endpoint https://mart402.com/v1/jp-company x402 endpoint https://mart402.com/v1/ocr x402 endpoint
Response schema 
{
  "input": {
    "body": {
      "schema": {
        "title": "page title"
      },
      "url": "https://example.com"
    },
    "bodyType": "json",
    "discoverable": true,
    "method": "POST",
    "type": "http"
  },
  "output": {
    "description": "JSON: your schema filled from the page, with per-field source evidence"
  }
}