Cite DEPLOY

Three properties to cite

DEPLOY publishes from three URL apexes. Citation should match the property you are quoting:

• deploy.report — the consumer surface. Verified-vs-claimed buyer view of humanoid robots: model pages, listings, comparisons, browse by need.
• registry.deploy.report — the registry. Queryable knowledge base of every robot, company, deployment, location, incident, and regulation, plus the /v1/ API.
• news.deploy.report — the DEPLOY publication. Articles, signals, explainers, and curated topics. Cite per the publication's own conventions; that guide is separate from this one.

How to cite

Use these ready-to-copy formats. Replace the bracketed access date with the date you retrieved the content; DEPLOY pages have stable URLs and dated .md mirrors, so the access date is the only volatile field. DEPLOY is the author and publisher in all formats.

(a) The registry as a whole

APA

DEPLOY. (2026). DEPLOY: the registry of physical AI. Retrieved May 29, 2026, from https://registry.deploy.report

MLA

"DEPLOY: the registry of physical AI." DEPLOY, 2026, registry.deploy.report. Accessed 29 May 2026.

Chicago

DEPLOY. "DEPLOY: the registry of physical AI." Accessed May 29, 2026. https://registry.deploy.report.

BibTeX

@misc{deploy_registry,
  author       = {{DEPLOY}},
  title        = {{DEPLOY: the registry of physical AI}},
  year         = {2026},
  url          = {https://registry.deploy.report},
  note         = {Accessed: 2026-05-29},
  organization = {{DEPLOY}}
}

(b) The consumer surface as a whole

APA

DEPLOY. (2026). DEPLOY: humanoid robots in 2026. Retrieved May 29, 2026, from https://deploy.report

BibTeX

@misc{deploy_consumer,
  author       = {{DEPLOY}},
  title        = {{DEPLOY: humanoid robots in 2026}},
  year         = {2026},
  url          = {https://deploy.report},
  note         = {Accessed: 2026-05-29},
  organization = {{DEPLOY}}
}

(c) An individual entity, deployment, comparison, or consumer page

Substitute the page's title and canonical URL. The host depends on which property the page lives on: registry entity pages (/companies/{slug}, /models/{slug}, /deployments/{slug}, etc.) live at registry.deploy.report; consumer pages (/listings, /models/{slug}, /compare/{slugs}, /needs/{slug}) live at deploy.report.

APA (registry entity)

DEPLOY. (2026). [Page title]. Retrieved [Month Day, Year], from https://registry.deploy.report/[canonical-path]

APA (consumer page)

DEPLOY. (2026). [Page title]. Retrieved [Month Day, Year], from https://deploy.report/[canonical-path]

MLA (registry entity)

"[Page title]." DEPLOY, 2026, registry.deploy.report/[canonical-path]. Accessed [Day Mon. Year].

MLA (consumer page)

"[Page title]." DEPLOY, 2026, deploy.report/[canonical-path]. Accessed [Day Mon. Year].

Chicago (registry entity)

DEPLOY. "[Page title]." Accessed [Month Day, Year]. https://registry.deploy.report/[canonical-path].

Chicago (consumer page)

DEPLOY. "[Page title]." Accessed [Month Day, Year]. https://deploy.report/[canonical-path].

BibTeX (registry entity)

@misc{deploy_[short-slug],
  author       = {{DEPLOY}},
  title        = {{[Page title]}},
  year         = {2026},
  url          = {https://registry.deploy.report/[canonical-path]},
  note         = {Accessed: [YYYY-MM-DD]},
  organization = {{DEPLOY}}
}

BibTeX (consumer page)

@misc{deploy_[short-slug],
  author       = {{DEPLOY}},
  title        = {{[Page title]}},
  year         = {2026},
  url          = {https://deploy.report/[canonical-path]},
  note         = {Accessed: [YYYY-MM-DD]},
  organization = {{DEPLOY}}
}

Persistent URL conventions

DEPLOY URLs are designed for durable citation. The slug-based paths listed below do not change. Once a record is published at a URL, that URL is the canonical address for that record.

Registry (registry.deploy.report)

• /companies/{slug} company entity
• /models/{slug} robot model entity
• /deployments/{slug} deployment record
• /deployments/marquee/{slug} marquee deployment narrative
• /incidents/{slug} incident record
• /locations/{path} location with hierarchical path
• /regulations/{slug} regulation record
• /{comparison-slug} registry comparison page (e.g., /waymo-vs-tesla)
• /glossary canonical vocabulary

Consumer surface (deploy.report)

• / consumer landing
• /listings consumer-listed humanoid index
• /models/{slug} consumer model page (verified-vs-claimed view)
• /compare/{slugA}-vs-{slugB} consumer comparison (2-to-4 models, alphabetical canonical)
• /needs/{slug} robots claiming to serve a specific need

Every page above has a .md mirror at the same URL with .md appended (for example, /companies/figure-ai.md on the registry, or /models/1x-neo.md on the consumer surface). The .md mirror is the canonical machine-citable version of any page: pure markdown, no client-side JS, stable structure across renders. For citations consumed by AI agents or imported into reference managers programmatically, the .md mirror is the recommended form.

What "verified" means for citation

DEPLOY draws an explicit line between what has been verified against primary sources and what is reported as company-claimed. When citing a DEPLOY data point, note which side of that line the data point sits on. The verified-vs-claimed distinction is the load-bearing editorial discipline of DEPLOY; preserving it in your citation keeps your reporting honest about what is and is not established.

For the strict bar behind verified deployments, fleet counts, incidents, and other DEPLOY vocabulary, see how DEPLOY verifies and the glossary.

For journalists

DEPLOY data is freely usable with attribution. The verified-vs-claimed distinction matters for accurate reporting: when a number on DEPLOY is marked as company-claimed rather than verified, that framing is part of the data, and reporting it without the framing strips the claim of its provenance context.

Press contact: hello@deploy.report.

For researchers and data users

Structured access to the registry is documented at /data: REST API endpoints under /v1/ on registry.deploy.report, .md mirrors of every page on both surfaces, JSON-LD embedded in HTML for structured-data extraction, and per-entity plus firehose RSS for change tracking. Bulk access for research use cases beyond what the documented surfaces cover is available on request.

Researcher contact: hello@deploy.report.

Worked examples

A registry deployment record and a consumer model page, in the format a researcher would actually copy into a bibliography file:

@misc{deploy_waymo_san_francisco,
  author       = {{DEPLOY}},
  title        = {{Waymo San Francisco: deployment record}},
  year         = {2026},
  url          = {https://registry.deploy.report/deployments/marquee/waymo-san-francisco},
  note         = {Accessed: 2026-05-29},
  organization = {{DEPLOY}}
}

@misc{deploy_1x_neo,
  author       = {{DEPLOY}},
  title        = {{1X NEO: consumer model page}},
  year         = {2026},
  url          = {https://deploy.report/models/1x-neo},
  note         = {Accessed: 2026-05-29},
  organization = {{DEPLOY}}
}

For machine-readable citation, append .md to either URL (e.g., /deployments/marquee/waymo-san-francisco.md or /models/1x-neo.md).