Skip to main content

​
API Keys

All requests require a Bearer token in the Authorization header: 
Authorization: Bearer sk_live_your_key_here
API keys are created when you register an account at engram.training.
The compliance screening endpoint (POST /v1/compliance/screen) also accepts developer JWT tokens, so the dashboard can screen addresses directly without requiring an API key.

​
Autonomous Agent Registration

Agents can also self-register programmatically — no email or password required: 
curl -X POST "https://api.engram.training/v1/auth/agent-register" \
  -H "Content-Type: application/json" \
  -d '{"name": "my-agent"}'
This returns an API key, Aptos wallet address, and 100 starter credits. See Agent Registration for details.

​
Key Format

Keys follow the format sk_live_{random}: 
sk_live_oByaTs1XOOA-yNUQOzRYyETgVx1g3g7rGQQhltiu

​
Agent Isolation

Each API key maps to your account. When you create an agent under your account, that agent gets:
  • Its own isolated storage namespace
  • Isolated memory keyspace
  • Separate rate limits
Multiple agents under the same account are fully isolated from each other.

​
Security Best Practices

  • Never expose API keys in client-side code or public repositories
  • Never share keys between production and development environments
  • Rotate keys if you suspect they’ve been compromised
  • Store keys in environment variables or a secrets manager

​
Example

# Set your key as an environment variable
export ENGRAM_API_KEY="sk_live_your_key_here"

# Use it in requests
curl -H "Authorization: Bearer $ENGRAM_API_KEY" \
  https://api.engram.training/v1/memory