Embed caps are hard. Verify is metered. Every plan includes verification on every retrieval. The first verify is on us.
MOST TEAMS START ON GROWTH.
Indie builders and prototypes.
Series A teams in production.
Series B+ and mid-market.
| Attribute | Free | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
Embed cap Hard cap. Embeds never overage. They force an upgrade. | 100,000 | 500,000 | 5,000,000 | 20,000,000 | Custom |
Verify included Bundled allotment per month. | 10,000 | 50,000 | 500,000 | 2,000,000 | Custom |
Verify overage Pay-as-you-go above the included allotment. | None. 429 at cap | $0.004 / verify | $0.002 / verify | $0.001 / verify | Custom |
Retention How long signed audit records stay queryable. | 30 days | 90 days | 365 days | 365 days | Custom |
SLA | None | None | 99% | 99.9% | Custom |
Support | Community | Email · 3 day | Email · 1 day | Priority | Dedicated AM |
Deploy model | Multi-customer | Multi-customer | Multi-customer | Multi-customer | Hosted or BYO |
When you hit the cap, embed calls return HTTP 429. Upgrade your tier to keep embedding.
Each tier ships with a generous verify allotment. Above it, you pay per call. $0.001 to $0.004 depending on tier. No surprise multipliers.
Use Mnemo via API or run it inside your own infrastructure. Pricing, SLA, and deployment model are scoped per engagement.
Contact sales →One mnemo.embed(vector, source_id) call. Re-embedding the same source produces a new record and consumes a new credit.
embed() returns HTTP 429 with X-Mnemo-Cap-Reset. verify() continues to work for all stored embeddings.
Yes. We bill in arrears at the per-call rate of your tier.
From the timestamp of mnemo.embed(). After retention, verification records are purged but the source identifier on the embedding remains valid.
Yes. Upgrades prorate. Downgrades take effect at the next cycle if you fit under the new cap.
Yes, on Enterprise. Pricing, SLA, and deployment model are scoped per engagement.