How it works
One prepaid balance in rupees, a price before every call, a hold that becomes a charge or is released, and ₹0 for anything that is not a useful answer.
One balance, one bill
Every team has one balance, in paise (₹1 = 100 paise). A new team starts with ₹100 of welcome credit. Every tool call is paid from that balance; there is no subscription and no per-tool account. The balance is read with GET /v1/balance or the MCP tool check_balance, and every paid response repeats it as balance_paise and in the X-Balance-Paise header.
During the closed beta, more credit is added by Parel on request: email hello@parel.si with the team name. Purchases are off; see Top-ups.
The price comes first
Every tool shows its price before you run it, in rupees at today's exchange rate (₹93.93 per US dollar on 17 November 2026). The price in a tool's description, in POST /v1/discover, in inspect_tool and in POST /v1/quote is computed by the same formula and the same live rate that settle the call, so the number you read is what the call normally costs. The rate is fixed for each call when it starts.
The formula, from the wallet's own code: the source's cost in US dollars, converted at today's rate, plus Parel's margin, rounded up to the next paisa. The margin is a share of the cost, and never less than ₹0.10 a call, so a call that costs the source a fraction of a paisa costs you about ₹0.10. There is no flat minimum charge, and a call that costs the source nothing costs you nothing. The margin is a setting; the site does not state it as a percentage because it can change, and the price you see is always the price after it.
A free quote for an exact input: POST /v1/quote or quote_tool returns estimate_paise, hold_paise, whether the balance covers it and whether the call needs confirmation. Nothing is recorded and nothing is held.
Hold, then charge or release
- Validate. The input is checked against the tool's schema. A bad field is
invalid_inputwitherrors[], ₹0, and the source is never called. - Hold. The estimate plus a safety margin is held on the balance: for
search_webtoday that is ₹0.38 for a ₹0.14 call. If the balance cannot cover the hold, the call is refused withinsufficient_balance(HTTP 402), ₹0. Spend caps are checked in the same transaction:budget_exceedednames the cap. - Call. The source is called with the tool's timeout.
- Settle. In one transaction the call is classified, the real price is charged and the unused part of the hold is released. The real price is normally the price shown. See if a source bills more than expected, below.
Every response from POST /v1/run carries X-Call-Id, X-Cost-Paise and, once the balance is known, X-Balance-Paise. The body repeats them as call_id, cost_paise (or charged_paise: 0 on failure) and balance_paise.
If a source bills more than expected
The price shown is what a call normally costs, and a failed call costs nothing. The charge itself is worked out from what the source really billed for that call, so it can come out different from the price shown:
- Within the hold. The real price is charged and the unused part of the hold goes back to your balance. This is the normal case; the hold is larger than the price shown so that a call that comes out a little dearer still fits inside it.
- More than the hold. The extra is taken from your balance only when the balance covers all of it. When it does not, you are charged exactly the hold and Parel pays the rest.
Your balance never goes below zero. cost_paise and the usage log show what was really charged.
Two details. Every call is sent to the source with a limit: the source is told to refuse a call it expects to cost more than the estimate plus half, or one US cent, whichever is larger (the refusal is estimate_too_low, ₹0). For the cheapest tools that limit is higher than the hold. And spend caps are checked when the hold is placed, so an extra taken this way can carry a day's or a month's spend past a cap by the amount of the extra.
What costs ₹0
Only a useful answer is charged. Every response has a class; only ok is paid.
class | What happened | You pay |
|---|---|---|
ok | A result came back | the real price of the call, normally the price shown (if a source bills more) |
ok_free | The source answered but there was nothing in it by the tool's rule: no email, an empty list, an empty page (error: no_result) | ₹0 |
replay | The same idempotency_key within 24 hours: the stored answer | ₹0 |
vendor_error | The source refused the call (HTTP 422) | ₹0 |
upstream_error | Timeout, the source down, a route problem or our own fault (HTTP 502, or 500) | ₹0 |
rejected | Refused before the source was called: bad input, empty balance, a cap, an unknown tool, a paused tool (400, 402, 404, 429, 503) | ₹0 |
running | A slow job has started (HTTP 202) | nothing yet; the hold stays until it finishes, a failed job is ₹0 |
A charged answer that was useless anyway: press Report bad result on the call in your usage log within 7 days. Up to ₹200 per team per calendar month comes back to the balance at once; larger amounts, or reports after 7 days, are reviewed within two business days. Refund Policy.
The confirmation step above ₹200
A call whose estimate is above ₹200 (a setting; none of today's 268 tools reaches it with a normal input) does not run. It answers confirmation_required (HTTP 428) with the full quote, ₹0, no call recorded and nothing held. An agent shows the user the estimate; on a yes it resends exactly the same input with confirm: true inside input. Tools flagged as always needing confirmation (get_domain_history today; deep research, when it is switched on) behave the same way whatever the estimate.
Repeats are free
Send an idempotency_key with a call (any string unique to the request, up to 128 characters) and a retry is safe: a finished call is replayed from storage for ₹0 for 24 hours, a key still running answers in_progress, the same key with a different input is refused, and a purged replay says replay_expired. The exact rules and every outcome are in Conventions.
The usage log
Every call, charged or free, is a row in the dashboard's usage log at app.parel.si: the tool, the time, the price, the outcome (ok, or "failed, charged ₹0" with the error code), the latency, the key that made it and the client_tag you sent. A failed call never removes money; a hold that is somehow left open expires on its own (one hour for a normal call, 24 hours for a slow job) and is swept back to the balance by the hourly housekeeping job.
Where the numbers come from
Prices on this site are generated from the tool catalog and the day's exchange rate with the wallet's own price function, then written into the pages; nothing is typed by hand. The live figure for your account is always discover_tools, inspect_tool or GET /v1/tools/:id.
This page as Markdown: /docs/how-it-works.md. Something wrong or missing: hello@parel.si.