Skip to main content
Most Fastino API operations require your API key. Explicitly public catalog routes such as GET /v1/models can be called without one. Authenticated operations use a simple header-based scheme-no OAuth flow or token exchange is required. Your key identifies you and determines which resources and rate limits apply to your requests.

​
Getting an API key

  1. Log in at Fastino.
  2. Go to Settings → API Keys.
  3. Click Create key, give it a name, and copy the value shown.
Store your key in an environment variable (for example FASTINO_API_KEY) rather than hard-coding it in source files. New Fastino keys start with fast_sk_. Legacy pio_sk_ keys are retired; create a replacement in the dashboard before calling the Fastino API.

​
Passing your API key

Include your key in the X-API-Key header on native Fastino requests:
cURL
OpenAI- and Anthropic-compatible SDKs conventionally send the same key as a Bearer token. Set their api_key option to $FASTINO_API_KEY; the SDK adds Authorization: Bearer ... for you.

​
Managing keys

Create, rotate, and revoke keys from Settings → API Keys in the Fastino dashboard. The public API does not expose API-key management operations.

​
Rotation checklist

  1. Create the replacement key and copy it immediately.
  2. Update each service through its secret manager or FASTINO_API_KEY environment variable.
  3. Verify requests succeed with the replacement.
  4. Revoke the old key in the dashboard. Revocation is immediate and irreversible.

​
Error responses

Treat API keys as secrets. Never place them in source code, client-side applications, URLs, logs, documentation examples, or support messages.