Cubby

Memory for Solana agents

Your agent forgets on restart. Its cubby doesn’t.

Cubby keeps what your agent learns: wallets it trusts, coins it already checked, each user's limits. One call to save a note, one call to get the right ones back, even on a new server.

Free for one small agent. Add it as an MCP server or a small SDK.

Trusted wallets Checked coins User limits Preferences Avoid list Lessons Trusted wallets Checked coins User limits Preferences Avoid list Lessons
your-agent
  1. Running. Tap a cubby to see what goes in it.

How it works

Three things, nothing else to run.

  1. 1

    Remember

    When your agent learns something worth keeping, it saves a short note. Tie it to a wallet, a mint or a user with subject, add tags, or let it expire.

  2. 2

    Recall

    At the start of a run, or before it acts, the agent asks in plain words and gets the most relevant notes back, ranked by meaning, not just matching words.

  3. 3

    Look inside

    Every note shows up in your dashboard, per agent. Read them, fix a wrong one, delete what should go. Nothing is hidden from you.

Survives restarts and moves

Memory that lives outside the process.

Crash, redeploy, switch hosting: the next process asks Cubby and picks up where the last one stopped. Your agent key is the only thing it needs to bring along.

Made for crypto agents

Notes about the things your agent touches.

Exact keys for on-chain things

Give a note a subject, like a wallet address or a token mint, and recall can filter on it exactly. Forget everything about one wallet in a single call.

Per-user limits stay put

“Never more than half a SOL per trade.” Save it once with the user's id as subject, and every later run checks it before acting.

Notes that expire

A check on a fresh coin is only good for a while. Set ttl_days and the note removes itself when it goes stale.

Each agent has its own shelf

Every agent gets its own key and only sees its own notes. Rotate a key from the dashboard if it ever leaks.

Plug it in

As an MCP server, or a few lines of code.

MCP clients get five tools: remember, recall, update_note, forget and recent_notes. Anything else can use the SDK or plain HTTP.

mcp config
{
  "mcpServers": {
    "cubby": {
      "type": "http",
      "url": "https://cubby.cash/mcp",
      "headers": { "Authorization": "Bearer cubby_agent_..." }
    }
  }
}

Pricing

Start free. Pay monthly in USDC when you grow.

Plans count stored notes and recalls. The free plan covers one small agent: 1,000 notes and 5,000 recalls a month. Once $CUBBY is live, its creator fees can pay an agent's plan.

Free

0 USDC / month

One small agent.

  • 1 agent
  • 1,000 stored notes
  • 5,000 recalls a month
Get a free key

Builder

12 USDC / month

A few agents in production.

  • 5 agents
  • 25,000 stored notes
  • 100,000 recalls a month
USDC billing opens soon

Fleet

49 USDC / month

Many agents, one bill.

  • 50 agents
  • 250,000 stored notes
  • 1,000,000 recalls a month
USDC billing opens soon

Questions

Plain answers.

What does “recall by meaning” mean?

Notes are matched on what they are about, so “is this wallet safe?” finds a note that says “dev dumped on holders”. Cubby also matches exact words and subjects, so an address always finds its notes. Each recall tells you which kind of matching ran.

Who can read my agent's notes?

Only requests with that agent's key, and you in your dashboard. Keys are stored hashed; we cannot show them again, so keep them somewhere safe.

Can I delete notes?

Yes, one at a time, by subject, a whole agent at once, or your entire account. Deleted means gone.

Does it need my wallet?

No. Cubby never asks for wallet keys or seed phrases, and you should never put them in a note.

What happens at the plan limit?

New notes or recalls get a clear “limit reached” error (HTTP 402) so your agent can carry on without memory. Nothing you saved is deleted.

Give your agent a cubby.

Create an account, add an agent, paste its key. Takes about a minute.

Get a free key