Intellectual Property

1. The principle: who owns what

Three separate layers of rights, and this document does not blur them together:

2. What TexAPI owns

• The platform source code: the API gateway, the format conversion, the routing system, the billing and metering systems, the operator console, and the texapi-connect command-line tool.
• The interface design, the information architecture, and the visual system of the site and the dashboard.
• The name TexAPI, the domain names, the logo and the brand identity.
• Documentation TexAPI wrote, including this entire set of legal documents.
• The structure and organisation of the model catalogue, and the internal pricing and routing parameters.

You may not: copy, reverse-engineer, disassemble or make derivative works from TexAPI’s software; use the TexAPI name or logo in a way that suggests you are TexAPI or are endorsed by TexAPI; or remove copyright notices.

You may: name TexAPI to describe truthfully that your product uses it — “Powered by TexAPI”, for instance; and use the TexAPI logo unmodified in your own technical documentation.

TexAPI grants you the right to use the service — it does not transfer ownership of any part of the software. The texapi-connect command-line tool is published under the MIT licence; that licence’s terms apply to that package and do not extend to the rest of the platform.

3. What you own

3.1 The content you send

You keep every right in the content you send through TexAPI. TexAPI claims no ownership, asks for no assignment, and asks for no broad licence.

TexAPI has the right to use your content only to the minimum extent necessary to provide the service: forwarding it to the infrastructure supplier for a model to process, and scanning it with the automated moderation filter. There is no other purpose.

TexAPI does not use your content to: train models — TexAPI trains no models; improve the service; do commercial analysis; or sell to a third party. Your content is not stored.

3.2 Content the model generates

TexAPI claims no ownership of the output a model generates for you. To whatever extent TexAPI has any right in that output, TexAPI assigns all of it to you.

But TexAPI cannot — and does not — warrant that you own the output. This is the part to read carefully, because many platforms are vague here:

1. Your rights in the output depend on the model vendor’s terms, not on TexAPI. Each vendor has its own rules, and some attach conditions.
2. The law on copyright in machine-generated content is unsettled. In many legal systems, content with no human author may not attract copyright protection at all. TexAPI does not reach that conclusion on your behalf.
3. Output can be duplicated. The same prompt can produce identical or near-identical output for another user. You have no exclusivity in the output.
4. Output can infringe other people’s rights. Models are trained on data TexAPI does not control and whose contents it does not know, so output can reproduce protected material. You are obliged to check before using output commercially — especially for source code, images, and long text.
5. Trademark protection is a separate question. Even where you have copyright in the output, using it in commerce can infringe someone else’s trademark. The infrastructure supplier’s terms expressly exclude indemnity on this point, which means TexAPI has no cover to pass on to you here — and TexAPI says so rather than staying quiet about it.

4. Why model names appear on TexAPI’s pages

The following clearly do not belong to TexAPI:

TexAPI shows model names and vendor logos as nominative use: naming them so you know which model is being served and which format is compatible. There is no way to describe a model other than by naming it.

Three conditions TexAPI holds itself to:

1. Use them only as far as identification requires.
2. Do not suggest endorsement, affiliation or authorisation.
3. Carry a statement of non-affiliation where a reader will see it — that bilingual statement appears at the foot of every page that shows a vendor name or logo, not only the home page.

The logo outlines come from an open-source, public-domain icon set. That grants no trademark rights — the icon set’s licence covers the path data, not the trademark. They are different things, and TexAPI relies on the nominative-use principle above rather than on the icon set’s licence.

5. Open-source software

TexAPI is built on third-party open-source libraries. Ownership and licensing belong to their respective authors, and TexAPI complies with each library’s licence.

If you are an author and believe TexAPI has misapplied a licence, contact support@texapi.dev and TexAPI will deal with it within 10 working days. A full open-source attribution page is being prepared.

6. Reporting an intellectual-property infringement

If you believe content on the TexAPI platform, or a customer’s use of TexAPI, infringes your intellectual property: email support@texapi.dev with the subject [SỞ HỮU TRÍ TUỆ].

What to include: a description of the work or trademark infringed, with evidence of your rights; a specific description of the allegedly infringing material and how to identify it; your contact details; a statement that you believe the use is unauthorised; and a statement that the information you have given is accurate and that you hold the rights or are authorised to act.

TexAPI commits to: acknowledging receipt within 2 working days; assessing and responding within 10 working days; removing content or restricting access where there is a clear basis; and notifying the affected customer and giving them a right of reply.

Counter-notice. If you are a customer against whom a measure has been taken and you believe the complaint is unfounded, send a counter-notice to the same address. TexAPI reviews it within 7 working days. TexAPI does not automatically take the complainant’s side.

7. Your obligations

• Only send TexAPI content you have the right to send.
• Check output before using it commercially, especially source code, images and long text. This is not a formality — points 4 and 5 of section 3.2 are real risks.
• Do not use TexAPI to deliberately reproduce protected material.
• Do not use TexAPI to create impersonating content, or to imply a false commercial origin.
• You indemnify TexAPI against third-party claims arising from the content you send or from your use of the output.