x402 · BASE MAINNET

Pay-per-call UK data & utilities,
no API keys required.

DataBroker serves DVSA MOT history, fleet analytics, and 24 identifier, geospatial and reference-data utilities over HTTP, gated by x402 micropayments. Send a signed USDC payment, get an answer back. No accounts, no subscriptions, no rate-limited free tiers — just a price per call, from $0.001.

curl /v1/discover View on GitHub llms.txt

Quick start

$ curl https://api.databroker.mossforge.dev/v1/discover

{
  "datasets": [
    {
      "dataset_id": "dvsa-mot",
      "description": "DVSA MOT history for UK vehicles",
      "price_usdc": "0.005",
      "network": "eip155:8453",
      "kind": "cached"
    },
    {
      "dataset_id": "dvsa-mot-analytics",
      "description": "Aggregated MOT analytics by vehicle segment",
      "price_usdc": "0.02",
      "network": "eip155:8453",
      "kind": "cached"
    },
    {
      "dataset_id": "util-iban",
      "description": "IBAN validation — length, check digits, BBAN parse",
      "price_usdc": "0.001",
      "network": "eip155:8453",
      "kind": "computed",
      "standard": "ISO 13616 / ISO 7064 MOD 97-10",
      "deterministic": true
    }
    // ... 26 more datasets
  ]
}

Datasets

/v1/dvsa-mot/{registration}

$0.005 USDC per call

Full MOT history for any UK vehicle — pass/fail summary, mileage, and individual test records with defects. Cached 30 days.

/v1/dvsa-mot-analytics/{key}

$0.02 USDC per call

Aggregated pass rates, top defects, mileage percentiles, and fuel mix by vehicle segment. Refreshed daily from the full DVSA dataset.

Utility endpoints

24 single-purpose endpoints an agent can call instead of implementing the algorithm itself. Pure computations are $0.001, reference-data lookups $0.002. Every response states the standard it implements and whether the result is deterministic. Malformed keys are rejected free of charge before any payment is taken — you only ever pay for a well-posed question.

Vehicles

util-vin — VIN decode & check digit
util-uk-plate — UK plate format & age decode
util-mot-due — first MOT due date
util-tyre-size — ISO tyre code parser

Finance & securities

util-iban — ISO 13616 validation
util-isin / util-cusip / util-sedol
util-lei — ISO 17442 validation
util-card — Luhn + network detection
util-aba-rtn — US routing numbers

Product & logistics

util-gtin — EAN/UPC validate & compute
util-isbn — validate + 10↔13 convert
util-issn — serial identifiers
util-container — ISO 6346 containers
util-imo — IMO ship numbers

Algorithms & geo

util-checkdigit — Luhn / Verhoeff / Damm / ISO 7064
util-geo — great-circle distance & destination
util-geohash — encode / decode

Reference lookups

util-oui — MAC address vendor
util-airport — IATA / ICAO codes
util-tz — IANA timezone info
util-currency — ISO 4217
util-locode — UN/LOCODE

Example

GET /v1/util-iban/GB82WEST12345698765432
GET /v1/util-geo/distance:51.47,-0.45,40.64,-73.78
GET /v1/util-airport/LHR

How payment works

Request a paid route with no payment header. DataBroker responds HTTP 402 with the exact amount, recipient address, and network in a PAYMENT-REQUIRED header.
Sign an EIP-3009 transfer authorization for the required USDC amount using your agent or app's Base wallet.
Retry the request with a PAYMENT-SIGNATURE header containing the signed payload.
DataBroker verifies and settles the payment on-chain, then returns the data with a PAYMENT-RESPONSE receipt header. You only pay on a 200.

Resources

Agent-readable API description/llms.txt

Machine-readable API spec/openapi.yaml

Source, examples, integration guidegithub.com/mossforge/databroker

x402 protocolx402.org