Tarseek Legal Center

API & Developer Terms

Effective

September 2026

Last updated

September 2026

Version

1.0

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 spend limits

Tarseek and Model Providers may impose rate limits, quotas, and concurrency limits. Exceeding limits may result in throttling, errors, or suspension. Additional spend-limit controls may be offered in the product when available.

4. Billing and metering

API Usage is billed in Credits under the Credits, Billing & Refund Terms. Billable Usage may be based on Tarseek metering, provider-reported usage, token counts, provider billing units, or actual processed usage. Streaming interruptions after processing has begun may still be billable.

5. Routing, fallback, and retries

Tarseek may route, retry, or fail over between Deployments unless you use an available control to pin a provider. You must design clients for retries and partial streams. Request identifiers, when returned, should be retained for support and 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 billable. Clients must handle incomplete streams without assuming a refund.

10. API deprecation, versioning, and compatibility

Tarseek versions public APIs under /v1 and aims 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.