openapi.json. The generated pages include request parameters, schemas, responses, and API examples.
Base URL
/v1. Health endpoints use /health.
Endpoint map
Decisions
Models
Catalogs
Health
HTTP conventions
- Requests with JSON bodies use
Content-Type: application/json. - Successful responses are JSON except
204 No Contentfor a successful catalog delete. - Error responses use an
{ "error": { ... } }envelope. - Responses may include
X-Request-IDfor support and tracing. - Rate-limited responses may include
Retry-Afterand rate-limit headers.
Generated API pages
Select an operation in the sidebar to view its full contract. The API reference is the source of truth for exact field names, required properties, response codes, and model schemas. If the narrative guide and the generated schema ever disagree, treat the OpenAPI contract as authoritative and open an issue with the request ID or affected operation.The free decision and model endpoints require no API key. Catalog operations are protected and require a bearer key. This API reference describes HTTP access to Aspas Labs; it does not describe a dashboard or hosted UI because those surfaces do not exist yet.