DocsHelp
FAQ
Plans, quotas, billing, privacy, and what an agent can and can't touch.
Plans & tool access
Every tier gets the core toolset: memory CRUD, code intelligence, and the verify hallucination gate.
Free also gets a monthly sample of the headline tools: 50 one-call code answers (recall(answer) + code(locate/impact)) and 5 code(ingest) runs per month. recall(explore) is a Pro+ tool.
The MCP call returns a structured error before the tool runs:
{
"allowed": false,
"error": "tier_required",
"tool": "remember(action: "chunk")",
"currentTier": "free",
"requiredTier": "pro_plus"
}Free and Pro get this error for all three Pro+ tools: recall(explore: true), remember(chunk) and remember(batch). Pro gets bigger quotas, not these tools. Running out of a per-tool monthly quota is a different error — tool_quota_exceeded — covered below.
That tool returns tool_quota_exceeded until the 1st of next month UTC. Other tools keep working.
Upgrading unlocks higher quotas mid-month — see pricing.
Every tool returns monthly_limit errors until reset at 00:00 UTC on the 1st. Unused calls do not roll over.
License validity & offline
The JWT from /license/validate expires in 15 minutes. The client auto-refreshes; plan changes take effect within that window.
Within JWT lifetime: no interruption. Past expiry, within 24 hours: offline grace with real tier. Past 24 hours: downgrades to Free until network returns. Memories stay accessible.
You get Free tier without network. SQLite + on-device embeddings run entirely locally.
No. Certificate pinning plus RS256 JWT verification against an embedded public key prevents forged tier upgrades.
Quotas & call counting
Each MCP tool invocation or REST API request = 1 call. Failed calls before execution do not count.
First millisecond of the next calendar month, UTC. Overall cap and per-tool sub-quotas reset together.
Both locally (SQLite) and on the server via /license/usage. Server-side is authoritative across machines.
Yes — /usage when logged in shows calls, limit, plan, and recent log.
Billing & account
Pro ($19/mo) and Pro+ ($49/mo) via Razorpay. Cancel anytime from Billing.
Paid tier through end of billing period, then Free on next sync. Local SQLite unaffected.
Yes — from API keys. Old key deactivates immediately; update MEMORY_API_KEY in your MCP config and restart the server.
Privacy & data
On your machine in ~/.memorylayer/memories.db. Only license validate + usage pings leave your machine — no memory content.
Computed on-device (BGE-small ONNX, ~130 MB cached). Queries and ingest content never reach our servers.
Yes — run without an API key for Free tier with no outbound traffic.
Agent security boundaries
fs_read, fs_list, and fs_grep block SSH keys, cloud creds, ~/.memorylayer, system dirs, database files, and dotfiles.
remember({ action: "delete" }) removes one memory by ID. Bulk namespace wipe is CLI-only with typed confirmation:
memorylayer delete --namespace my-project # prompts: type "my-project" to confirm
No raw-query tool exists. All operations go through typed handlers with validated inputs.
Something missing or wrong? Email support@memorylayer.in or open an issue.