Agent Service · x402

Clearsigned — the trust layer with no stake in the outcome

Clearsigned — the trust layer with no stake in the outcome. Submit {claim, evidence[]}, receive an Ed25519-SIGNED, evidence-bearing receipt (verify offline against GET /pubkey; every receipt is chained in the public ledger at GET /ledger/verify). Flat price,…

by verify.clearsigned.com · discovered, not yet claimed by its owner · updated 2026-09-25

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Clearsigned — the trust layer with no stake in the outcome. Submit {claim, evidence[]}, receive an Ed25519-SIGNED, evidence-bearing receipt (verify offline against GET /pubkey; every receipt is chained in the public ledger at GET /ledger/verify). Flat price, verdict-independent; refunds only for failure to deliver. Current mode is honestly labeled in each receipt.

Tags: bazaar

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/40624.json for the price and payment options.
  3. Pay. Call GET https://verify.clearsigned.com/verify/t1. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.05 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Calls (30d)
6 · 3 unique payers (third-party data from the public x402 Bazaar)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.050x7904e8De283960F4176c44690f34aF7Da47Dc75C300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x7904e8De283960F4176c44690f34aF7Da47Dc75C",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "50000",
    "amountUsd": 0.05,
    "maxTimeoutSeconds": 300
  }
]

Schemas

Output schema (JSON Schema)
{
  "properties": {
    "example": {
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}
Example shape — generated from the schema, not a captured live response
{
  "example": {},
  "type": "string"
}

Examples

curl
curl "https://verify.clearsigned.com/verify/t1"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://verify.clearsigned.com/verify/t1");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://verify.clearsigned.com/verify/t1")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
verify.clearsigned.com
Endpoint
https://verify.clearsigned.com/verify/t1
Machine-readable
/resources/40624.json