API Reference Overview
The source-verified entry point for the versioned AutoCore API.
Choose the correct endpoint family, authentication mode, and operational boundary before making a request.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The API is REST-shaped, versioned under /api/v1, validated with Zod, and wrapped in a stable error envelope. This reference covers the 403 controller methods audited from the release candidate source.
| Check | Source-backed expectation |
|---|---|
| Scope | API base, versioning, and the public/authenticated/operator split are fixed by the API bootstrap and controller metadata. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -H 'Accept: application/json' https://api.example.invalid/api/v1/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 -H 'Accept: application/json' https://api.example.invalid/api/v1/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.