Keys, versions and changes.

Rotate without losing your place

Create named keys in Your account and store their one-time secret in your environment or secret manager. Redact authorization headers in logs and never put a key in a URL, notebook, commit or screenshot. Rotate a key, update your application, then revoke its predecessor. Rotation permits at most 24 hours of overlap; suspected exposure calls for prompt revocation.

Cancellation keeps access through the paid period, then queries stop. Expired trials, suspension or changed entitlements can stop queries too. Billing and security restrictions are independent. Retained query definitions and financial/audit history are not erased when access ends.

Compatibility checklist

1. Compare the accepted service's /openapi.json, SDK version and your dataset's field/schema contract before upgrading. The marketing preview does not host the customer API.
2. Keep request parameters and the dataset version with your analysis. A corrected data version is separate from an API or SDK update.
3. If a saved version is unavailable, inspect the current catalogue, compare fields and rebuild the query deliberately. Do not silently relabel old results.
4. Read the release and migration notes for a breaking change. This guide does not promise indefinite access to superseded versions.

Guide changelog

• 12 September 2026: Version update metadata, explicit unknown update status and ISO date-column delivery across REST, Explorer and SDK.
• 11 September 2026: Searchable guide, equivalent bounded HTTP/Python requests, explicit pages, error recovery and time glossary. REST v1 and SDK 0.1.0 behavior is unchanged.
• Initial implementation: Invited-account setup, account-wide usage, Explorer and the source-distributed Python client.

These examples describe implemented interfaces and synthetic fixtures. They do not announce general customer availability or a public PyPI release.