Pricing

Simple on purpose: one free allowance, then credits. No seats, no per-project fee, no minimum.

Free#

100 credits, once, when you sign in. No card, no expiry.

That is enough to open a project, send real pages through your own server, and find out whether the schema asks for the right fields. Most of the work of an integration happens in those 100 reads.

After that#

Rp 32.000 per 100 credits. Bought as top-ups, used when you use them.

Credits	Price	Typical use
100	Rp 32.000	Trying a new document type
500	Rp 160.000	A first integration on one document type
2,000	Rp 640.000	A pipeline on invoices or receipts

The smallest top-up is 100 credits. Nothing is charged monthly, and nothing expires. A read that is never made is never billed.

What a credit is#

A credit is our abstraction, not a vendor's bill. Every read spends credits according to the page: how much of it there is to see, how dense it is, and which tier read it. Tokens are the underlying unit; you are not asked to reason about them.

So the price of a read does not jump when a model vendor changes its rates, and a fast read costs less than a best read of the same page.

Choosing a tier is the real cost control#

Each project picks fast, balanced or best. Heavier tiers read more difficult pages and spend more credits doing it. The honest answer to "how do I spend less":

• use fast where the scans are clean and the layout is regular;
• keep balanced as the default;
• switch a project to best for the document types that need it, not for all of them.

Read Schemas, models and assistance for what changes between the tiers.

Where credits are visible#

Usage per project (reads, tokens and failures over a window) is on the project page. The console counts the same reads the core bills, so the number you see and the number you are charged for are the same number.