Data & API

RoboZaps maintains a source-backed robot database. Each sourced specification records its source and, where available, a verification tier and confidence score. The data ships in two layers.

Two access layers

• Headline layer — no key

  Identity, deployment stage, price ranges, and headline specs (height, weight, payload, speed, battery, DoF, reach) via the list endpoint and keyless per-robot detail. Licensed under the RoboZaps Data Terms below.

• Depth layer — free API key; bulk exports — Pro API key

  Full normalized specs with per-spec source links, verification tiers, and confidence scores, plus deployment evidence, readiness scores, and the bulk dataset downloads. Licensed under the RoboZaps Data Terms below.

Endpoints

All endpoints are read-only and allow cross-origin requests. Keyless endpoints are cached for one hour and rate-limited to 60 requests per hour per IP. Verifying a key against the backend has its own per-IP ceiling of 600 requests per hour, separate from the keyless budget. A key we've never seen before spends one unit the first time it's checked; an invalid key spends it every time after that too, whether discovered fresh or replayed from cache. A key already known valid never spends it again on a recheck, so many already-active keys sharing one IP can't lock each other out. A valid key denied at an endpoint it isn't entitled to (e.g. a free key on change history) is rate-limited on its own per-key budget, separate again. Keyed access allows 500 detail requests and 5 dataset exports per day per key — enough to evaluate the data; talk to us about anything heavier. Change history (/api/v1/changes) has its own budget of 2,000 requests per day per key, separate from the detail budget, since paging the feed takes far more requests than looking up individual robots. Send your key as the x-api-key header — a key sent via the query string is rejected and is never rate-limited (it costs nothing to reject). An old, superseded catalog slug's redirect and a missing key's 401 are likewise never rate-limited — both are resolved before any backend call, so there is nothing to protect a budget from.

• /api/v1/robots

  List of published robots (headline fields). Query params: manufacturer, stage, verification, limit (max 25), offset. Keyless, rate-limited.

• /api/v1/robots/<slug>

  Per-robot detail. Without a key: headline layer (identity + headline specs). With a free API key: full depth layer — every current spec with its source link, verification tier, and confidence score, plus deployment evidence and readiness.

• /api/v1/dataset.json

  The published catalog in one JSON document: identity plus headline specs per robot. Requires a Pro API key.

• /api/v1/dataset.csv

  The published catalog as CSV — one row per robot with core fields and common spec columns. Requires a Pro API key.

• /api/v1/changes

  Change history and events across the catalog — price moves, availability, deployments, and spec corrections. Only the listed filters (cursor, limit up to 100, target_type, target_id, since, manufacturer, materiality) are forwarded; any other query param is silently dropped. Requires an API key issued from a signed-in account on the Pro plan. History beyond the most recent 30 days is available now through this Pro API; the same unlock on the site with a Pro account is coming once account history ships.

{
  "events": [
    {
      "id": "fcl:1234",
      "event_type": "price",
      "target_type": "robot",
      "target_id": "robot_01",
      "target_slug": "unitree-g1",
      "target_name": "Unitree G1",
      "manufacturer_slug": "unitree",
      "field_key": "price",
      "field_label": "Price",
      "old_value": "USD 15000",
      "new_value": "USD 16000",
      "effective_date": "2026-09-01",
      "recorded_at": "2026-09-20T00:00:00.000Z",
      "source_url": "https://unitree.com/g1",
      "source_publisher": "unitree.com",
      "materiality": "major",
      "verification_state": "verified"
    }
  ],
  "next_cursor": null,
  "license": "RoboZaps Data Terms — attribution required; ...",
  "docs": "https://robozaps.com/data"
}

{
  "error": "upgrade_required",
  "message": "Change history and events are available on the Pro plan. Upgrade to unlock full per-entity history via the API.",
  "upgrade_url": "https://robozaps.com/pricing"
}

Get a free API key

Keys are free and issued instantly. Tell us what you are building so we can keep the data useful for it.

Licenses & terms

All layers are licensed under the RoboZaps Data Terms: attribution required, internal and research use welcome, replication, bulk redistribution, or resale of the corpus prohibited. Keys may be revoked for abuse. Every price is an observed list or asking price with source and date, not an offer.

The same terms cover the Pro plan's own export surfaces: the /app watchlist's CSV export and the /api/v1/changes change-history API for Pro keys — attribution required, internal and research use welcome, replication, bulk redistribution, or resale of the corpus prohibited, whether you hold the data as a CSV file, an API response, or a copy of either.

Releases before 2026-07-23 were licensed CC BY 4.0, which remains irrevocable for copies retrieved before that date. Releases on or after 2026-07-23 are licensed under the RoboZaps Data Terms.

Citation

Cite individual robot records as:

RoboZaps Robot Database, robozaps.com/products/<slug>, retrieved <date>

For AI agents

A machine-readable overview of the site and its entry points is published at /llms.txt.

Contact

Questions, corrections, or bulk-use requests: use the contact page.