Versioning, changes, and support
Track v1 behavior, evaluate changes, and send a useful support report safely.
- Audience
- Developers and integration owners
- Before you start
- An inventory of the API operations and response fields your integration depends on
The v1 contract
Current public routes live under /api/public/v1. Integrate only against fields, statuses, and headers described by OpenAPI; ignore additional fields so compatible additions do not break your client. Do not depend on exact message text, JSON property order, or problem UUIDs.
An incompatible change requires a new route version or a communicated migration. Security, correctness, and availability fixes may ship within v1 when they do not change the documented contract.
Deprecation notices
Deprecations will be announced on this page and, for partners with a contractual contact, through the agreement’s channel before the prior version is removed. There is no public minimum notice period; a commercial agreement controls when it specifies one. Keep a current technical contact.
Changelog
| Date | Change | Impact |
|---|---|---|
| 2026-07-20 | Block billing | Completed generations use one credit per exercise; failures reverse the reservation. |
| 2026-07-20 | Header units | Prepaid credits and quota problems are documented separately. |
| 2026-07-20 | Embeds | Minting settles atomically; public URLs, optional CSP, answers, and five-minute caching are documented. |
| 2026-07-20 | Bilingual documentation | EN/ES quickstart, reference, recipes, errors, examples, and downloads were published. |
Get support
Email admin@overthemathwall.com. Include the goal, method/path, UTC timestamp, environment, status, error.code, usage headers, and visible key prefix. State whether the outcome was ambiguous and whether you retried the request.
Also review the API Terms and download the current OpenAPI contract.