Operations

AMAI API errors

Most integration failures are simple: missing Bearer token, unpaid checkout, insufficient credits, or a route failover while custom capacity is unavailable.

Enter receipt email before opening Stripe. AMAI uses it for recovery and key claim.

Receipt email Email is required before Stripe so AMAI can send recovery and key-claim email. Buy $10 credits Open AMAI chat Model catalog

Best first purchase

Pick the smallest paid path that proves the AMAI route you need. The same key works in chat and OpenAI-compatible clients after Stripe returns to the claim page.

Smoke test $10 credits for a fast live check against abliterated and heretic. Buy $10 credits

Coding/API integration $100 credits when you are wiring OpenCode, Aider, Continue, Open WebUI, or your own agents. Buy $100 credits

Recurring research work Research Pro for authorized security, life-science literature, and frontier technical workflows. Start Research Pro

Stripe fallbackJavaScript is off. Stripe fallback links remain available; Stripe collects the receipt email and redirects to the AMAI key claim page.

$10 credits Explorer

Configuration

401 or 403: check the AMAI key
402: add credits or open billing
429: slow the agent loop
5xx: retry with request id and route metadata

First run

The gateway blocks unpaid or over-budget requests before provider spend.

Paid before spend

Credits must exist before inference starts. The gateway blocks insufficient-credit requests before provider spend.

Launch models

Use amai-glm-abliterated-v0.1 by default and amai-glm-heretic-v0.1 for heretic candidate search.