LTX-2.5 vs MiniMax H3: license lines and run requirements

The sharpest difference between LTX-2.5 and MiniMax H3 is the license, not the specs. LTX-2.5 is free under the LTX-2.x Community License below 10 million dollars in revenue and needs a paid agreement above that. MiniMax H3 requires written authorization above 20 million US dollars in yearly revenue, and its license defines the applicable territory as worldwide except the US, EU, UK and Republic of Korea.

How do they compare on the pages that matter?

What does each ask you to display?

H3's license section III.3.a requires a notice reading "Powered by MiniMax H3" on products or services developed with it. I did not find an equivalent line on the LTX-2.5 card, but the card points to a license file, so read it before launch.

What should a small team do first?

Check the license against your own situation before you check the speed. A team in the US, the EU, the UK or South Korea is in the license's excluded territories, so check with MiniMax before using the H3 weights. A team with revenue near 10 million dollars should read the LTX terms about the paid agreement before it builds on the weights.

If the license is fine, run the same five prompts on each and compare time, memory and look. Where a license blocks one of them, you do not need that comparison at all. None of this is legal advice; ask counsel if the stakes are high.

Which ones can you call by id on Sume?

minimax-h3 and minimax-h3-max are in the catalog. LTX is not (catalog code, read 2026-10-09). The hosted minimax-h3 row takes 5 to 15 seconds at 480p or 768p, and a hosted call is a different thing from running the open weights. For a full read of what a company outside the excluded territories can do, see the earlier license comparison, and the video docs for the hosted fields.