Service-Specific Terms
These Service-Specific Terms supplement the Terms of Service and address technical aspects of Hummingbird API (the "Service"). In case of conflict with the Terms of Service, the more specific provisions here control.
1. Model Hosting and Providers
The Service is an aggregating gateway; the models accessed through it are operated by their respective third-party providers. Model capabilities, limits, and behavior are determined by those providers. We may add or remove available models without notice, or adjust routing when upstream changes occur.
2. API, Quotas, and Rate Limits
Access requires API keys you create in the console. To maintain stability, we may impose quotas or rate limits on request frequency, concurrency, and per-request size. Requests over the limit may be rejected or queued. Keep your keys secure; you are responsible for all use resulting from a leaked key.
3. Data Retention
For billing, abuse prevention, security auditing, and troubleshooting, we retain request metadata (such as timestamp, model, token counts, status, and source IP). Logs are routinely purged after a reasonable retention period; see the Privacy Policy for details.
4. Availability
We use commercially reasonable efforts to keep the Service available. Because it depends on third-party upstreams and public networks, we do not provide a binding uptime guarantee (SLA) unless separately agreed in writing. We aim to give advance notice of planned maintenance.
5. Beta Features
Features labeled Beta, preview, or experimental are provided "as is", may be unstable or change/discontinue at any time, and may be excluded from any availability target.
6. Model Deprecation and Changes
When upstream providers deprecate or change models, we may discontinue or replace the corresponding models. We will use reasonable efforts to offer a migration path or equivalent alternative, but cannot guarantee one-to-one parity.