Skip to main content

Concurrency Quotas & Rate Limiting

The platform allocates the following limits per account, based on the plan tier:
Actual limits depend on your plan. If your business needs higher concurrency, submit an upgrade request via Profile → Plans, or contact sales.
Rate-limit mitigation patterns:
  1. Use a local client queue + token bucket to control the send rate
  2. Apply exponential backoff retry on 429
  3. Use WebHook for long tasks to avoid occupying HTTP connections

Data Retention & Security

Download important results to your own storage within 15 days. No recovery service is provided after expiry.

Content Moderation

The platform performs automatic content moderation on input prompts, uploaded images, and generated results:
  • audit_status: 1 Not reviewed (should not appear in terminal-state tasks)
  • audit_status: 2 Approved
  • audit_status: 3 Rejected; result is inaccessible
  • audit_status: 4 Moderation error (e.g., input inaccessible)
Tasks that fail moderation will still incur inference-time charges — filter sensitive prompts at the business layer in advance.

Billing & Balance

Billing Method

Fee = inference_cost_time × the app’s unit price. Includes:
  • ✅ Inference time (Running stage)
  • ❌ Does not include queueing, preparation, upload, or download time
  • ❌ Does not include Canceled tasks
  • ✅ Includes inference time consumed before an interruption

Querying Balance

Response:

Low-balance Alert

It’s recommended to poll the balance periodically (e.g., hourly) at the application layer and trigger an alert when it drops below a threshold, to avoid production disruption caused by insufficient balance.

Monitoring & Observability

Recommended metrics to monitor:

Drills & Disaster Preparedness

Drill Checklist

  • Periodically drill a fast API Key rotation after a leak (create → deploy → delete old key)
  • Drill a progressive 429 degradation (reduce concurrency, apply backpressure upstream)
  • Drill progressive WebHook callback failure (fall back to polling)

Readiness Checklist

Confirm before going live:
  • API Key stored in a secrets management service, not hard-coded
  • Synchronous blocking call client read timeout ≥ 60s
  • WebHook receiver verifies the X-BizyAir-Task-Authorization header
  • WebHook receiver implements idempotency (guard against duplicate callbacks)
  • Important outputs are transferred to your own OSS / S3 storage in real time
  • Low-balance alerts configured
  • Retry and degradation logic in place