What you may do with the data
Reselling, attribution, mirroring, images and accuracy: the questions asked before anyone writes code, answered from the Terms.
Licence, resale, attribution and commercial use
This page summarises for developers; the Terms of Service are what actually govern, and where the two differ, they win.
| Question | Answer |
|---|---|
| Can I use the data in a commercial product? | Yes. A subscription grants a limited, non-exclusive, non-transferable licence to use data retrieved through the API in your applications, products and services, within your plan’s limits. |
| Do I have to credit GunSpec? | The Terms do not require attribution for the specification data. Media is different: an asset that carries a credit line is served on the condition that you render it. |
| Can I resell the data, or republish it as a dataset? | No. The licence is to use the data in your product, not to redistribute the compiled database. Reselling access to the catalog itself needs an agreement. |
| Who owns the specifications? | Individual published specifications are public facts. What is protected is the compilation: the database, its organisation and the enrichment on top of it. |
| Can I cache or mirror it? | Yes, through the API, and there is a guide to doing it well. What is prohibited is scraping or systematic downloading designed to circumvent the API or replicate the database. |
| Can I share my key with a partner? | No. Keys are licensed to the account holder and are not transferable across organisations without an enterprise agreement. |
| Can I build a marketplace on it? | A product that facilitates illegal firearms transactions is prohibited outright. Lawful commerce tooling is ordinary use, and the seller endpoints exist for it. |
| Do you guarantee the data is correct? | No. Specifications vary by production run, region and configuration, and the data represents typical or published figures. Build as though a field may be wrong, and tell us when one is. |
Where the line actually sits
The distinction that catches people is between using the data and redistributing the collection.
- Your product showing specifications to your users, including a local copy that makes that fast, is use. Mirroring the catalog is the supported way to hold one.
- Handing the collection on is redistribution, and the licence does not cover it. That includes a public dump, a competing dataset, and a bulk feed to a third party.
- Circumventing the API to collect the same thing faster is prohibited regardless of intent, and that includes running many keys to dodge a plan limit. The acceptable use policy has the full list.
- One thing is banned outright whatever your licence: building or contributing to a product that facilitates illegal firearms transactions.
Images, drawings and models
Media is not covered by the same blanket as the specification data, because some of it belongs to somebody else. The media page lists the kinds and how to fetch them; rights holders is how a manufacturer asks about their own. The rule at the call site is simple: render the credit an asset carries, do not strip it, and do not hotlink an asset into a context that implies an endorsement.
Accuracy, and saying so
The data is compiled from public sources and may contain errors or omissions; nothing here is warranted as fit for a purpose where being wrong is dangerous. Every record carries dataConfidence and its sources, data quality reports coverage per catalog, and showing what you have is how to put that on a page. Never present a specification as a safety instruction, and never fill a gap with a guess.
When in doubt, ask
This page is a summary written for developers, not a licence, and it cannot answer a question about your specific product. The Terms govern; for anything beyond them, including redistribution, volume access or an enterprise agreement, write to support@gunspec.io.