Create Seo Fix Content Route
S4’s in-product Create Content submission (PR13).
Reuses TaskCreate — the exact schema POST /tasks accepts — and
mirrors that route’s Task-construction + admin-visibility-gate + Redis
pipeline dispatch, so this behaves identically to the marketplace
wizard’s /tasks/new path. Two additions only: the ai_seo_fixes
entitlement gate (raises BiLimitExceeded -> HTTP 402 the frontend’s
BiPaywallDialog renders) runs BEFORE anything is persisted, and the
created Task is stamped is_bi_seo_fix_request=True so
count_ai_seo_fixes_this_month counts only submissions that came
through here. BotIdGuard (the public /tasks route’s bot defense)
is intentionally absent — this route is authenticated, brand-scoped,
and already gated by the entitlement check, a different threat surface
than the anonymous-reachable marketplace form.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Task category from the taxonomy
Specific task type within category
3 <= x <= 30020050000 <= x <= 1Response
Successful Response