Get Your API Key

All API requests require authentication. Learn how to get and use your API key.

Getting an API Key

Create an API key from the Dashboard. Each key can be named and has its own usage tracking.

Prefer the API? Call POST /v1/auth/register with { email, password, full_name }. The response includes an access_token (JWT) you can use immediately — or mint an API key later via POST /v1/auth/api-keys.

Using Your API Key

Include your API key in the Authorization header of every request.

curl -X GET "https://api.hebbrix.com/v1/memories" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

# Python SDK — pass the API key explicitly to the client constructor.
from hebbrix import MemoryClient

client = MemoryClient(api_key="mem_sk_your_api_key")

# Or pull it from the environment yourself:
# import os; MemoryClient(api_key=os.environ["HEBBRIX_API_KEY"])

// TypeScript SDK
import { MemoryClient } from 'hebbrix';

const client = new MemoryClient({
  apiKey: 'mem_sk_your_api_key',
});

// Or read from env:
// new MemoryClient({ apiKey: process.env.HEBBRIX_API_KEY! });

API Key Format

Hebbrix API keys start with mem_sk_ followed by a unique identifier.

Security Best Practices

Rate Limits

Two limits are enforced in parallel: a per-tier requests-per-minute ceiling (to smooth traffic spikes) and a monthly credit allowance (1 credit = 1 billable operation). Individual endpoints may also carry their own stricter per-minute caps — see each endpoint's docs page. Check theX-RateLimit-*response headers for live values.

Endpoint-level caps (beyond the tier ceiling): search is 30/min, chat completions 30/min, media uploads 20/min, batch operations 30/min. Document uploads fall back to your tier's per-minute ceiling. These apply on top of your tier limit and protect expensive code paths.