Tiers & access

Free tier is generous on purpose; you can build real things with it. Paid tiers add self-learning, the memory linter, and remove the local cap. There are two ways to upgrade: hold $SIBYL, or subscribe.

The three tiers

Upgrade

Run sibyl upgrade. It opens a page with two paths:

$ sibyl upgrade

• Stake. Connect your wallet (browser wallet or Coinbase Smart Wallet), sign to bind, and the page checks your $SIBYL balance on Base. Hold the threshold and the local cap lifts. The threshold is configurable; the default is 100,000 $SIBYL counted across liquid and staked.
• Subscribe. Pick a USDC plan, sign the transfer, and the tier flips immediately. The upgrade page shows the current monthly, quarterly, and annual prices.

On either path the CLI sees the change, rewrites credentials.json, and clears its tier cache so your next write picks up the new entitlement without delay. The upgrade command reference has the terminal flow.

The 2 MB cap, precisely

The free cap is on local database size: 2,097,152 bytes. You can read and search freely; the cap governs how much you store. When an activated free account writes past the cap, the write is checked against the server. Paid tiers remove the cap. Run sibyl status to see your current DB size against the cap.

Privacy & network behavior

This is the whole of it, stated plainly:

• Your memory content never leaves the machine. Not on read, not on write, not on search.
• Free, unactivated use makes no network calls at all.
• The only outbound call is tier verification. When an activated account writes past its tier cap, the client calls api.sibyllabs.org/api/plugin/check-write with account metadata only: account id, session token, and the database's byte size and proposed delta. Never the contents of your memory.
• The CLI never reads your memory content. It checks file size, not rows. Wallet operations happen in the browser; the CLI only sees the resulting tier change.