Codex HTTP API
Rust implementation surfaces live in vox-db (Codex schema, readiness, store ops). There is no separate vox-codex-api workspace crate; operators integrate HTTP routers built on vox_db types (see OpenAPI below).
SSOT
- OpenAPI 3 —
contracts/codex-api.openapi.yaml(validated byscripts/check_codex_ssot.ps1).
Tests
cargo test -p vox-db— integration tests undercrates/vox-db/tests/(e.g.ops_codex_tests.rs) exercise Codex HTTP / store behavior where applicable.
Defaults
| Item | Value |
|---|---|
| Bind | VOX_DASH_HOST (default 127.0.0.1) + VOX_DASH_PORT (default 3847) when a dashboard-compatible server is run |
| Readiness | GET /ready uses vox_db::evaluate_codex_api_readiness (baseline schema_version 1 + required tables + manifest digest) |
Speech ingress (/api/audio/*)
OpenAPI paths GET /api/audio/status, POST /api/audio/transcribe, POST /api/audio/transcribe/upload are implemented by the vox-audio-ingress binary (crates/vox-audio-ingress): Oratio STT on paths under VOX_ORATIO_WORKSPACE (or process CWD) or multipart upload. Same bind vars as the table above. This is separate from Codex CRUD routes but lives in the shared contracts/codex-api.openapi.yaml catalog for client codegen.
Related
- Environment variables (SSOT) —
VOX_DASH_*, Codex DB envs - Codex BaaS scaffolding
- Codex vNext schema
- Nomenclature migration map — retired
vox-codex-apiname