API Base URL and Versioning
How to construct AutoCore API URLs and reason about compatibility.
Use the versioned prefix for application routes and the unversioned probes only for health checks.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The API bootstrap applies /api/v1 globally and excludes /health and /ready. Clients must not infer an unversioned application route from a successful probe.
| Check | Source-backed expectation |
|---|---|
| Scope | The version prefix is an API contract; deployments can change the host without changing the route contract. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i https://api.example.invalid/health |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
curl -i https://api.example.invalid/health
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.