Admin API Endpoint Boundary
How operator-sensitive routes are documented without exposing control-plane details.
Use the Admin client and approved permissions; do not treat this page as an operator runbook.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The audit identifies 228 operator-sensitive methods, primarily under /admin and admin controller files. Public documentation records the boundary, permission model, and safe response expectations; live identifiers, private hosts, and escalation details remain excluded.
| Check | Source-backed expectation |
|---|---|
| Scope | Operator access is approval-gated and should be tested with disposable fixtures. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i -H 'Authorization: Bearer [operator-token]' https://api.example.invalid/api/v1/admin/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 -H 'Authorization: Bearer [operator-token]' https://api.example.invalid/api/v1/admin/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.