Skip to main content

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.

Verification methodology

RoboZaps keeps the displayed value, its supporting evidence, and its freshness separate. A linked source alone does not make an entire robot record verified.

Verified
Every usable current specification has linked evidence and a recorded verification date.
Partially verified
At least one current specification is sourced or checked, but the record is not fully evidenced.
Unverified
No usable current specification has linked evidence; unsourced values remain visible as unverified.
Conflicting
A current specification has a contradiction flag. Differing public values are also shown as conflicting at the field level; no conflict is silently resolved.

Prices are shown only from a sourced, checked list-price observation or from a verified record; otherwise they are shown as “Price not publicly disclosed.” Freshness is tracked separately: records checked more than 180 days ago are classified as stale, while records without a check date remain unknown.

Two access layers

  • Open headline layer — no key

    Identity, deployment stage, price ranges, and headline specs (height, weight, payload, speed, battery, DoF, reach) via the list endpoint and the bulk dataset. Licensed CC BY 4.0 — attribution: RoboZaps (https://robozaps.com): use, share, and adapt the data, including commercially, with credit and a link back to robozaps.com.

  • Depth layer — free API key

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

Endpoints

All endpoints are read-only and allow cross-origin requests. Open endpoints are cached for one hour.

  • /api/v1/robots

    List of published robots (headline fields). Query params: manufacturer, stage, verification, limit (default 50, max 200), offset. Open, no key.

  • /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. Open, no key.

  • /api/v1/dataset.csv

    The published catalog as CSV — one row per robot with core fields and common spec columns. Open, no key.

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

The open headline layer is licensed CC BY 4.0 — attribution: RoboZaps (https://robozaps.com). The depth layer is licensed under the RoboZaps Data Terms: attribution required, internal and research use welcome, 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.

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.