> ## Documentation Index > Fetch the complete documentation index at: https://docs.deapi.ai/llms.txt > Use this file to discover all available pages before exploring further. # Prompt Booster Price > Price of a prompt boost, and a free check that one is possible: it runs the same guide lookup as the boost itself, so a 422 here means the boost would also be rejected. Charges nothing either way. NOTE the response shape differs from every other price endpoint: this one returns `{"price": …}` at the top level, not wrapped in `data`. Calculate the cost of a prompt-booster call before running it. Takes the same fields as the [Prompt Booster](/api/v2/prompt-enhancement/prompt-booster) (`prompt`, `type`, `model_slug`, optional `image` / `negative_prompt`) and returns `{ "price": }`. ## OpenAPI ````yaml openapi-v2.json POST /api/v2/prompts/enhancements/price openapi: 3.1.0 info: title: deAPI REST API description: >- Decentralized AI inference API for image generation, video processing, audio transcription, and more. ## Rate limits Two windows can apply to a request: a per-minute one (RPM) and a per-day one (RPD). Every throttled response — success or 429 — carries the `X-RateLimit-*` headers, so you can pace traffic without waiting to be rejected. Each header documents itself: see `components/headers`, or the headers listed on any response. What follows is only what a header cannot say about itself. Windows open on your first request into a bucket and run their full length from that second — never to a calendar boundary, in any timezone. That is deliberate: a boundary every account shares is a boundary every account can double up on. **The headers describe the pool *this* request landed in, and `X-RateLimit-Source` is what identifies it — not `X-RateLimit-Limit` alone.** A per-model limit is keyed to the model you named, so a request that carried no recognised `model` — rejected at validation, an unknown slug, an empty body — was counted against your tier pool, and it is the tier pool the headers then describe. The two pools are fully independent: separate minute window, separate day, separate `X-RateLimit-Daily-Reset`. This is a consequence of rate limiting running *before* validation, which is what keeps malformed traffic from reaching the rest of the API uncounted. Compare headers only across responses carrying the same `X-RateLimit-Source`. **Buckets are shared in ways worth knowing.** API **v1 and v2 count against the same bucket**, so migrating grants no fresh allowance and mixed traffic behaves as one stream. All `*/price` and `*/price-calculation` endpoints share a single quote bucket, separate from generation. Prompt enhancement (`/v2/prompts/enhancements`) has its own bucket as well, so heavy prompt work no longer eats into your image throughput. **Counting is exact in sequence, best-effort in parallel.** Sent one after another, your requests are counted precisely: the one that crosses the limit is the one that gets 429. Sent in parallel, a few beyond the limit can slip through, because the counter is read and then incremented as two steps and requests already in flight are not yet visible to one another. The excess is bounded by how many of your own requests are in flight at once, and it only ever runs in your favour — you are never rejected while below your limit. So do not treat `X-RateLimit-Remaining` as a reservation: it is a snapshot, and a request you sent a millisecond ago may already have spent what it shows. Requests rejected before authentication (HTTP 401) never reach the limiter and carry no rate-limit headers at all. contact: name: deAPI Support url: https://deapi.ai email: support@deapi.ai version: 0.0.1 servers: - url: https://api.deapi.ai description: Production API Server base URL security: - bearerAuth: [] tags: - name: Client API v2 description: Current client endpoints (OpenAI-aligned noun-based paths) paths: /api/v2/prompts/enhancements/price: post: tags: - Client API v2 summary: Estimate prompt enhancement price description: >- Price of a prompt boost, and a free check that one is possible: it runs the same guide lookup as the boost itself, so a 422 here means the boost would also be rejected. Charges nothing either way. NOTE the response shape differs from every other price endpoint: this one returns `{"price": …}` at the top level, not wrapped in `data`. operationId: clientCalculateBoostPriceV2 requestBody: required: true content: multipart/form-data: schema: properties: prompt: type: string example: A beautiful landscape minLength: 3 negative_prompt: type: - string - 'null' example: blurry, low quality minLength: 3 type: description: >- Inference type, v2 dot notation. Only prompt-driven types are boostable. type: string example: images.generations enum: - images.generations - images.edits - videos.generations - videos.animations - audio.speech - audio.music model_slug: type: string example: Flux1schnell image: description: Reference image (for price estimation of image-based types). type: - string - 'null' format: binary type: object responses: '200': description: Price calculation returned successfully headers: X-RateLimit-Policy: $ref: '#/components/headers/X-RateLimit-Policy' X-RateLimit-Source: $ref: '#/components/headers/X-RateLimit-Source' X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' X-RateLimit-Daily-Limit: $ref: '#/components/headers/X-RateLimit-Daily-Limit' X-RateLimit-Daily-Remaining: $ref: '#/components/headers/X-RateLimit-Daily-Remaining' X-RateLimit-Daily-Reset: $ref: '#/components/headers/X-RateLimit-Daily-Reset' content: application/json: schema: properties: price: type: number format: float example: 0.00012345 type: object '422': $ref: '#/components/responses/ValidationError' description: >- Validation failed, or the model is not available on your plan. In the last case the error is reported on the "model_slug" field (not "model") with the message "This model is not available on your plan. Please upgrade to access it." '429': $ref: '#/components/responses/RateLimitExceeded' security: - bearerAuth: [] components: headers: X-RateLimit-Policy: description: >- Every window that applies, as `;w=` elements. Always present on a throttled response, so a single element means there is no daily limit — do not infer that from the absence of the Daily-* headers. `300;w=60` is minute-only; `3;w=60, 100;w=86400` is both. schema: type: string example: 3;w=60, 100;w=86400 X-RateLimit-Source: description: >- Where the limit came from, so you know what would change it: `tier` — your account tier's rate for this endpoint; `fallback` — no rate configured for this tier and endpoint, degraded default in force; `model` — a per-model override for the model in the request, unaffected by your tier (only when the request carried a recognised `model`, otherwise the tier pool applies); `static` — a flat limit outside the tier system, identical for every account. If you ever see `fallback`, tell us: it means no rate is configured for that tier and endpoint. schema: type: string example: tier enum: - tier - fallback - model - static X-RateLimit-Limit: description: Maximum requests allowed per minute (RPM) schema: type: integer example: 3 X-RateLimit-Remaining: description: Remaining requests in current minute window schema: type: integer example: 2 X-RateLimit-Reset: description: >- Epoch second at which the minute (RPM) window refills. Fixed window — the value does not drift as you spend the quota. Describes the same window as X-RateLimit-Limit, including on a daily rejection. schema: type: integer example: 1755800460 X-RateLimit-Daily-Limit: description: Maximum requests allowed per day (RPD) schema: type: integer example: 100 X-RateLimit-Daily-Remaining: description: Remaining requests in current day window schema: type: integer example: 95 X-RateLimit-Daily-Reset: description: >- Epoch second at which the daily (RPD) window refills — 86400 s after the first request that opened this bucket's window, not a calendar midnight. Present only when a daily limit applies. schema: type: integer example: 1755846000 X-RateLimit-Type: description: >- Which limit rejected the request. Sent only on 429. Read it before anything else on the response: it decides what the other `X-RateLimit-*` headers are counting. `minute` — the per-request RPM window. `daily` — the per-request RPD window; the Daily-* pair is the one at 0. `key-creation` — the hourly cap on keys created over the API (`POST /api/v2/keys`), per account and shared by its ADMIN keys. The whole `X-RateLimit-*` set describes that bucket and there are no Daily-* headers. `ip-not-allowed` — too many calls from an address your key's IP whitelist refuses. Counted against that address, never against your account. schema: type: string example: minute enum: - minute - daily - key-creation - ip-not-allowed Retry-After: description: >- Seconds until the window that rejected you frees up (60 for minute, up to 86400 for daily). Counted from when that window opened, not to a calendar boundary. Sent only on 429. schema: type: integer example: 60 responses: ValidationError: description: >- Validation failed. Common errors include: model does not exist, model does not support the inference type for this endpoint, the model is not available on your plan (it requires a higher tier than your account has — upgrade to use it), or invalid request parameters. content: application/json: schema: properties: message: description: General error message type: string example: The selected model does not support Text To Image. errors: description: >- Detailed validation errors by field. A model your plan does not cover is reported on the "model" field with the message "This model is not available on your plan. Please upgrade to access it." Such a model is also omitted from GET /models. type: object example: model: - >- This model is not available on your plan. Please upgrade to access it. type: object RateLimitExceeded: description: >- Rate limit exceeded. Check X-RateLimit-Type header to determine if minute (RPM) or daily (RPD) limit was hit. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Daily-Limit: $ref: '#/components/headers/X-RateLimit-Daily-Limit' X-RateLimit-Daily-Remaining: $ref: '#/components/headers/X-RateLimit-Daily-Remaining' X-RateLimit-Type: $ref: '#/components/headers/X-RateLimit-Type' Retry-After: $ref: '#/components/headers/Retry-After' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' X-RateLimit-Daily-Reset: $ref: '#/components/headers/X-RateLimit-Daily-Reset' X-RateLimit-Source: $ref: '#/components/headers/X-RateLimit-Source' X-RateLimit-Policy: $ref: '#/components/headers/X-RateLimit-Policy' content: application/json: schema: $ref: '#/components/schemas/response_error_rate_limit' schemas: response_error_rate_limit: description: Rate limit exceeded response properties: message: description: Error message type: string example: Too Many Attempts. type: object securitySchemes: bearerAuth: type: http description: >- Sanctum personal access token, sent as `Authorization: Bearer `. The token is opaque — it carries no claims and no embedded expiry, so do not attempt to decode it. Issue and revoke tokens from your account dashboard. scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.