ACAAS uses standard HTTP status codes. Successful requests returnDocumentation Index
Fetch the complete documentation index at: https://acaas.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
200.
Anything else falls into one of the categories below. All error responses are
JSON.
Error response shape
Validation errors follow FastAPI’s standard envelope: a top-leveldetail
array describing each problem.
loc— path to the offending field, from the request root.msg— human-readable message.type— machine-readable error type, suitable for branching logic.input(optional) — the rejected value, when the server can echo it back.ctx(optional) — extra context, such as the boundary that was violated.
401, 413, 429, 5xx) return a simpler shape with
a single detail string.
Status codes
200 OK
The request succeeded. Every capitalization endpoint returns the shout response envelope;/v1/emphasize returns the
emphasis envelope.
401 Unauthorized
TheX-API-Key header is missing, malformed, or revoked. The demo key
acaas_banned_demo_key always returns 401 — it had its bullhorn revoked.
X-API-Key. Confirm the value is non-empty. In production, rotate the key
from the dashboard.
413 Payload Too Large
Thetext field exceeds 10,000 characters. ACAAS will not amplify what it
cannot lift.
/v1/shout (or any
capitalization endpoint) per chunk, and concatenate the results. Case
conversion is per-character, so chunked output equals single-call output.
422 Unprocessable Entity
The body is valid JSON but failed schema validation. Common causes:textis missing or empty.intensity(on/v1/scream) is outside1..10.emphasis_ratio(on/v1/emphasize) is outside(0, 1].
loc to find the bad field, surface msg to the
user (or log it), and resubmit with a valid value. Treat type as a stable
key for client-side branching.
429 Too Many Requests
You have exhausted your quota for the current rate limit window. ACAAS will not serve another request until the window resets./v1/rate-limits to
see how long until the window resets, then retry after that interval. For
guidance on graceful backoff, see Rate limiting.
5xx Server Errors
Something went wrong on the ACAAS side. These are rare but possible during deployments or upstream model incidents (the latter affecting/v1/emphasize
specifically).
How to recover. Retry with exponential backoff — start at one second,
double on each attempt, cap at sixty seconds. Stop after five attempts and
surface the failure. Check the status page
if retries continue to fail.
Handling errors in code
A defensive pattern that handles all the above:Next steps
Rate limiting
Quota mechanics, the
status ladder, and graceful backoff.Quickstart
Make your first ACAAS request in under a minute.