Authentication

Cortex uses API keys for authentication. Every request must include your API key in the Authorization header.

Getting an API Key

1. Go to console.askcortex.in (opens in a new tab)
2. Sign in with Google
3. Navigate to API Keys
4. Click Create Key
5. Copy your key immediately - you won't see it again

Using Your API Key

HTTP Header

Authorization: Bearer YOUR_API_KEY

SDK Configuration

import { CortexClient } from '@cortex/memory';
 
const cortex = new CortexClient({
  apiKey: process.env.CORTEX_API_KEY
});

MCP Server

For Claude Desktop or Cursor, set the environment variable in your MCP config:

{
  "mcpServers": {
    "cortex": {
      "command": "npx",
      "args": ["-y", "@cortex/mcp"],
      "env": {
        "CORTEX_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Security Best Practices

Never Commit API Keys

Add your environment file to .gitignore:

# .gitignore
.env
.env.local

Use Environment Variables

# .env
CORTEX_API_KEY=your-api-key-here

Rotate Keys Regularly

If you suspect a key is compromised:

1. Go to console.askcortex.in/keys (opens in a new tab)
2. Create a new key
3. Update your applications
4. Delete the old key

API Base URL

All API requests go to:

https://askcortex.plutas.in/v3

Rate Limits

Rate limit headers are included in every response:

X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 950
X-RateLimit-Reset: 1704067200

Containers

Cortex supports multi-tenant isolation through containers. Each container has its own separate memory space.

const cortex = new CortexClient({
  apiKey: process.env.CORTEX_API_KEY,
  containerTag: 'project-alpha'  // Optional: isolate memories per project
});

This is useful when:

• Building multi-user applications
• Separating test and production data
• Isolating memories per project or workspace