https://api.deapi.ai and require authentication via Authorization: Bearer <API_KEY> header.
Each generation/analysis endpoint has a corresponding
/price-calculation endpoint to estimate costs before execution.Relationship to v2
v1 and v2 are two request surfaces over the same inference backend. For endpoints that exist in both, the request fields, validation rules and validation messages are identical, and jobs are stored in a single namespace — arequest_id returned by a v1 endpoint can be polled with GET /api/v2/jobs/{request_id}, and a request_id returned by a v2 endpoint can be polled with GET /api/v1/client/request-status/{request_id}.
The practical differences are naming and grouping: v1 uses one flat /api/v1/client/<task> namespace with /price-calculation suffixes, while v2 groups endpoints by media type (/api/v2/images/*, /api/v2/videos/*, /api/v2/audio/*) with /price suffixes, and consolidates several v1 endpoints into unified ones (all transcription endpoints into /api/v2/audio/transcriptions, all prompt boosters into /api/v2/prompts/enhancements).
Generation
Create images, videos, audio, and embeddings from text or images.Analysis
Extract text and transcriptions from images, videos, and audio.Transformation
Modify existing images and videos.Utilities
Account management and job status tracking.Workflow
Typical API usage follows this pattern:1
Check available models
Call
GET /api/v1/client/models?limit=50 to get current models and their parameters. That covers the whole catalogue in one call — the page size defaults to 50, and meta.last_page reading 1 is what confirms nothing is missing.2
Calculate price (optional)
Call the
/price-calculation endpoint with your parameters to estimate cost.3
Submit job
Call the main endpoint (e.g.,
POST /api/v1/client/txt2img) with your parameters. Response contains request_id.4
Poll for results
Call
GET /api/v1/client/request-status/{request_id} until status is done or error.5
Download result
When
status is done, use result_url to download your generated content.Response Formats
Response structure varies by endpoint. See individual endpoint documentation for exact schemas.