API Terms / Developer Agreement

These API Terms apply when you access CLEARIE™ GETWAY through API keys, SDKs, webhooks, exports, or automated integrations. They supplement the Terms of Service.

1. API keys and access

• Keep API keys confidential and rotate them after staff, vendor, or system changes.
• Use sandbox keys only for testing and production keys only for authorised workloads.
• You are responsible for activity performed using your keys, tokens, and webhooks.
• Do not embed live keys in browsers, mobile apps, public repositories, or client-side code.

2. Rate limits and quotas

Each plan includes rate limits, weighted API units, AI credits, webhook limits, and retention windows. You must not bypass limits through key sharing, account splitting, distributed scraping, automated retries without backoff, or endpoint rotation.

3. No raw resale or competing API

Unless expressly allowed in an Enterprise Order Form, you may not resell, sublicense, redistribute, or expose raw Getway responses as a standalone database, enrichment API, marketplace feed, bulk-download product, or competing trade-data service.

You may use API outputs internally and may show derived, limited results to your own users when those results support your workflow and do not substitute for Getway.

4. Source and rights restrictions

Some data may be sourced from public sources, licensed vendors, customer-provided records, government portals, or internal enrichment. API access does not grant ownership of underlying third-party data or the right to remove source notices, provenance, disclaimers, or confidence labels.

5. Prohibited API use

• No illegal trade, sanctions evasion, export-control evasion, AML evasion, or fraud.
• No reverse engineering, model extraction, benchmark abuse, or security testing without written approval.
• No use of API results as official customs, tax, legal, sanctions, credit, or investment advice.
• No collection or re-identification of personal data beyond your lawful basis and stated purpose.
• No automated load that degrades Getway or third-party sources.

6. Webhooks and integrations

Verify webhook signatures, use idempotency keys, protect endpoints with TLS, and avoid logging secrets. You are responsible for downstream systems triggered by API responses or webhook events.

7. Suspension

We may throttle, suspend, or revoke API access for credential exposure, suspected abuse, security risk, non-payment, legal compulsion, or use that violates these API Terms.

8. Contact

API and developer agreement questions: legal@neximprove.com