Build with operational receipts: address validation, geocoding, flood, census, climate, risk signals, MCP tools, x402 payments, and independent verification.

Eligible responses can return a decision-ready verdict and a tamper-evident operational receipt for independent verification.

Customers retain the receipt and associated verification material needed to verify what was returned at decision time, on their own infrastructure, independent of any GeoClear application server.

Pass your API key via header or query parameter on every request.

curl https://geoclear.io/api/address?street=Main+St&city=Austin&state=TX \
  -H "X-Api-Key: YOUR_API_KEY"

curl "https://geoclear.io/api/address?street=Main+St&city=Austin&state=TX&key=YOUR_API_KEY"

Verify an address in under a minute.

curl "https://geoclear.io/api/address?number=525&street=Lexington+Ave&city=New+York&state=NY" \
  -H "X-Api-Key: YOUR_API_KEY"

const res = await fetch(
  'https://geoclear.io/api/address?number=525&street=Lexington+Ave&city=New+York&state=NY',
  { headers: { 'X-Api-Key': 'YOUR_API_KEY' } }
);
const { data } = await res.json();
console.log(data[0].full_address, data[0].confidence);

import requests

r = requests.get(
    'https://geoclear.io/api/address',
    params={'number': '525', 'street': 'Lexington Ave', 'city': 'New York', 'state': 'NY'},
    headers={'X-Api-Key': 'YOUR_API_KEY'}
)
data = r.json()['data']
print(data[0]['full_address'], data[0]['confidence'])

{
  "ok": true,
  "data": [{
    "full_address": "525 Lexington Ave, New York, NY 10017",
    "add_number": "525",
    "st_name": "Lexington",
    "st_pos_typ": "Ave",
    "st_pre_dir": "",
    "city": "New York",
    "state": "NY",
    "zip_code": "10017",
    "latitude": 40.7556,
    "longitude": -73.9729,
    "county_fips": "36061",
    "timezone": "America/New_York",
    "residential": false,
    "confidence": 96
  }]
}

Limits are enforced per API key. Exceeding either limit returns 429 Too Many Requests.

Rate limit headers are included in every response: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

All errors return a JSON body with ok: false and an error string.

Each error includes a machine-readable Resolution so AI agents and SDKs can self-heal without human intervention. Inspect the response error string for context; the table below tells you what to do.

{
  "ok": false,
  "error": "Invalid or revoked API key."
}

The two most common alternatives, and what's different.

Verification over Information. Every GeoClear REST API response carries a receipt header, a portable operational receipt your team retains alongside retained verification material. Verification runs locally on your infrastructure using that retained material; GeoClear's application servers do not participate in the verification result.

The receipt attests to what GeoClear returned at what moment. It does not attest to the ground-truth correctness of underlying datasets, if an authoritative source updates, your old receipt is still valid; it records what we returned on the day you asked.

Issuance: issued behind the trust boundary; public verification material is published. Substrate detail and rotation cadence are available in the developer integration guide for approved evaluators, /security/whitepaper (NDA).

Install the public verifier package

npm install @geoclear/verify-receipt

Verify, Node.js

const { verifyGeoClearReceipt } = require('@geoclear/verify-receipt');

const claims = await verifyGeoClearReceipt({
  receipt, // value of the receipt response header
  method: 'GET',
  path: '/v1/address?street=...&city=...',
  responseBody, // the JSON body you received
});
// Returns the verified payload object.
// Throws if verification fails or retained evidence does not match.

Other runtimes

Python, Go, Rust, and other-runtime verifier reference implementations are available in the developer integration guide for approved evaluators, /security/whitepaper (NDA). The verification model is the same across runtimes: customer-held verification material + a standard signature library; no GeoClear server participates in the verification result.

Receipt payload shape

The public docs intentionally show the verification model, not the production receipt schema. Receipt payload fields and their semantics are available in the developer integration guide for approved evaluators, /security/whitepaper (NDA).

Try it in your browser: open the live verifier demo on the security page, or click Search on the homepage demo, you'll see the receipt auto-verify in under 100 ms with a tamper-test button.

For regulated workflows and enterprise audit integrations, reach out: hello@geoclear.io.

A GeoClear Evidence Bundle is a customer-held evidence package for verifying a result years later, without calling GeoClear. The bundle contains the operational receipt, retained evidence, verification material, and supporting references needed for later review. Detailed bundle internals (exact file layout, verifier implementation, key-management guidance) are available to qualified evaluators under NDA, see /security/whitepaper.

Bundle contents at a glance

An Evidence Bundle contains the receipt, retained operational evidence, verification material, supporting references, and a self-contained offline verifier. Detailed bundle internals are shared with qualified procurement and security reviewers under NDA, request the developer integration guide.

Verification flow

Open the self-contained offline verifier from the bundle, drop in the bundle files, and the verifier checks the receipt against the retained verification material entirely on your machine. No call to GeoClear required; verification runs locally in your browser.

For a sample bundle you can verify in your browser, see What Is an Evidence Bundle? and the offline verifier. Honesty disclosure (what this proves / does not prove): on the Security page.

Receipt Vault is the productized customer surface for retained operational evidence. It packages every operational receipt into an Evidence Bundle, exposes a list + detail dashboard for retained receipts, and supports per-receipt download for long-lived audit + chargeback investigation. Pro Compliance + Scale + Enterprise tiers.

What Receipt Vault stores

Receipt Vault stores customer-held operational receipt records, retained verification material, and supporting references needed for audit, chargeback review, and long-horizon verification. Detailed retention models and verifier internals are available to qualified procurement and security reviewers under NDA, request the developer integration guide.

What the customer should retain

• The full Evidence Bundle ZIP for every high-stakes verdict (mortgage origination, insurance claim, agentic-commerce settlement).
• A quarterly snapshot of the published verification material (so a 10-year audit doesn’t depend on any single distribution channel being available later).
• The verification material from each bundle (already included in the ZIP, just don’t lose the bundle).

Surfaces

• /vault/payments, payments dashboard (transactional receipts with settlement-pairing view).
• GET /v2/vault/payments, list API, paginated, filterable by tx_hash prefix, merchant_id, date, verdict status.
• GET /v2/vault/payments/:receipt_id/bundle.zip, per-receipt evidence bundle download.
• /security/offline-verifier, verify any bundle ZIP locally in your browser.

Public verification material is published redundantly so a verifier can resolve a key for any historical receipt without depending on a single endpoint, and customers retain a copy in their bundle.

Detailed key-distribution, rotation cadence, and publication-channel topology are available in the Security & Verification Whitepaper under NDA.

What this does not promise

Storage durability is a property of redundant publication + customer-held copies, not a guarantee about the future of any specific service. Customers retain the bundle (Receipt Vault, above) so verification does not depend on any single hosted channel remaining available.