API · Chazz.ai
The Chazz.ai HTTP API: one authenticated JSON endpoint behind a bearer token, the same one the website and every chat-app connector calls. Machine-readable description at /openapi.json.
Chazz.ai exposes one JSON HTTP API at api.chazz.ai. Every surface of the product calls it, including the website and the chat-app connectors, so anything the site can do the API can do. Access is by bearer token issued through single sign-on. A machine-readable description is published at /openapi.json.
Shape
One action-dispatch endpoint taking JSON and returning JSON, plus a small number of streaming and media routes. Authentication is a bearer token in the Authorization header, issued by the platform identity service. Cookies are not used for API authentication, which is why there is no CSRF token to carry.
- Base URL: https://api.chazz.ai
- Auth: Authorization: Bearer <token>
- Content type: application/json
- Streaming: Server-sent events for chat turns
- Realtime: WebSocket for multiplayer, campaign and live avatar rooms
- Machine-readable: https://chazz.ai/openapi.json
Limits, and why they are published
Publishing the limits is deliberate. An undocumented limit is discovered by hitting it, which is indistinguishable from abuse, and a client that cannot see the ceiling writes a retry loop that looks like an attack.
- Per-action rate limits with a 429 and a Retry-After. A client that honours it is never blocked for honouring it.
- Request bodies are size-capped, and a body over the cap is refused rather than truncated.
- List endpoints are page-capped. Asking for a larger page returns the cap, not an error, and never the whole table.
- Priced actions check the wallet before doing the work, and the price is returned with the result.
What it is not
There is no public API key programme yet. Access is through an account, with the same entitlements, credits, moderation and age gating that account has on the website. A key issued to a machine, scoped per permission and rotatable, is the intended shape and is not built.
There is no GraphQL endpoint, so there is no introspection surface to abuse.
Versioning
Actions are additive. An existing action keeps its shape, new fields are optional, and a breaking change ships as a new action name rather than a silent change to an old one. Anything genuinely removed answers 410 rather than 404, so a client can tell "gone" from "typo".
If you are building something
Say hello at [email protected] first. The connectors in integrations are the reference implementations, and they are the fastest way to see the intended shape.
Questions
- Does Chazz.ai have an API?
- Yes. One JSON HTTP API at api.chazz.ai, authenticated with a bearer token, which the website and every connector call. A machine-readable description is at /openapi.json. There is no public API key programme yet.
- Is there a GraphQL endpoint?
- No. The API is JSON over HTTP, so there is no GraphQL introspection surface.
Read next
Last updated: .
Elsewhere on Chazz.ai
- Explore characters
- About
- Features
- Pricing
- Use cases
- Integrations
- Compare
- Documentation
- FAQ
- Changelog
- API
- Security
- Status
- Contact
- Press
- Stories
- Marketplace
- Image generation
- Credits and plans
- Chat app connectors
- Terms
- Privacy
- AI transparency
- Notice to AI agents
This document is the server-rendered form of /api. The interactive page needs JavaScript, and shows the same content.
The complete documentation of this service is available as one plain-text file at /llms-full.txt. A short summary, with the operator's policy for automated readers, is at /llms.txt. Changes are published as a feed at /rss.xml.
Chazz.ai is operated by Cognitive Industries, ABN 62 794 528 747, Australia. Contact: [email protected].