Start with the quickest path
Use Quick Start when you want the shortest route to an image generation request, then open API Reference for exact request bodies, response shapes, headers, and errors.
Appearance
Skip to content01 02 03 04 05 06
Pixapi Developer Docs
One API key for image and video generation models. Compatible with OpenAI-style APIs, provider routing, and credit-aware billing.
Quick StartMake your first request in cURL, Python, JavaScript, Go, Java, or PHP.API ReferenceEndpoints, request bodies, response shapes, and errors.Model CatalogImage and video generation models behind one interface.Billing and creditsUnderstand credit usage, billing errors, and account balances.Async TasksRun long image and video jobs without blocking user requests.
Best integration
Developer-first, production-ready
Pixapi keeps provider details behind a stable API surface. Your team can ship against one request format while managing model vendors, usage tracking, and billing policy from the platform layer.
One keyIssue one Pixapi key and avoid exposing provider credentials.
One billNormalize usage into credits across models and modalities.
One migration pathMove between compatible APIs without rewriting product code.
Docs workflow
How to use the Pixapi API docs
The Pixapi API docs are written for teams that need to move from a first request to a production workflow quickly. The guide is organized around real product tasks: image generation, image editing, video generation, async tasks, billing, and model selection all connect back to the same account and credit system.
Confirm endpoint behavior
Before coding, check which endpoints are synchronous, which are async-only, which field carries the model id, and how generated assets are returned.
Compare models before launch
Use the Model Catalog to compare Gemini image models, Nano Banana aliases, GPT Image models, Veo, Wan, and other supported routes.
Design for async work
Read the Async Tasks guide when a workflow may take longer than a normal request. Video generation and large media jobs should be submitted as tasks, then polled through the task endpoint.
Plan credits and access
Review Billing and Credits before opening a feature to users. Credits connect model cost to outputs, quality, resolution, duration, and provider-specific settings.
Give agents current sources
Pixapi exposes llms.txt and llms-full.txt so coding agents can follow current endpoint names, model ids, and async patterns.
Operational map for visual AI features
Use these pages to choose a model, price the workflow, write the request, handle the response, monitor the task, and support the customer. When one prototype grows into several visual AI features, the docs keep integrations aligned under one API key, one credit ledger, and one developer workflow.