Restrictions¶
The information on this page is a summary of the restrictions outlined in the Terms of Use Agreement. To request the full Terms of Use document, please contact us at [email protected].
Where applicable, addendums to the agreement may be made to allow for usage outside the standard restrictions.
These restrictions are primarily in place to ensure that data accessed via the APIs is used in accordance with the licensing agreement. Some restrictions also exist to maintain security and ensure system resiliency.
Before using the APIs, please make sure you’ve read and understood the restrictions outlined on this page. If you have any questions or concerns, contact us at [email protected].
Artificial Intelligence (AI) Usage¶
All data provided by Spec Check via the API may not be used, directly or indirectly, to; train, fine-tune, or otherwise improve or operate any machine learning models or artificial intelligence (AI) systems, including but not limited to large language models (LLMs), without the express prior agreement from Spec Check.
This prohibition includes, but is not limited to:
- Uploading, scraping, copying, or transmitting our Data into or through AI platforms or tools;
- Using our Data to create derivative models, algorithms, or automated systems;
- Granting third parties access to our Data for AI development or processing.
Access Locations¶
The Spec Check APIs are intended to be accessed server-to-server. The APIs should never be accessed directly by end-user browsers or mobile devices.
Storage¶
Permanent storage of any data returned via the APIs is a breach of the terms of use. There are two exceptions to this rule; caches and mappings.
Caches¶
Building performant applications without utilising caching is exceptionally difficult, as such we do allow data to be cached in RAM for up to 24 hours, after this time data must be refreshed.
Mappings¶
There is no restriction on the storage of identifiers and keys where used as a mapping.
For example, if in your own system you have machines and would like to match them against results from the APIs, then there is no problem with storing the machine id, variation id, or revision id.
An example that would not be permissable however is storing an attribute value for later reference.
Redistribution¶
All forms of redistribution of the data must be discussed before implementation to ensure they are covered by your specific licence agreement.
Rate Limiting¶
Rate limiting measures are in place to protect the APIs - initially a limit of 1,500 requests per hour will be placed on each API key, this limit operates over a rolling 1 hour windows, and can be increased once the APIs have been accessed.
When a request is rate limited the server will response with a 429 - Too Many Requests response. In the response headers there will be a value for Retry-After, this value will be given in seconds and client applications should wait at least this length of time before attempting to reconnect.
Ad-hoc rate limiting may also be used if the APIs are subject to heavy loads to protect from loss of service.
Exceptions¶
If required exceptions can be made to the restrictions above where there has been agreement with Spec Check. In these scenarios an amendment to the terms of use will be agreed upon, this may include additional restrictions.