Tripo AI

What the Tripo integration does

The Assets page and the Editor can generate a 3D model in three ways: from a text prompt alone, from one image, or from two to four views of the same object given in front, left, back, right order. With images, Tripo models from the images alone; your prompt is kept in MapToPlay as the model description and is not sent. MapToPlay passes the request to Tripo on your behalf, follows the job until Tripo reports it finished, downloads the textured model and its preview image straight away, and imports them into your MapToPlay assets.

The integration stays off until you use it and select a Tripo API key saved for your team. MapToPlay provides the connection and the import step; the model itself is produced entirely by Tripo. MapToPlay does not own, train, host, licence, or resell that generation service.

Bring your own key, and what that means

This integration is bring-your-own-key, often shortened to BYOK. It means MapToPlay supplies the technical connection and you supply the key that authorises and pays for the generations. Your integration is yours.

In practice: you create your own Tripo account, pick your own plan, buy your own credits, generate your own API key, and select it in MapToPlay. You must own that account or be expressly authorised to use it. MapToPlay does not create a Tripo account for you and does not give you access to anyone else’s.

MapToPlay does not provide a shared key, a bundled key, a fallback key, a trial key, a pooled account, free generations, credits, boosts, top-ups, or allowances of any kind. There is no MapToPlay-owned Tripo access waiting behind this feature. If your key or your credit balance runs out, generation stops.

MapToPlay is not affiliated with Tripo

MapToPlay and Tripo are separate and unrelated. MapToPlay is not affiliated with, sponsored by, endorsed by, certified by, an agent or reseller of, or in a partnership or joint venture with Tripo AI or Holymolly Limited, and has no influence over how Tripo runs its service or its models.

Tripo, its logos, service names, models, and outputs belong to Holymolly and its licensors. They appear in MapToPlay only to identify the service you have chosen to connect.

What reaches Tripo

When you start a generation, the request goes to Tripo with the material that job needs: your prompt for a text generation, or the reference images you attached for an image generation, the generation settings, and the ordinary technical details that accompany an API request. Reference images are uploaded to Tripo first, which gives each one a file token for the generation. The key you selected is used to authorise those requests and is not handed to your browser as part of the generation flow.

Send only material you have the right to send. Anything included in a prompt or a reference image is received and processed by Tripo under Tripo’s rules, and MapToPlay cannot recall it, filter it, or restrict what Tripo does with it afterwards.

Tripo’s privacy policy is Tripo’s

How Tripo collects, uses, stores, shares, retains, and deletes data — including whether your prompts, images, and results are retained or used to improve its models — is governed by its own documents, including the Tripo Terms of User Agreement and the Tripo Privacy Policy. MapToPlay does not write, manage, review, approve, negotiate, or enforce any of them, and cannot change them on your behalf.

Tripo may change those documents at any time without notifying MapToPlay or you. Read the current versions before you enable the integration, and again while you keep using it.

Any request about data Tripo holds — access, correction, deletion, restriction, or objection — goes to Tripo. MapToPlay cannot make or answer it for you.

Keys, plans, credits, and charges

Everything commercial about Tripo happens outside MapToPlay: choosing a plan, buying credits, paying for them, watching your balance, and dealing with an invoice, a downgrade, or a suspension.

A generation consumes credits from your Tripo account when the job runs, and running one again consumes them again. How credits are counted is set by Tripo, and your balance and history live in your Tripo account. MapToPlay checks your balance before a generation starts so that a job it cannot pay for is not sent.

MapToPlay does not sell, resell, sublicense, pool, or redistribute Tripo access, and does not provide credits, boosts, top-ups, discounts, or allowances of any kind. It does not judge whether your plan suits your project, and it does not reimburse Tripo charges or credits consumed by any generation.

No guarantees about generation or results

MapToPlay provides the connection and the import step, and provides them as they are. To the maximum extent permitted by applicable law, MapToPlay makes no representation or warranty about availability, continuity, licensing status, non-infringement, or fitness for any particular purpose.

What comes back depends on your prompt, your reference images, and the settings used. Review a result and check its scale, topology, and materials before you build on it.

Whether a generated model may be used, modified, published, or sold — and what licence, credit, or attribution applies — is determined by Tripo’s terms and by applicable law, not by MapToPlay. Tripo’s Terms of User Agreement (last updated July 11, 2025) treat free and paid use differently: for users who use Tripo free of charge, Tripo retains all rights in their inputs and outputs (section 5.2.1), while paid users generally hold the rights in their own inputs and outputs (section 5.2.2). Check which applies to your Tripo account before you rely on a result. You are responsible for holding the rights to every prompt and reference image you submit, and for checking that a result may be used the way you intend.

If Tripo changes something on its side

Tripo controls its own API, models, pricing, credit rules, plans, terms, authentication, output formats, and availability, and can change or withdraw any of them at any time without notice to MapToPlay or to you.

MapToPlay follows those changes as they happen, and may add, change, suspend, restrict, or remove the integration at any time. MapToPlay owes no refund, credit, or compensation for a change made on either side.

Turning it off and removing your key

Nothing is generated unless you ask for it, and you can stop using the integration at any time by not selecting a key.

Saved provider credentials are kept encrypted for your team and used only for the integration an authorised team member selects. Because team membership changes, decide deliberately which team may use a key, remove it when that is no longer appropriate, watch your credit usage, and rotate or revoke the key if you suspect it has been exposed or misused.

Removing a key from MapToPlay does not revoke it at Tripo. Revoke it in your Tripo account as well.

Who to ask

MapToPlay can help with the MapToPlay side: where the generation controls live, what is imported into your assets, and whether the interface is behaving.

Anything about your Tripo account, key, plan, credits, invoice, charge, quota, licence, model, or output goes to Tripo. MapToPlay cannot open, escalate, or resolve a case on your behalf.

Limitation of liability

To the maximum extent permitted by applicable law, MapToPlay is not liable for any loss or damage arising from Tripo, your Tripo account, a compromised or misused key, a Tripo charge or consumed credit, an unavailable or removed integration, material transmitted to Tripo, Tripo’s processing of that material, or your use of or reliance on any generated result. Nothing in this notice excludes liability that cannot lawfully be excluded.

Contact

Questions about how this integration connects to MapToPlay can be sent to contact@maptoplay.com. Questions about Tripo AI itself go to Tripo AI.

The general third-party integrations notice covers every MapToPlay integration and applies alongside this page.