Terms for Si14 QI API access, keys, rate limits, caching and redistribution. These API Terms apply to use of any Si14 QI application programming interface, webhooks, data endpoints, tokens, SDKs, documentation, sandbox environments or integration tools. They supplement the Terms of Service and any order form.
1. API access
API access may be provided under a specific plan, enterprise agreement, trial, integration approval or written permission. We may approve, deny, limit, suspend or revoke API access at our discretion if necessary for security, compliance, abuse prevention or operational reasons.
2. API credentials
-
Keep API keys, tokens and secrets confidential and store them securely.
-
Do not embed keys in public repositories, client-side code, screenshots, logs or shared documents.
-
Use separate keys for development, production and individual integrations where possible.
-
Notify support immediately if credentials are lost, leaked or compromised.
3. Permitted use
Unless an order form states otherwise, API access is limited to internal business use for retrieving, displaying and analyzing Si14 QI outputs within your own systems for your authorized users.
4. Restrictions
-
Do not resell, redistribute, publish, sublicense or provide API outputs to third parties without written permission.
-
Do not use API outputs to build a substantially similar product, model, signal service or competing dataset.
-
Do not remove or hide source attribution, timestamps, risk warnings or required disclaimers.
-
Do not exceed rate limits, bypass quotas, create duplicate accounts or rotate keys to avoid restrictions.
-
Do not use the API for unlawful trading, market manipulation, fraud, surveillance, sanctions evasion or abuse.
5. Rate limits and changes
We may set or change rate limits, quotas, endpoint availability, response fields, latency, retention, export size and caching rules. We will try to provide reasonable notice of material breaking changes, but urgent security, legal or operational changes may occur without advance notice.
6. Caching and storage
Unless an order form permits otherwise, you may cache API responses only for reasonable internal operational purposes and must refresh data in a way that preserves timestamps and avoids presenting stale data as current. You must delete cached data when API access ends if required by agreement or law.
7. Data integrity and attribution
Do not alter Si14 QI outputs in a way that makes them misleading. If you transform, summarize or combine outputs with other data, you remain responsible for accuracy, labeling and downstream use.
8. Security and monitoring
We may monitor API usage for security, debugging, billing, abuse prevention, performance and compliance. You must maintain reasonable security controls for systems connected to the API.
9. Availability
API availability is not guaranteed unless a signed SLA states otherwise. Endpoints may be delayed, unavailable, inaccurate or incomplete due to maintenance, outages, provider issues or model updates.
10. Support
API support requests should be sent to support@si14.ai. Enterprise integration and commercial questions should be sent to sales@si14.ai.