Connect

Two ways in: plain REST (any HTTP client) or the remote MCP endpoint (Claude Desktop, Cursor, and other MCP clients). Both use the same API key from /portal/keys.

1. Remember something

curl https://your-deployment/api/v2/remember \
  -H "Authorization: Bearer utek_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{ "content": "Deploy keys live in Vault, rotated quarterly", "tags": ["ops"], "importance": 0.8 }'

Optional fields: metadata (free-form JSON), namespace, type, importance (0–1), pinned, content_type.

2. Recall it

curl https://your-deployment/api/v2/recall \
  -H "Authorization: Bearer utek_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{ "query": "where do deploy keys live", "limit": 5 }'

Recall is hybrid: vector similarity and full-text search fused together (RRF), so exact keywords and paraphrases both hit. Response: { "results": [ … ] }.

3. Keyword search (no embedding)

curl https://your-deployment/api/v2/search \
  -H "Authorization: Bearer utek_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{ "query": "Vault" }'

4. Remote MCP

The MCP endpoint speaks JSON-RPC 2.0 over HTTP (protocol 2025-06-18) at /api/v2/mcp. Five tools are exposed: remember, recall, search, list, get — each inherits the same key policy and quotas as REST.

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "uteke": {
      "url": "https://your-deployment/api/v2/mcp",
      "headers": {
        "Authorization": "Bearer utek_YOUR_KEY"
      }
    }
  }
}

Cursor and other Streamable-HTTP-capable clients take the same URL + header. Older stdio-only clients can bridge via mcp-remote.

5. Check usage

curl https://your-deployment/api/v2/usage \
  -H "Authorization: Bearer utek_YOUR_KEY"

Returns today’s writes/reads/searches, storage counts, your plan, and quota snapshot in one response.