Credits

Every API request draws from a pool of credits. Today, credits exist to protect the API from abuse, not to bill you. Everything is included with the Pro plan, which comes with a generous ceiling. We may introduce usage-based pricing in the future; if we do, this page will document it.

How the pool works

Parcel uses a rolling 24-hour window, not a prepaid balance:

remaining = ceiling - used

used is the number of credits consumed in the trailing 24 hours. As calls age out of the window, used falls and remaining rises automatically. There is no hard reset.

Plan	Ceiling	Window
Pro	250,000 credits	rolling 24 hours

What costs a credit

Entity searches and entity get-by-id reads cost credits. Writes and View/Favorite metadata operations are free.

Operation	Cost
Entity search (Data API, Workspace book, View-record search)	1 credit per row returned
Entity get by id (account, contact, project, signal)	1 credit per record
List/get Views, Favorite list/upsert/delete	0 credits
Upsert, delete (including View definition and membership)	0 credits

Every search response includes metadata.credits, the exact number of credits that call consumed, so you can see usage as you go.

Note

Credits are an abuse-protection limit today, included with the Pro plan. Free and Starter workspaces cannot call the API.