Public beta terms

Terms of use

Effective October 13, 2026. These terms form an agreement between you and API Many. By creating an account, adding USD balance, or using the service, you agree to them.

1. Eligibility and accounts

You must be able to enter a binding contract, provide accurate account information, and use the service for a lawful business or personal purpose. You are responsible for your account, API keys, applications, users, and all requests made with your credentials. Notify [email protected] promptly if a key or account may be compromised.

2. Public-beta service

API Many provides a public-beta gateway to eligible third-party AI model routes. The API supports model discovery, OpenAI- and Anthropic-compatible text endpoints (including streaming), embeddings, moderation, transcription, and asynchronous image, video and music tasks. Model capabilities and limits follow the respective model maker, and not every feature of every upstream API is guaranteed.

The beta may contain defects and may be changed, rate-limited, suspended, or withdrawn. We do not promise uninterrupted operation, a response-time target, a service level, permanent model availability, or compatibility beyond the documented request and response fields. Do not rely on the beta for emergency, safety-critical, or other use where a delay or incorrect result could cause material harm.

3. Model catalog and route authorization

The public catalog is for discovery and comparison. A model name, logo, description, or planned integration in the catalog does not mean that the model is callable, that a route has passed compatibility review, or that API Many is affiliated with or endorsed by its owner.

A model remains catalog-only unless and until we have verified the written resale, redistribution, marketplace, or other authorization required for a paid route. Only models returned by the authenticated GET /v1/models response are enabled for the account, but that catalog is not a promise of instantaneous upstream availability. We may remove or restrict a model immediately if authorization, provider terms, credentials, exact-version compatibility, safety requirements, regional availability, or upstream supply changes.

4. Requests, routing, and output

You grant us the limited rights needed to transmit submitted content and settings to an eligible provider, receive the result, meter usage, prevent duplicate requests, and provide support. You retain rights you already hold in submitted content. You are responsible for having all required rights, notices, and consents.

Provider routing is implementation detail, not a promise that every model has multiple eligible sources. We may select among exact, compatible routes using availability, health, weight, limits, and other operational signals. We may move to another eligible route after a definite pre-submission rejection. We do not blindly replay a request after a timeout or other uncertain outcome that an upstream may already have accepted.

AI output may be inaccurate, incomplete, unsafe, biased, offensive, non-unique, or similar to existing material. You must review it before use. We do not guarantee factual accuracy, fitness for a purpose, copyright eligibility, exclusivity, or non-infringement.

5. Prepaid balance and charges

Your balance and model prices are denominated in USD. The prepaid balance is a limited contractual right to use API Many, not money, a bank deposit, a stored-value account, or a transferable asset. Promotional or test balances have no cash value and may have separate limits.

For an accepted request, we may reserve enough balance for its permitted output ceiling before contacting a provider. The final charge is based on recorded token usage and the public input and output rates for the requested model. The published rate quoted for a request does not change when internal processing changes. If reliable usage is unavailable after a confirmed response, the documented conservative metering rule may apply. The request receipt is the account record of the reservation, release, and final charge.

Purchased USD recharges are pooled with the account balance and, under the current offering, do not expire while the account remains active. We may change future pricing or future recharge terms prospectively, but we will not reduce an existing purchased balance merely because a model price changes. Taxes may be added where required. Stripe processes payment details.

Amounts reserved for a definite pre-submission rejection or provider-confirmed terminal failure are returned to the account balance. A timeout, connection loss, invalid success response, or other uncertain upstream outcome may remain held while we reconcile whether the request was accepted and billed. A held amount is not a second charge. Recharges are final and non-refundable except as described in the refund policy.

Saved cards and optional auto top-up

Saving a card requires your consent and does not enable automatic payments. When you separately enable auto top-up, you authorize API Many to charge your saved card the fixed USD amount you choose when your available balance falls below your selected threshold, subject to your monthly maximum. The monthly maximum counts gross successful and pending automatic recharges in each UTC calendar month; refunds do not reset it. Only one automatic payment may be pending at a time, with at least ten minutes between new automatic recharges.

You can disable auto top-up or remove the card in Account & billing. This stops new automatic payments; a payment already submitted may still complete. Failed or uncertain payments pause further automatic charges until resolved. A bank may require authentication even after a card has been saved. Card setup itself does not add to your balance.

6. Acceptable use

You must follow our acceptable use policy and any policy that applies to the selected upstream route. You may not sell, sublicense, share, or expose your API Many credentials or resell access to the service without our written agreement. We may investigate, rate-limit, suspend, or terminate access when reasonably necessary to stop abuse, protect others, comply with law or provider requirements, or manage a payment or security risk.

7. Intellectual property and names

API Many and its software, documentation, and branding belong to us or our licensors. Model and provider names and trademarks belong to their respective owners and are used only to identify compatibility. No catalog entry grants you or us rights in a provider trademark, model, or output beyond applicable law and the relevant provider terms.

8. Disclaimers and liability

To the extent permitted by law, the public beta is provided “as is” and “as available”, without implied warranties. We are not liable for indirect, incidental, special, consequential, exemplary, or lost-profit damages. Our aggregate liability for claims relating to the service is limited to the amount you paid us during the 12 months before the event giving rise to the claim. These exclusions and limits do not apply where prohibited by law.

9. Suspension, termination, and changes

You may stop using the service or request account deletion. We may suspend or terminate access for material breach, abuse, legal or provider risk, security risk, or nonpayment, including a chargeback or payment dispute filed for a valid recharge. Treatment of an unused purchased balance follows the refund policy and mandatory law; promotional balances are not refundable. Provisions that should reasonably survive, including payment, intellectual property, disclaimers, and liability, remain in effect.

We may update these terms as the public beta develops. Material changes will be posted with a new effective date, and additional notice will be given where required. If you do not agree to a change, stop using the service before it takes effect.

10. Contact

Questions about these terms: [email protected]. These terms do not limit non-waivable rights available under applicable law.