Skip to main content
Synap bills on credits. Every plan includes a monthly credit allotment, and the memory operations your app performs draw down that balance. You can start free, and current plans and prices are always on the Dashboard → Manage billing.
Prices below reflect current launch/promotional pricing and can change. The Dashboard is the source of truth for what your plan costs today. This page explains the model so the numbers make sense.

​
What’s a credit?

A credit is Synap’s unit of usage. Memory operations consume credits as they run:
  • Ingestion: memories.create, memories.batch_create, and conversation.record_message
  • Retrieval: *.context.fetch (and accurate mode costs more than fast, since it runs LLM subquery decomposition + reranking). A fetch is charged once per search query it carries, so a fetch with three queries costs the same as three single-query fetches.
  • Compaction: conversation.context.compact
  • Real-time listening: each concurrent streaming session (instance.listen)
What one ingestion charge covers. A single ingestion is billed once, for the whole pipeline that ran on that document: extraction, knowledge update (deciding whether a new memory supersedes, enriches or duplicates an existing one), hypothetical-question generation, and the user-profile merge. It is one charge per document, not one per internal step.A document that is ingested but yields no memories is still charged: the extraction ran either way.
Two SDK calls let you stay ahead of your balance:
See credits.estimate, credits.get_balance, credits.get_ledger, and credits.redeem for the full reference. When you run out of credits, what happens depends on your plan and on one setting (see Overage & hard caps below). On the free Trial, requests stop. On a paid plan, requests stop too, unless the account owner has turned overages on: then they keep working and the extra usage is billed. Overages are off until the owner turns them on.

​
Plans

Annual billing saves ~17% versus paying monthly. Project and listening-session counts are indicative. For current, exact pricing and to change plans, use the Dashboard; for volume pricing, contact sales.

​
Overage & hard caps

Overages decide whether your app keeps working after a paid plan’s credits run out. They are off by default for every account, and only the account owner can turn them on. Nothing is ever billed past your allowance unless the owner has turned overages on.
A request that was already accepted when your balance reached zero still finishes, so the balance can dip slightly below zero. When overages are off, that small overdraft is not billed.

​
Turning overages on

To turn overages on, the account needs all three of these:
  • A paid plan with an overage rate: Starter, Pro or Scale.
  • An active subscription. A subscription whose payment is past due cannot turn overages on.
  • A chargeable card: the default card on your subscription, or else the default card on your billing account, and not expired. Other saved cards do not count.
The owner turns overages on in the Dashboard under Credits & Usage → Plan & billing, in the Budget & alerts panel. The Payment method panel on the same tab is where you add a card, or update one that has expired: Add card and Update card open the card form directly. Any account can add a card there, the Trial included, without buying a plan. On the Trial the card is kept for when you upgrade and nothing is charged to it; overages stay available only on Starter, Pro and Scale. From a terminal, the owner can run maximem-synap billing overages set --allow (see the CLI reference). Admins and members can see the setting but cannot change it. Every member of the account is notified when overages are turned on or off.

​
How overage is billed

  • Usage past your allowance is billed per 1,000 credits at your plan’s rate, prorated to the credit. For example, 2,500 credits past the allowance on Pro is 2.5 × $1.75 = $4.38.
  • Overage for a billing cycle is added to the invoice that renews your subscription. Annual plans are billed for overage every month.
  • If you change plans, usage before the change is billed at the old plan’s rate. If you cancel, a final invoice covers usage up to the cancellation.

​
When overages turn off by themselves

Synap turns overages off, and emails every member of the account, when:
  • the card they depend on is removed, or expires;
  • the subscription is cancelled, or moves to a plan that cannot carry overages.
Your app then stops when its credits run out, as it would with overages off. Fix the card or the plan, then turn overages back on. A failed renewal payment does not turn overages off; while that payment is past due, requests stop when credits run out, and overages apply again once the payment goes through.

​
Usage alerts

On every plan, including the Trial, every member of the account gets an email when usage reaches 75%, 90% and 95% of the credits for the current cycle. The percentage is the credits used this cycle out of those used plus the balance still left, so credits you add during the cycle count towards the total. Each alert is sent once per cycle: adding credits after the 95% alert does not send the 75% alert again.
  • Overages on: the alert gives your overage rate, since usage past 100% is billed. If usage has already passed 100% when the alert goes out, it says your allowance is used up and usage is now billed at that rate.
  • Overages off: the alert says that at 100%, requests will stop, and how to turn overages on.
  • Trial: the alert suggests upgrading.
If your account does stop at zero, every member also gets one “requests stopped” email for that cycle. Billing emails are sent even to members who have turned off other email notifications. Each one names the account it is about, and its link opens that account’s Plan & billing, so a member of several accounts always lands on the right one.

​
BYOK: bring your own LLM key

On Pro and above, you can connect your own LLM provider key (BYOK). Synap then uses your provider for the model calls in its pipeline (extraction, accurate-mode reranking), so that usage bills to your provider account instead of consuming Synap credits, useful for controlling cost and data flow at scale. Scale supports multi-provider BYOK; Enterprise supports any provider.

​
Managing your plan

Plans, invoices, current pricing, overages, the payment card, and BYOK configuration all live in the Dashboard → Manage billing. Use credits.get_ledger to audit consumption programmatically, and credits.get_balance to check what is left before a large job.

Estimate credits

Estimate an operation’s cost before you run it.

Performance & Limits

Timeouts and the limits that are visible in Dashboard → Usage.