Documentation Index
Fetch the complete documentation index at: https://docs.judit.io/llms.txt
Use this file to discover all available pages before exploring further.
Public beta. The pricing model documented here is stable, but small tier adjustments may occur during beta. Always check the
cost returned by /requests/create before planning volume.POST /requests/create). POST /requests/count is free — always use it before creating to estimate volume and avoid surprises.
How cost is computed
Each lawsuit materialized in a query has a unit price defined by amount tier (amount_tier). Final cost is the sum of per-tier price multiplied by the number of lawsuits returned in each tier.
find for judgement-bond on TJSP/TJRJ without amount_tier (open query) and Miner returns:
| Tier | Lawsuits returned | Price per lawsuit (credits) | Subtotal |
|---|---|---|---|
0-100k | 320 | 5 | 1,600 |
100k-250k | 180 | 10 | 1,800 |
250k-500k | 95 | 20 | 1,900 |
500k-750k | 40 | 30 | 1,200 |
750k-1.5M | 25 | 50 | 1,250 |
1.5M+ | 12 | 100 | 1,200 |
| Total | 672 | 8,950 |
/requests/create response would carry:
status: failed) due to a server-side issue, we’ll proactively contact your team to refund.
Strategies to control cost
1. Always use /requests/count first
Knowing total_lawsuits before purchasing avoids 90% of the surprises. Count is free and synchronous.
2. Narrow with amount_tier or amount_min/amount_max
If you only want assets above R$ 250k, filtering upfront avoids paying for lawsuits you’d discard later.
3. Cap volume with responses_limit
For experimentation or sampling, set a ceiling:
4. Don’t re-run identical queries
count already excludes lawsuits your company has retrieved before. If you run the same query twice, the second count will return zero (or only what was added to the base since). This protects your balance.
Billing errors (HTTP 403)
Miner uses403 with readable codes in the error payload:
| Code | Meaning | How to fix |
|---|---|---|
MISSING_CONFIGURATIONS | Your account doesn’t have the Miner plan configured (no price tiers). | Request configuration from the commercial team. |
MISSING_CREDITS | The company has no credits provisioned. | Top up the balance on the dashboard. |
INSUFFICIENT_CREDITS | There’s balance, but not enough for the computed cost. | Reduce responses_limit, narrow the filters, or top up. |
Refunds
- Server-side failure (
status: faileddue to our issue): full refund, manual via support. - Plan-side post-debit failure (rare): full refund.
- Cancellation while
pending: no refund — the work has been queued.
request_id to support.
How to track consumption
Eachfind creation appears in your account history with:
request_id(Miner ID)created_atcost(credits debited)- final
status(completed/failed)
GET /requests/{request_id} to inspect individually. For a consolidated view, Consumption shows the monthly aggregate across all Judit products, including Miner.
Next steps
Quickstart
See count → create → poll → paginate in action.
Concepts
Understand which filters to combine to narrow cost.
Supported courts
Full list of IDs for the
tribunals filter.Consumption
Consolidated view of credit consumption per product.