OAKOAK/memory
Dashboard
DocumentationReference
OAK.memory

Usage tiers and limits

Understand which limits your account shares, how operation credits work and what to do when a request is refused.

What counts toward a limit

All cloud MCP tool calls and protected memory data routes share your account’s rolling 60-second request budget. Calls made with different keys, stores or agents still belong to the same account. Embedding operations have an additional per-minute budget; both checks can apply to a search or write.

LimitShared byWhere to check
Total requests / minuteAll stores, keys and agents on one accountAccount settings
Embedding operations / minuteThe requesting accountAccount settings
Operation creditsThe requesting account, including shared storesAvailable credit balance

Find your effective usage tier

Open account settings in the dashboard to see your effective tier and its total-request and embedding-operation limits. An active account assignment determines the tier. When an assignment expires, the default tier applies. Buying or receiving operation credits does not change your tier. Subscription purchases are not currently available.

Request limits and credits are different

A request limit controls how quickly you can use the service. An operation credit allows a cost-bearing embedding operation, such as search, creation or update. You may have credits left and still hit a rate limit, or have request capacity but no credits for search. Failed operations follow the credit refund rules; a request reservation still remains in the rolling time window.

Signup includes 1,000 credits valid for 30 days. 50 free credits reset daily at 00:00 UTC without rollover and are spent first. Request limits follow your account usage tier. Across all stores you own: 1,000 memories and 50 MiB of estimated storage. Reads, graphs and exports also count toward the request limit.

Create, update and semantic recall cost 1 credit each. Failed operations are refunded. Listing, export, deletion and link management are free.

Resume after a limit

When a request is rejected for a confirmed rate limit, stop repeated retries and wait for earlier requests to leave the 60-second window. Reduce concurrent agents or pace a large import. For example, if your account limit is 100 requests per minute, two agents making 60 calls each would exceed that shared budget. This is an example, not a promise of your account’s current limit.

Documentation

Persistent memory for your AI workflow. Start with a private store, connect Claude Code, and carry useful context from one session to the next.

Quickstart

Create a store, connect your assistant and save your first memory. The cloud service runs the database for you.

Core concepts

Understand memories, stores and retrieval before connecting them to a longer workflow.

Connect ChatGPT or Claude

In your app’s custom MCP or connector settings, add https://www.openaikits.com/api/mcp and choose OAuth. Sign in to OAK, choose a store and approve access. You return to your app automatically. Automatic registration needs no API key, client ID or secret.

Connect Claude Code

Use a personal key and store profile to connect the OAK.memory plugin to hosted memory.

Share a memory store

Give collaborators access to a shared context while keeping each account’s identity and usage separate.

MCP tool reference

The cloud MCP endpoint exposes tools for store discovery, retrieval and memory changes. Your connection supplies the account and store context.

Usage tiers and limits

Understand which limits your account shares, how operation credits work and what to do when a request is refused.

Troubleshooting

Identify whether an issue comes from your connection, permissions, usage or the embedding service.

Local plugin setup

Run memory on your own machine instead of using a hosted cloud store. This has a separate database and setup process.

Guides

Practical paths for using memory in a personal project, a shared team store or a workflow with several agents.