Reference
Use reference documentation when you need an exact Drift contract rather than a guided procedure or design rationale. These pages define inputs, outputs, defaults, invariants, ownership, limits, and failure behavior.
- API reference — routes, authentication, scopes, request rules, and errors.
- Data model — persisted tenants, API keys, vertices, edges, and their fields.
For writing and reviewing documentation itself, use the documentation style and review guide.