Skip to main content
Welcome to the BabySea API documentation. The API normalizes image and video generation across multiple inference providers into a single unified schema.

Interactive API Reference

View our comprehensive, interactive API reference on the Model Schema page. It includes exact curl commands, SDK snippets, and specific schemas for every model we support.

​
Base URL

BabySea provides three regional API endpoints. You must use the API base URL that corresponds to the region your account was created in. API keys are region-specific, and you cannot use a key from one region to authenticate against another region’s API.
  • US region: https://api.us.babysea.ai/v1
  • EU region: https://api.eu.babysea.ai/v1
  • APAC region: https://api.jp.babysea.ai/v1
Regional Routing: In the examples throughout the documentation, api.<your_region>.babysea.ai is used as a placeholder. Be sure to replace <your_region> with your account’s assigned region (us, eu, or jp).

​
Endpoint Security & Schema Validation

BabySea employs an enterprise-grade edge API firewall across all regions (US, EU, APAC). Every request is strictly validated against our OpenAPI 3.0.3 schema before it reaches our orchestration layer.
  • Strict Validation: All 15 endpoints (totaling 45 operations across our 3 regional hosts) are monitored. Any traffic that does not conform to the documented schema methods, parameters, and paths will be logged and may be dropped in the case of volumetric abuse.
  • Session Identifiers: Rate limits, anomaly detection, and sequence analytics are bound directly to your Authorization header (your API key) using session tracking, rather than basic IP blocking.
  • Regions: You must use the API host assigned to your account (api.us, api.eu, or api.jp). API keys are not cross-regional.

​
Authentication

Authentication is handled via Bearer tokens. Include your API key in the Authorization header: 
Authorization: Bearer BABYSEA_API_KEY

​
Standard Envelope

All successful responses follow a standard envelope:
JSON
{
  "status": "success",
  "request_id": "req_a1b2c3d4e5",
  "message": "Operation successful",
  "timestamp": "2025-01-01T12:00:00.000Z",
  "data": { ... }
}
For paginated endpoints, the response also includes total, limit, and offset.

​
Errors

Error responses return a 4xx or 5xx status code and follow this structure:
JSON
{
  "error": "bse_invalid_api_key",
  "message": "The provided API key is invalid or expired."
}