# Cite DEPLOY

DEPLOY is the verified record of physical AI. Researchers, journalists, and analysts are welcome to cite DEPLOY. This page explains how.

When citing DEPLOY data, the distinction between verified and claimed metrics is part of what is being cited. Preserve that distinction in your citation, and your reporting will inherit the same provenance discipline.

## How to cite the registry

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.

### The registry as a whole

**APA**

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

**MLA**

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

**Chicago**

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

**BibTeX**

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

### An individual entity, deployment, or comparison page

Substitute the page's title and canonical URL. Every entity has a stable slug-based URL and a dated .md mirror.

**APA**

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

**MLA**

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

**Chicago**

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

**BibTeX**

```bibtex
@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}}
}
```

## 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.

- `/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}` comparison page (e.g., /waymo-vs-tesla)
- `/glossary` canonical vocabulary

Every page above has a .md mirror at the same URL with `.md` appended (for example, `/companies/figure-ai.md`). 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 the registry; 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 registry vocabulary, see [how DEPLOY verifies](/methodology.md) and [the glossary](/glossary.md).

## 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](/data.md): REST API endpoints under `/v1/`, .md mirrors of every page, 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 example

A concrete BibTeX entry citing the Waymo San Francisco marquee deployment page, showing the format a researcher would actually copy into a bibliography file:

```bibtex
@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-28},
  organization = {{DEPLOY}}
}
```

For machine-readable citation, append `.md` to the URL: `/deployments/marquee/waymo-san-francisco.md`.

_Canonical URL: /cite. JSON-LD and HTML version: [/cite](/cite)._