Credits

Valendata uses a credit-based, pay-for-what-you-use billing model. Every action a run takes is metered separately and priced in credits, listed exactly below — no bundled flat fees, no hidden categories.

​

What credits cover

Every time you run a skill or workflow, Valendata deducts credits based on the exact resources that run consumed. Everything is billed at the published rate in 0.01-credit increments — never rounded up to a whole credit. Browser time is billed per second for as long as your run holds the browser, from session start until the run finishes (idle gaps between steps of a running workflow included). If a run fails because of our infrastructure (our proxy, our cloud browser, a worker restart, an error in our code, or an AI provider outage), every credit it used is refunded automatically and the run is marked “Failed on our side — refunded”. See Runs. Runs that fail because the site is down, blocks the run, asks for a login, or changed its page, or because of bad inputs or a cancel, are charged as usual.

​

AI model usage

Cost depends on which model a run uses, and scales with tokens used: Bring-your-own-key (BYOK) users pay their own provider directly for tokens; the model picker still applies for capability, but token cost is between you and your provider.

​

Browser & proxy time

Browser time is billed per second at this rate, in 0.01-credit increments: 45 seconds costs 1.5 credits, and 60.04 seconds costs 2.00 credits. Not every task needs a proxy — Valendata decides automatically based on what the task requires, and the surcharge only applies for the actual time a proxy tier is in use.

​

Other metered actions

Verification handling only happens (and only bills) when a task actually meets a challenge, and only where the site permits it — most tasks never touch this line at all. If a site refuses access, the run stops and reports blocked rather than trying to get around it. Every new Valendata account receives 100 free credits at sign-up, no credit card required. Use them to build and test your first skills before choosing a plan.

​

Pricing tiers

Credits are sold in bundles. The more you buy at once, the lower the per-credit cost.

​

Credits never expire

Purchased credits never expire. If you buy 5,000 credits today and use 1,200 over the next month, your remaining 3,800 are still there, no deadlines, no cut-off dates. You can buy in bulk whenever it suits your budget. Subscription plan credits work differently: they refresh each month on your billing date. Unused monthly credits do not carry over — every plan resets to its monthly grant each cycle. (Purchased top-up credits are separate from this and never expire, as above.)

​

Checking your credit balance

Click the credit pill in the top header to open the Credits & Billing panel. From there you can view your transaction history, per-run breakdowns, and top up your balance. Credits are added immediately after payment. From code, read your balance with GET /v1/account and what you spent with GET /v1/usage. Every run result reports its own credits_charged. See Runs.

​

Who pays in a workspace

Runs in a workspace draw from the workspace owner’s balance, whoever starts them. The owner can cap each member’s monthly spend. See Workspaces.

​

Frequently asked questions

Do credits carry over if I buy a new bundle?

Yes. New credits are added to your existing balance. Credits from different purchases are pooled together and drawn down as a single balance — oldest credits are consumed first.

Is there a free tier?

There is no recurring free tier, but every account starts with 100 free credits. These are enough to run several skills and evaluate the platform before purchasing a bundle.

How do Enterprise agreements work?

Enterprise plans offer volume pricing for 50,000 or more credits, custom SLAs, dedicated support, and invoiced billing. Contact the Valendata team to discuss your requirements.