DAILY BRIEF · PODCAST
Today's brief is being prepared — episodes publish daily around 04:10 UTC.

API Terms

Last updated: 5 July 2026

1. Scope

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.

2. Authentication and keys

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.

3. Rate limits and quotas

Limits are enforced per API key and vary by plan. Current ceilings:

  • Anonymous (no key): 60 requests / hour.
  • Pro + API / Founder: 60 requests / minute, 20,000 / day, 50,000 rows / day.
  • Team / Lifetime: 300 requests / minute, 100,000 / day, 250,000 rows / day.
  • 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 info@cschronicles.com.

4. Availability and changes

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

5. Restrictions

  • 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 required on any surfaced content: "Source: CS::Chronicles (cschronicles.com)".

6. Data and caching

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.

7. Logging and monitoring

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

8. Termination

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.