🟢 Operations Page

Status and operational communication

This public page explains what operational areas matter, how issues are communicated, and where customers should go when they need support.

Operational areas

API request handling

Request acceptance, auth validation, and service routing.

Async generation jobs

Queueing, job progression, and result delivery for longer-running tasks.

Dashboard and billing

Account access, usage visibility, and billing-related platform actions.

Documentation access

Public docs availability and developer onboarding paths.

How issues are communicated

  • • Public status updates should summarize impact area and expected next action.
  • • Support requests should include endpoint, request timing, and affected workflow.
  • • Pricing and billing questions should be separated from incident or runtime issues.