Usage and credits
How FishMem meters API calls with credits.
FishMem Cloud meters usage in credits. Each metered operation costs a fixed number of credits, your plan sets how many credits you get each month, and you watch consumption in the dashboard.
What each operation costs
| Operation | Credits |
|---|---|
| Add (inferred) | 2 |
| Add (raw) | 1 |
| Search | 1 |
| Reads (get / list) | Free |
A couple of things worth knowing:
- Inferred add costs more than raw add because it runs extraction — FishMem uses a model to pull the durable facts out of your messages. A raw add stores what you give it without that step, so it's cheaper.
- Search costs one credit per query.
- Reads are free. Fetching a memory by id (
get) or listing memories doesn't draw down credits, so you can browse and verify freely.
What credits are worth
Credits map to cost at roughly 1000 credits ≈ $1. That gives you a quick way to estimate spend from your operation mix — for example, 1000 inferred adds is about 2000 credits, or roughly $2.
Watching your usage
Track consumption in the dashboard under usage and billing. It shows credits used against your plan's monthly allotment, so you can see how much headroom you have and which operations are driving spend. The Requests view breaks activity down call by call if you need to attribute usage to specific operations.
How plans set capacity
Your plan determines your monthly credit capacity. Higher tiers include more credits per month; moving up a tier raises your allotment. Credits are the meter, the plan is the bucket. For the tiers and pricing, see Billing.