AI providers policy
Last updated: March 09, 2026
Note: If these Terms, Policies, or Agreements are available in multiple languages, and any discrepancies exist between translations, the English version shall prevail.
1. Provider orchestration model
BabySea is not itself the underlying model host for every generation request. In the current product, BabySea orchestrates supported routes across third-party providers including Replicate, Fal, BytePlus, Cloudflare, and BFL depending on the model, media type, region, and route configuration.
BabySea normalizes requests into its own schema, applies routing logic, and then may pass those requests to a configured provider. Some routes return results inline, while others depend on provider callbacks, provider polling, or BabySea-managed webhook finalization. Customers interact with BabySea's interface and API rather than receiving direct provider-console access from BabySea as part of the standard product.
2. Current provider boundaries
Provider capabilities differ. Depending on the route, a provider may support:
- Webhook-driven completion.
- BabySea-side polling.
- Synchronous inline delivery.
- Best-effort cancellation only.
- Different timeout and failover behavior.
BabySea may add, remove, or reprioritize providers, models, and routing order over time.
3. Provider terms still matter
Your use of BabySea must comply with:
- The Terms of use.
- The AI service terms.
- The AI principles.
- Any provider-side restrictions that apply to the underlying inference provider or model.
Even when BabySea is the customer-facing platform, some provider-side restrictions may still apply to content categories, geography, intellectual-property use, export controls, delivery mechanics, or permitted commercial use.
4. No provider permanence guarantee
BabySea does not guarantee that any specific third-party provider, route, model, or delivery method will remain available indefinitely. Product availability may change because of provider outages, commercial changes, legal restrictions, technical deprecation, or BabySea's own product decisions.
5. Customer responsibility
Customers are responsible for evaluating whether a given BabySea route is suitable for their own legal, regulatory, contractual, and business requirements. This includes assessing whether the provider chain, region behavior, latency profile, retention behavior, and output characteristics are acceptable for the customer's own use case.
6. Questions
If you need commercial or legal clarification about provider-backed routes, contact BabySea through support page before using the affected workflow in production.