Terms of Service
These terms govern your use of Inspekt. They are written to be read, not skimmed past. Sections 11 through 14 limit our liability and disclaim warranties, so read those in particular.
The agreement
Inspekt is operated by Menu Atlas LLC, a limited liability company formed in Utah.
In this document "we" and "us" mean Menu Atlas LLC, and "you" means the business or person on the
account. "The service" means Inspekt: the embed, the Render API, the Inventory API, the
cs2embed.js loader and the published documentation.
Creating an account, requesting a key, or calling the service means you accept these terms, the Acceptable Use Policy, the Privacy Policy and the Service Level Agreement. Those three documents are part of this agreement. If you do not accept them, do not use the service.
1. What the service does
1.1 Inspekt renders Counter-Strike 2 weapon finishes from a Steam inspect link or an equivalent set of parameters (wear, pattern seed, stickers, StatTrak, name tag). It returns an interactive 3D view (the embed), a still image (the Render API), or parsed public inventory data (the Inventory API).
1.2 We may add, change or remove features. We will not materially cut the core functionality of a plan you are paying for mid-term without giving you notice under section 16.
1.3 The service depends on Valve's game files and on Steam's public services, including inspect-link resolution and inventory data. We do not control either and are not responsible for their availability or accuracy. See section 11 and the SLA.
2. Accounts, keys and origins
2.1 An API key is not a secret. It travels in the URL of an iframe or a script tag, so it is visible in the page source of every site that uses it. We never treat a key as a credential, and neither should you. There is no version of this product where the key alone protects anything.
2.2 Your origin list is what protects your account. Every request is checked against
the origins you register. For the embed the browser enforces the same list a second time through a
Content-Security-Policy: frame-ancestors header, so a key lifted from your page source
and pasted into another site is refused by the visitor's own browser, whatever happens at our end.
2.3 You are responsible for registering every origin you call from, including staging and subdomains, and for keeping that list current. A request from an origin you have not registered is refused. That is the feature working, not a fault.
2.4 Each plan includes a set number of registered origins. More origins may mean a higher plan.
2.5 Do not use someone else's key, guess or enumerate keys, or work around the origin allowlist or the quota checks.
2.6 We can issue, rotate or disable a key at our discretion, including under section 10. Disabling a key does not by itself close your account.
3. What you may and may not do
3.1 Licence. While your account is open and your fees are paid, you have a non-exclusive, non-transferable, non-sublicensable, revocable, worldwide licence to put the embed on properties whose origins you have registered, and to call the Render API and Inventory API for your own products.
3.2 This licenses a service, not software. Our source is unlicensed and stays that way. You get access to something we host. Nothing here gives you rights in our code, 3D models, textures or anything else underneath, by implication or otherwise.
3.3 You must not, and must not help anyone else:
- self-host or mirror the service, or run any part of it outside our infrastructure;
- extract, decompile, reverse-engineer or otherwise pull out the 3D models, textures or animations the service serves, beyond what an ordinary browser caches while displaying them;
- crawl, scrape or systematically harvest the asset tree, API responses or embed output, including by automated requests designed to reconstruct our catalog;
- sublicense, resell, rent, white-label or otherwise offer the service to third parties as a product, or use one key to serve businesses other than your own;
- use our output, or what you learn from watching the service, to build or improve a competing 3D weapon-skin renderer;
- remove or obscure the wordmark on a plan that requires it; or
- use the service in any way these terms do not permit.
3.4 Everything not granted here stays with us, or with Valve as to game content. See section 11.
4. Acceptable use
4.1 The Acceptable Use Policy is part of this agreement. You are responsible for your own conduct and for anyone using the service through your key, including your end users where your product lets their input reach us, such as a name-tag field.
4.2 We serve the skin-gambling sector. Case-opening, roulette, jackpot, coin-flip and similar operators are welcome, and that is a deliberate decision rather than an oversight. If you run one, you warrant that you hold every licence and registration your jurisdictions require, that you comply with applicable gambling, age-verification and consumer-protection law, and you indemnify us under section 14.2. See Acceptable Use section 3 for the full position, and section 10 for our ability to decline or end service to a particular operator anyway.
4.3 Breaking the Acceptable Use Policy is a material breach of this agreement.
5. Plans, fees and overage
5.1 Current plans:
| Plan | Monthly | Embed loads | Renders | Inventory lookups | Wordmark | Origins |
|---|---|---|---|---|---|---|
| Free | $0 | 5,000 | 1,000 | 500 | Required | 2 |
| Starter | $49 | 100,000 | 25,000 | 10,000 | Required | 5 |
| Pro | $199 | 1,000,000 | 250,000 | 100,000 | Removable | 20 |
Quota is counted per calendar month (UTC), per event kind, per key.
5.2 Over quota. On Free, requests past a quota are refused with HTTP 429 and a
Retry-After header until the month resets. There is no overage charge because there is
no bill. On Starter and Pro we keep serving and bill the excess:
| Event | Overage |
|---|---|
| Embed loads | $0.50 per 1,000 |
| Renders | $2.00 per 1,000 |
| Inventory lookups | $2.00 per 1,000 |
5.3 Cached responses are never billed as overage, on any plan. A cached response still counts toward quota, which is what decides whether Free throttling applies.
5.4 Plan changes. Upgrades take effect immediately. Downgrades take effect at the start of the next billing cycle. We may change what a plan includes going forward under section 16, but never retroactively for a billing period already under way.
5.5 Tax. Fees exclude sales, use, VAT, GST and similar taxes. Those are yours, other than tax on our net income. We collect and remit where the law requires it.
6. Payment
6.1 Subscription fees are billed monthly in advance. Overage is billed monthly in arrears against the previous month's usage.
6.2 Payments go through a third-party processor. We never store full card numbers.
6.3 Invoices are due 15 days from the invoice date unless we agree otherwise in writing.
6.4 Late payment. Overdue amounts accrue interest at the lower of 1.5% per month or the maximum the law allows. More than 15 days past due, we may suspend the service after telling your account contact, until you pay.
6.5 Raise a billing dispute in writing within 30 days of the invoice date. After that it is waived. Disputing one line does not delay payment of the rest.
7. Uptime
7.1 We commit to 99.5% monthly uptime, measured as set out in the SLA, which is part of this agreement.
7.2 Read the SLA before you rely on this. Inspekt runs from a single self-hosted origin on a residential connection with no automatic failover. That is disclosed in full in SLA section 3 so you can judge it for yourself. The 99.5% figure is set with that in mind and is not covering for something worse underneath.
7.3 A service credit under the SLA is your only remedy for missed uptime. We do not refund downtime in cash.
8. Support
8.1 Support is by email at hello@inspekt.gg.
8.2 First-response targets, in business days, US Mountain Time:
| Plan | Target first response |
|---|---|
| Free | Best effort, no commitment |
| Starter | 2 business days |
| Pro | 1 business day |
These are targets for a first reply, not for a fix. Missing one is not a breach of this agreement and does not earn a service credit; credits are for downtime, under the SLA.
8.3 Support covers integration questions, bug reports and incidents. It does not cover custom development, content outside Counter-Strike 2, or your own site beyond the point where it meets ours.
9. New content coverage
9.1 We will make a newly released case, collection or item generally available within 7 days of Valve's release, as long as it can be rendered with techniques the service already supports.
9.2 If a new item needs a rendering technique we do not have yet, we will add it as soon as we reasonably can and will tell affected customers if it will miss the 7-day window.
9.3 We may publish a coverage page listing anything temporarily unsupported or rendered with a known limitation. Absent a published exception, our catalog covers all generally released Counter-Strike 2 weapon finishes as measured by our own coverage tooling.
9.4 This does not cover delays caused by Valve withdrawing or restricting access to the game files or data we depend on. That case is an SLA exclusion.
10. Suspension and termination
10.1 Suspension. We may suspend your access, in whole or in part, immediately and without prior notice, where it is reasonably necessary because of non-payment past the cure period in section 6.4, a suspected security threat or fraud, a breach of the Acceptable Use Policy or section 3, a legal requirement we reasonably believe applies, or a risk to the service for other customers. We will tell you as soon as we reasonably can, with the reason and what would get you reinstated.
10.2 For convenience. Either of us may end this agreement on 30 days' written notice.
10.3 For cause. Either of us may end it if the other materially breaches and does not fix it within 15 days of written notice describing the breach. We may end it immediately, with no cure period, for a breach of section 3 or a material misrepresentation under section 4.2 or Acceptable Use section 3.
10.4 After termination the licence in section 3 ends, you must stop using your keys and remove the embed and API calls from your properties, and unpaid fees stay due. Sections 1 (as to definitions), 3.2, 3.4, 11, 12, 13, 14 and 17 survive, along with anything else that by its nature should.
11. Valve and game content
11.1 Counter-Strike 2, its weapon finishes, item names, descriptions and imagery are the property of Valve Corporation.
11.2 We are not affiliated with, sponsored by or endorsed by Valve. We name Valve, Counter-Strike 2 and Steam only to describe what the service does.
11.3 You get no rights in game content. Nothing here grants you any licence or interest in it. Our grant in section 3 covers access to our service and is not a sublicense from Valve or authorization by Valve. Whatever you do with renders or data derived from game content, including showing them to your own users, you do at your own initiative and risk, and you alone decide what rights you need for it.
11.4 We make no representation or warranty of title, non-infringement or licence as to game content, and we do not indemnify you for claims about it. See sections 12 and 13.1.
12. Warranties and disclaimers
12.1 Each of us has the authority to enter into this agreement.
12.2 Except for what the SLA expressly commits to, the service is provided "as is" and "as available", without warranty of any kind, express, implied or statutory, including any implied warranty of merchantability, fitness for a particular purpose or non-infringement. We do not warrant that the service will be uninterrupted, error-free or secure beyond the SLA's commitments, or that a render will match an item's in-game appearance pixel for pixel.
12.3 We give no warranty about your right to use, display or distribute anything derived from game content. See section 11.
12.4 Where local law does not allow a warranty to be excluded, the exclusions above apply only as far as that law permits.
13. Limitation of liability
13.1 Neither of us is liable to the other for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or goodwill, even if warned they were possible.
13.2 Cap. Except for the carve-outs below, each party's total liability arising out of this agreement is capped at the fees you paid us in the 12 months before the event that caused the claim.
13.3 Carve-outs. The cap and the exclusion above do not apply to the indemnities in section 14, a breach of confidentiality under section 15, your payment obligations, or either party's gross negligence or willful misconduct, or anything that cannot be limited by law.
14. Indemnities
14.1 From us. We will defend you against a third-party claim that the service, excluding game content, infringes that party's US intellectual property rights, and cover damages finally awarded, subject to the cap in section 13.2. This does not apply to claims arising from your modifications or from combining the service with something we did not provide, to any claim about game content (see section 11), or to your use of the service after we tell you to stop because of an infringement claim.
14.2 From you. You will defend and indemnify us against third-party claims, and damages finally awarded, arising from your use of the service in breach of this agreement or the Acceptable Use Policy; from your own business, including any claim that your gambling, case-opening or wagering operation breaks gambling, lottery, age-verification or consumer-protection law; from your breach of applicable law; or from a dispute between you and your own users or customers.
14.3 Whoever is indemnified must give prompt notice, hand over control of the defense and settlement, and cooperate. The indemnified party's approval is needed for any settlement admitting fault or imposing non-monetary obligations on it.
15. Confidentiality
15.1 Confidential information means non-public information one of us gives the other that is marked confidential or would obviously be understood as confidential, including usage data and pricing terms that are not published. API keys are not confidential; see section 2.1.
15.2 Each of us will use the other's confidential information only to perform this agreement and will protect it with at least the care we use for our own, and never less than reasonable care.
15.3 This does not cover information that becomes public without a breach, was already known without an obligation of confidence, is independently developed without reference to the other's information, or comes lawfully from a third party without restriction.
15.4 Either of us may disclose where the law requires it, giving the other reasonable notice first where that is legally allowed.
15.5 This section survives for 3 years after termination, and indefinitely for anything that is a trade secret under applicable law.
16. Changes to these terms
16.1 We may update this agreement. We will post the new version with a new effective date, and for a material change, including a change to fees, the liability cap or the uptime commitment, we will give you at least 30 days' notice by email or another reasonable method first.
16.2 Using the service after a change takes effect means you accept it. If you do not accept a material change, end the agreement under section 10.2 before the effective date, and the old terms apply until then.
17. Governing law and disputes
17.1 Utah law governs this agreement, without regard to conflict-of-laws rules.
17.2 The state and federal courts in Salt Lake County, Utah have exclusive jurisdiction, and both of us consent to jurisdiction and venue there.
17.3 To the extent the law allows, each of us waives the right to a jury trial in a dispute arising out of this agreement.
17.4 Neither of us may bring a claim as a class, collective or representative action.
18. General
18.1 Entire agreement. These terms, together with the Acceptable Use Policy, Privacy Policy and SLA, are the whole agreement about the service and replace anything discussed before. Where these terms and one of those documents conflict on something these terms address directly, these terms win.
18.2 Assignment. You may not assign this agreement without our written consent, except to a successor in a merger or a sale of substantially all your assets. We may assign it freely.
18.3 Force majeure. Neither of us is liable for failing to perform, other than to pay, because of events beyond reasonable control. Uptime-specific exclusions are in the SLA.
18.4 Notices. Send notices to us at Menu Atlas LLC, c/o Northwest Registered Agent LLC, 7533 S Center View Ct Ste N, West Jordan, UT 84084, USA. We will send notices to you at the email on your account.
18.5 Severability. If a provision is unenforceable, the rest stays in force and that provision is narrowed just enough to make it enforceable.
18.6 No waiver. Not enforcing something once does not give it up for later.
18.7 Independent contractors. This is not a partnership, joint venture or agency.
18.8 No third-party beneficiaries. Nobody outside this agreement gains rights under it, including your end users.
18.9 Headings are for convenience and do not affect meaning.