Tarseek Legal Center

API & Developer Terms

These API & Developer Terms supplement the Terms of Service and apply when you access Tarseek programmatically, generate API Keys, or build applications that call Tarseek.

1. API keys and credential security

You must keep API Keys secret, restrict them to trusted environments, rotate them if exposed, and revoke Keys you no longer need. You are responsible for all requests authenticated with your Keys.

2. Automated access

Automated access is permitted only through documented APIs using valid credentials. Scraping Tarseek websites, harvesting model catalogs by abusive means, or bypassing authentication is prohibited.

3. Rate limits, quotas, and cost guardrails

Tarseek and Model Providers may impose rate limits, quotas, and concurrency limits. Optional project and key cost limits use Tarseek's recorded estimates to reject later requests. They do not cap the Customer's provider account or guarantee the provider's final invoice.

4. Billing and metering

Customers bring their own Provider Credentials. Model Providers bill the Customer's provider account directly under the provider's terms. Tarseek does not sell prepaid inference credits or add a model-usage markup. Tarseek may display usage and estimated cost based on provider-reported usage, catalog prices, token counts, or other provider billing units. A provider may charge for work completed before a stream is interrupted.

5. Routing, fallback, and retries

Tarseek uses the explicit Model's designated primary Deployment with the Customer's matching Provider Credential. It does not silently switch to another Deployment or a Tarseek-owned key. You must design clients for retries, idempotency where offered, and partial streams. Request identifiers should be retained for support and provider billing disputes.

6. Downstream applications and end users

If you provide an application to end users, you are responsible for that application’s compliance, including your end users’ Inputs, your user terms, age restrictions, privacy notices, and provider rules. Tarseek has no direct contract with your end users unless it separately agrees.

7. API abuse

Prohibited conduct includes credential stuffing, automated attacks against Tarseek, bypassing rate limits or safety systems, mining undocumented endpoints, misusing provider identifiers, generating abusive traffic, or using Keys from unauthorized accounts.

8. Reverse engineering and undocumented endpoints

You may not reverse engineer the Service except to the extent that restriction is prohibited by law. Undocumented endpoints, beta headers, and internal identifiers may change or disappear and are not a supported contract. Do not present Tarseek-internal provider identifiers as if they were the provider’s official product names in a misleading way.

9. Streaming

Streaming may disconnect. Tokens already processed by a provider may be billed to the Customer's provider account. Clients must handle incomplete streams.

10. API deprecation, versioning, and compatibility

Tarseek intends to version public APIs and to provide reasonable deprecation notice for breaking changes where practicable. Backwards compatibility is a goal, not an absolute guarantee, especially for Model availability and provider-specific behavior. Beta endpoints are governed by the Beta & Preview Terms.

11. Provider rules

You must comply with applicable Model Provider terms. Tarseek may pass through or enforce those rules, including commercial-use, geographic, and data-handling restrictions.