Third-Party Services

1. What TexAPI is in the supply chain

TexAPI is a gateway and integration layer, not a developer of AI models. Concretely that means:

• TexAPI does not train, own or operate any model in the catalogue.
• TexAPI buys processing capacity wholesale from an infrastructure supplier, consolidates many models from many vendors behind a single programming interface, and resells it by actual usage.
• The current architecture has one infrastructure supplier. What that means for you: see section 7.
• TexAPI is not an authorised agent, partner or official distributor of any model vendor. Model names are given solely to indicate technical compatibility.

2. Three layers in the service relationship

You have a contractual relationship with TexAPI only. You have no direct claim against the infrastructure supplier or the model vendors.

3. Third parties that process your data

The complete list. There are no others — the whole source tree and the whole dependency tree have been audited.

What is NOT here, and this matters: TexAPI uses no behavioural analytics, no advertising tracking, no third-party error collection and no third-party content delivery network. See the Cookie Policy section 4 for the full negative list.

4. Your request content leaves the country

This is the part you most need to be clear about:

1. Every API call you make — the entire content, essentially verbatim — is sent to the infrastructure supplier, which is outside Vietnam.
2. TexAPI attaches no customer identifier: no user id, no organisation id, no id for your API key.
3. Your IP address is deliberately stripped before forwarding, along with every proxy and browser header.
4. Your API key is never forwarded; TexAPI uses its own.
5. The infrastructure supplier has its own data retention and use policy, outside TexAPI’s control.

5. Which models are available, and models that are withdrawn

The catalogue is dynamic, not a commitment. The list of models and their prices is synchronised automatically from the infrastructure on a schedule. Directly:

• A model can disappear from the catalogue when the infrastructure stops offering it, with no advance notice to TexAPI.
• TexAPI may switch a model off when the cost of every route exceeds the selling price — the automatic price-safety mechanism removes unsafe routes.
• TexAPI does not commit that a specific model will remain available, and does not commit that a model version will not change its behaviour.

What TexAPI commits to instead: when a model with live traffic is withdrawn, TexAPI notifies the organisations that used it in the last 30 days through in-product announcements and email. There is no automation for this yet — it is done by hand, and TexAPI says so rather than letting you believe it is automatic.

Your wallet balance is not lost when a model is withdrawn; you spend it on another one. The balance does not expire.

6. Prices can change when costs change

TexAPI’s selling price is derived from the infrastructure cost at a fixed target margin, not typed in by hand. The cost sync runs automatically and currently has no manual approval step. Which means: if the infrastructure raises its prices, yours go up too, automatically.

That is a significant commercial condition, so it comes with four guarantees:

• TexAPI does not apply a new price to usage already spent. Each request is charged at the price in force when it was made, and that price is recorded in the pricing receipt attached to the request — you can see it on the usage log page.
• For pay-as-you-go customers, TexAPI gives 7 days’ notice when a model’s price rises by more than 10%. There is no automation for this yet — it is done by hand.
• For a customer inside a subscription period, the price and discount of the paid period do not change.
• If you do not accept a new price, you are entitled to stop using the service and ask for your unspent balance back.

7. Failures on the infrastructure side

When the infrastructure fails, TexAPI switches to another supply route for the same model where one exists. When no route is left, the request fails. The principles TexAPI commits to:

• A request that fails because of an infrastructure fault is not charged.
• TexAPI does not offer an infrastructure fault as a reason to deny responsibility. The infrastructure supplier is TexAPI’s supplier, not yours; you chose TexAPI, and choosing where to buy capacity is TexAPI’s decision.
• TexAPI currently offers no contractual service-level agreement. The Service Levels page says why, and what it commits to instead.

Single-supplier risk, plainly: because there is only one infrastructure supplier, a prolonged failure on their side is a prolonged failure of TexAPI. Your protection in that case is the right to a refund of your entire unspent balance if the interruption runs continuously for more than 72 hours.

8. Territorial restrictions

TexAPI records the country inferred from your IP address for operational and statistical purposes, but currently does not block access by country.

The infrastructure supplier and the model vendors have their own lists of supported countries, and TexAPI has not been able to verify those lists in writing.

Your obligation: make sure your use of the service is lawful where you use it, and do not use it in a territory that applicable sanctions law prohibits.

9. Why TexAPI does not name its infrastructure supplier

This document describes who receives data by type, country, category of data and purpose, without naming the supplier. That is a commercial decision, and it must not cost you information about your own data. So:

Two things make this decision matter less to you than it would at a typical platform: TexAPI attaches no customer identifier when it forwards data, and deliberately strips your IP address. What leaves is content separated from identity — see section 4.

10. Changes to this document

Adding or changing a third party, changing the infrastructure supplier, or changing the categories of data sent abroad are all major changes — 30 days’ notice, with the Privacy Policy updated at the same time.

11. Contact

Anything on this page — including the request for the recipient’s identity in section 9 — support@texapi.dev.