terms of service
api access, billing and responsibilities.
01how 2api works
2api is being built as a marketplace of independent ai api channels. customers choose a seller offer or automatic routing and send requests through a single 2api endpoint. models run on the selected channel’s infrastructure and its suppliers.
verification results apply to a specific model, configuration and point in time. they are not an absolute guarantee of model origin, correct answers or uninterrupted availability.
02account and safe use
users are responsible for protecting their account and api keys, setting limits and managing access they grant. suspected compromised keys should be revoked and reported through the published support channel.
unauthorised access, stolen credentials, circumvention of restrictions, interference with the service and processing data without the necessary rights are prohibited. applicable laws and applicable supplier restrictions remain in effect.
03prices and usage
customers see the offer’s final rate and billing unit before use. input, output, cache reads, cache writes and embeddings may have separate rates. unsupported categories are not presented as free.
a request is billed using its recorded usage and the price snapshot at the start of processing. price changes are not applied retroactively. payment fees and conversion terms must be shown before confirming a deposit or payout.
04errors, restrictions and disputes
ai responses may be inaccurate. users should assess results before relying on them. quality, usage and billing disputes are reviewed using the request identifier and available technical evidence, subject to the refund policy.
access may be restricted for security threats, rule violations or technical failures. the reason and available review channel are communicated unless disclosure is legally prohibited or creates an immediate risk. these terms do not exclude mandatory user rights or liability that cannot lawfully be limited.
05document revisions
the accepted version and acceptance time are recorded. material changes are published in advance and require renewed acceptance where necessary. a new revision does not retroactively change completed request prices or settlements.
contact details and final documents must be published before launch. applicable operator-disclosure, data-retention and settlement requirements still need to be determined. the name “2api” does not replace disclosures required by applicable law.