Pricing
Three plans metered in credits. One credit covers 350 bytes of an ingested payload. Storage, memories, entities and seats are never metered, and recall is unlimited on Flex and Enterprise.
Pay as you go
$0 / month
$45 of credits to start, or $120 with a work email. No card required to start.
For building on your own data and growing at your own pace.
Flex Production
$99 / month
Buy more at any time, down to $0.13 per 1,000 credits.
For an application in production. Ingestion is metered; recall is not.
Enterprise
Custom
No base fee. Priced against your deployment and terms.
The whole engine, from 5,000,000 credits a month.
Explore data boundaries, retention controls and deployment questions in the security overview.
How credits work
Credits per payload are the payload’s size in UTF-8 bytes divided by 350, rounded up, with a minimum of 1. A batch prices each record separately and adds them up.
| What | Credits | Notes |
|---|---|---|
| Ingested payload | 1 per 350 bytes | Rounded up per record. 700 bytes = 2 credits; 26,000 bytes = 75. |
| Webhook event | 0.1 per event | Every received event counts, including ones your filter skips; tenths of a credit add up without rounding. Ingested events also pay their payload credits. |
| Recall or answer call | 0.1 per call | Pay as you go only. Unlimited on Flex and Enterprise. |
| Storage, memories, entities, seats | 0 | Never metered on any plan. |
Re-sending an unchanged record, or retrying with the same idempotency key, costs nothing.
Buy more credits
On Pay as you go and Flex you can top up whenever you like. A single purchase can be anywhere from 100,000 to 50,000,000 credits, in multiples of 1,000. The table lists the thresholds where the price per 1,000 credits drops; once a purchase crosses a threshold, every credit in it is charged at that lower rate.
Purchased credits expire 90 days after purchase on Pay as you go, or 365 days after purchase on Flex. Flex can also top up for you whenever the balance falls to a level you choose. Enterprise agreements fix a monthly credit allowance instead of selling packs.
| Credits | Price | Per 1,000 credits |
|---|---|---|
| 100,000 | $30 | $0.30 |
| 500,000 | $130 | $0.26 |
| 1,000,000 | $220 | $0.22 |
| 5,000,000 | $850 | $0.17 |
| 10,000,000 | $1,300 | $0.13 |
Estimator
Pick an example payload or paste your own. The estimator counts its UTF-8 bytes, converts them to credits, and prices your monthly volume on each plan. Everything runs in your browser.
Example payloads
Filled from the payload above. Type a number to model a different average.
Each record pays its own credits.
0.1 credit each on Pay as you go.
Assumes your filter ingests 1 in 5 events.
Monthly estimate
Modelled context tokens
—
An example value — enter your provider’s rate.
Compare
| Pay as you go | Flex | Enterprise | |
|---|---|---|---|
| Credits and billing | |||
| Price per month | $0 | $99 | Custom |
| Included credits | 150,000 once to start; 400,000 with a work email | 400,000 per month | From 5,000,000 per month |
| Buy more credits | From 100,000 for $30 | From 100,000 for $30 | — |
| Credit rollover | None | 30 days | None |
| Bought credits expire | After 90 days | After 365 days | Not applicable |
| Automatic top-up | — | ✓ | — |
| Billing | Card | Card | Annual agreement |
| Usage and limits | |||
| Ingestion | Metered in credits | Metered in credits | Metered in credits |
| Recall calls | 0.1 credit each | Unlimited | Unlimited |
| Tokens per recall | Up to 8,000 | Up to 8,000 | Up to 32,000 |
| Projects | 1 | 5 | Unlimited |
| Requests per minute | 500 | 750 | 1,000 |
| Storage | Unlimited | Unlimited | Unlimited |
| Data retention | 365 days | 3 years | Unlimited |
| API log retention | 7 days | 90 days | Unlimited |
| Seats | Unlimited | Unlimited | Unlimited |
| Engine | |||
| Memories | Unlimited | Unlimited | Unlimited |
| Entities and relationships | Unlimited | Unlimited | Unlimited |
| Source-backed memory | ✓ | ✓ | ✓ |
| Recall with dated evidence | ✓ | ✓ | ✓ |
| Tracing | ✓ | ✓ | ✓ |
| Usage analytics | ✓ | ✓ | ✓ |
| Webhooks | — | ✓ | ✓ |
| Entity type and edge customization | — | — | ✓ |
| Custom retrieval configuration | — | — | ✓ |
| Enterprise and support | |||
| Support | Community | Slack or Teams | |
| Account manager | — | — | ✓ |
| SSO | — | — | ✓ |
| SAML | — | — | ✓ |
| Bring your own cloud | — | — | ✓ |
A credit covers 350 bytes of an ingested payload. Every record costs at least 1 credit, plus one more for each further 350 bytes or part of it. A 700-byte record costs 2 credits; ten 100-byte records in a batch cost 10.
Bytes are what is stored and processed. In UTF-8, plain Latin letters are 1 byte, accented letters 2, Chinese, Japanese and Korean characters 3, and most emoji 4. The same sentence in Japanese therefore costs roughly three times as much as in English — the estimator counts your actual text so you can check.
Storage, memories, entities, relationships and seats on every plan; recall on Flex and Enterprise; re-sending a record that hasn’t changed; and retries with the same idempotency key.
Once the balance reaches zero, the API refuses new sends with a billing error; on Pay as you go, recall calls are refused too. Buying a pack restores service, and on Flex the monthly allowance also refreshes at the start of the next month. Nothing you have already stored is altered or removed. To avoid the gap entirely, Flex can top up automatically at a balance you choose.
Pay as you go starting credits are granted once. Bought credits expire after 90 days on Pay as you go and 365 days on Flex. Unused Flex monthly credits roll over for 30 days. Enterprise monthly credits do not roll over.
When you need webhooks, more than one project, unlimited recall, 3-year retention, email support or 750 requests a minute — or when your volume makes $99 with 400,000 included credits cheaper than buying packs.
No. Seats are unlimited and your users are represented as identities in your project. Billing follows API usage.
On an Enterprise agreement: either the database alone in your AWS, Google Cloud or Azure account, or the full engine and databases. Pay as you go and Flex run on the managed service. See Enterprise.
Pay as you go needs no card to start. Move to Flex when your app goes to production.