Skip to main content
Public beta. The filter set may receive new options (especially tags for sentence-execution). Treat enums as open and ignore unknown values.
A Miner query is defined by a single filter object — the same schema is used by POST /requests/count (free) and POST /requests/create (charges credits). This page explains every field, its valid values and how they combine.

kind (required)

Defines which type of asset you’re discovering. It’s the first filter to choose because it constrains which other fields can appear.
You cannot mix exclusive fields: tags with kind: judgement-bond or budget_years/natures with kind: sentence-execution fail with 400.

natures (only for judgement-bond)

Type of credit underlying the bond.
Combine both to include everything: "natures": ["alimentary", "common"].

budget_years (only for judgement-bond)

Budget years in which the bond was registered. Use to filter specific vintages — typically the registration year is the calendar year following the final judgment.

tags (only for sentence-execution)

Signals detected by Judit’s base that indicate a maturation stage of the execution.
Multiple tags are treated as OR — any lawsuit with at least one of the tags is included.

Amount range

There are two mutually exclusive ways to filter by amount:

Mode 1 — Free limits (amount_min / amount_max)

Use when you need a specific cut (e.g. “between R50kandR 50k and R 500k”).

Mode 2 — Pre-defined tier (amount_tier)

Use when you align with Judit’s commercial tiers — this is the recommended path because credit pricing is also tier-based.
Don’t combine the two modes. Sending amount_tier together with amount_min or amount_max fails with 400. Pick one.

tribunals

Array of numeric court IDs to include. Empty or absent = every court covered by Miner.
To discover the IDs: call GET /tribunals or check the full table.

responses_limit (only on /requests/create)

Optional cap on the number of lawsuits materialized in a query. Has no effect on /requests/count — count always returns the real total.
Use it to control cost when count returned a high volume and you only want a sample.

Combination rules

Summary of everything that fails with 400:

Full schema (quick reference)

Next steps

How billing works

cost calculation, price tiers and billing-error handling.

Court list

Full table of IDs accepted in the tribunals field.

Quickstart

Practical recipe with count → create → poll → paginate.

API Reference

Interactive spec to test every endpoint.