Sign in

v1

latestOpenAPI 3.1.02026-07-26151126273.9 KB
Custom Pipelines (Deprecated)

Get Creation Allowance

2026 custom-processor CREATION allowance preview for the current team (§5).

The frontend reads this BEFORE creating a NEW processor to show the at-cap block (Free / developer hard cap) or the one-time $5 confirmation (Team).

NOTE: the path is registered BEFORE /custom_pipelines/{lookup_key} so the literal "creation-allowance" segment is matched by this route, not captured as a lookup_key.

get/api/v1/custom_pipelines/creation-allowance

Cookies

wos-sessionstring
datalab_active_teamstring

Response

Successful Response

creations_this_cycleinteger required

Successful NEW-processor creations counted this billing month

limitinteger required

Included creations per month for the team's plan (or per-team override)

at_capboolean required

True when a hard-cap plan has used all its included creations (next creation is blocked with 402)

will_incur_feeboolean required

True when the next creation would incur the one-time overage fee (Team)

fee_centsinteger required

The one-time fee in cents the next creation would incur (0 when within the allowance or hard-capped)

overage_unit_fee_centsinteger

The plan's per-extra-creation fee in cents regardless of current count (0 for hard-cap plans) — lets the UI state the overage policy up front

planstring nullable

The plan whose limits apply (the team's active API plan, else 'free')

cycle_resets_atstring required

ISO timestamp when the monthly creation count resets