API Terms

These API Terms supplement the Terms of Service and govern access to the CS::Chronicles HTTP API ("API"). By using the API you accept these terms.

The API requires a personal API key sent as Authorization: Bearer <key>. Keys are shown once at creation. You are responsible for keeping keys secret, rotating them on suspected compromise, and scoping their use to your own systems. Do not embed keys in client-side or public code.

• Default rate limit: {60} requests / minute / key.
• Daily quota: {10,000} requests / day / account.
• Burst: {120} requests in a rolling 10s window.
• Responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. Exceeding limits returns 429 Too Many Requests with a Retry-After header.
• Higher limits are available on request — email {contact@example.com}.

The API is offered on a best-effort basis without an uptime SLA unless separately agreed. We may add, deprecate, or remove endpoints with at least {30} days' notice for breaking changes, or immediately for security or abuse reasons.

• No resale, redistribution, or bulk mirroring of API responses.
• No use to train third-party AI models without a written agreement.
• No circumvention of rate limits (multiple accounts, rotating IPs).
• No use that competes directly with the Service.
• Attribution: {Attribution requirement, if any}.

You may cache API responses for reasonable operational purposes consistent with response headers. You must honour deletion signals and remove data within {7} days of receiving a removal request from us.

We log request metadata (endpoint, timestamp, status, key ID, byte count) for security, billing, and abuse detection. See the Privacy Policy for retention.

We may revoke keys or suspend API access for breach, abuse, or non-payment. On termination you must stop using the API and delete cached data.