Direct HTTP Guide

Prefer the TypeScript SDK for normal integrations. Use direct HTTP only when you need a custom runtime.

All server-side requests include:

X-API-Key: sk_...
X-Agent: your-agent

Linked users include the agent-scoped token returned by Configure Link:

Authorization: Bearer <configure-agent-token>

Developer-scoped users can use:

X-User-Id: app-local-user-id

Canonical profile routes:

• GET /v1/profile
• GET /v1/profile/search
• POST /v1/profile/remember
• POST /v1/profile/commit

Connector routes live under /v1/connectors/*. Web search and URL fetch are utility routes under /v1/web/*, not connectors. These routes require the agent-scoped Bearer token from Configure Link; they do not accept X-User-Id or user_id request bodies.

Legacy memory route aliases are not active.