Contextwaise
See it live

Contextwaise is in early access: API keys and the dashboard open at launch. Join the waitlist to get yours first.

Docs · Authentication›
API reference

Authentication

Every API request is authenticated with a secret key sent as a bearer token. Keys belong to a project and its dashboard.

Base URL#

Base URL
https://app.contextwaise.com/api/v1

All requests use HTTPS and JSON bodies (Content-Type: application/json).

API keys#

Keys are created in Settings → API keys. A key starts with sw_live_ and is displayed once, at creation: store it immediately in your secret manager or environment.

API keys open at launch. Join the waitlist to get yours first.

Keep keys secret
Keys grant access to your project. Use them from your servers only, never in browser or mobile code, and never commit them to a repository.

Send the key in the Authorization header of every request:

Header
Authorization: Bearer sw_live_...

A missing, malformed or revoked key returns 401 with the code invalid_api_key. See Errors and limits.

The Agent SDK uses the same keys. It reads them from CONTEXTWAISE_API_KEY, or from the apiKey option.

Rotating and revoking#

To rotate a key without downtime:

  1. Create a new key in the dashboard.
  2. Deploy it to your environment.
  3. Revoke the old key once traffic has moved over.

Revocation takes effect immediately. If you use a fail-open helper, requests made with a revoked key keep working, just without optimization.