01
Compatible by design
Use a documented API base URL and compatible endpoint patterns in tools that support custom configuration.
Developer API access
Bring your tools to a single API surface.
ZOOAPI helps developers connect compatible tools through a documented API path, with account credits, API keys, and subaccounts in one console.
OpenAI-compatible access · documented endpoints · team subaccounts · usage credit management · OpenAI-compatible access · documented endpoints · team subaccounts
Built for the
way developers work.
Start with a familiar request pattern, then manage keys, credits, and team access from the same place.
02
Credits you can track
Review plans, credit balances, and current model availability in the ZOOAPI console.
03
Controls for teams
Use subaccounts and credit management when multiple developers or workflows need access.
From key to first
request in four moves.
Follow the documented path. The console remains the source of truth for model availability, multipliers, inventory, and final prices.
Create an account
Open the console and complete account setup.
Create an API key
Keep the key in an environment variable or secret manager.
Set your base URL
Configure https://api.zooapi.ai in your client.
Make a request
Use the compatible request example in the documentation.
Start with an
answer, not a guess.
Two practical resources for getting integrated and understanding how credits work.
Questions,
answered plainly.
ZOOAPI is an independent service. It is not affiliated with or endorsed by OpenAI.
What is ZOOAPI?
ZOOAPI provides OpenAI-compatible API access with API key, credit, and subaccount management for developer workflows.
How do I connect my application?
Create an API key, set your tool's base URL to the documented ZOOAPI endpoint, and use the compatible endpoint pattern shown in the docs.
Where can I see available models and prices?
The ZOOAPI console displays the currently available models, multipliers, inventory, and final prices.
How should I store my API key?
Use environment variables or a secure secret manager. Do not commit keys to source control or include them in client-side code.
Service compatibility, model availability, and billing conditions can change. Review the console before you deploy a production workflow.