80trust / 100

Courtlistener Cases

by Vaaya in Search & web

x402 APIPassing, checked 24 min ago

Search 10M+ US court opinions (CourtListener v4). Pass `q` + optional `court` (e.g. cand, ca9, scotus), `judge`, `filed_after`/`filed_before`, `order_by` ("dateFiled desc"), `cursor` (pagination). Returns case names, courts, dates, cites, and absolute_url links to full opinions.

POST
https://vaaya.ai/api/run/courtlistener/cases
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
277 ms
585 ms slowest 5%
Last check
Passed
24 min ago, next in 8 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://vaaya.ai/api/run/courtlistener/cases

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://vaaya.ai/api/run/courtlistener/cases
content-type: application/json

{
  "court": "cand",
  "q": "trade secret injunction"
}

Parameters

ParameterTypeRequiredDescription
case_namestringNo
courtstringNo
cursorstringNo
docket_numberstringNo
filed_afterstringNo
filed_beforestringNo
judgestringNo
order_bystringNo
party_namestringNo
qstringYes

Example response

The provider's example. We can't check it without paying.

{
  "charged_cents": 1,
  "data": {},
  "ok": true
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://vaaya.ai/api/run/courtlistener/cases' \
  -H 'content-type: application/json' \
  --data-raw '{"court":"cand","q":"trade secret injunction"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://vaaya.ai/api/run/courtlistener/cases' \
  -H 'content-type: application/json' \
  --data-raw '{"court":"cand","q":"trade secret injunction"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fvaaya.ai%2Fapi%2Frun%2Fcourtlistener%2Fcases&method=POST
const res = await pay("https://vaaya.ai/api/run/courtlistener/cases", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "court": "cand",
    "q": "trade secret injunction"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://vaaya.ai/api/run/courtlistener/cases",
        json={
            "court": "cand",
            "q": "trade secret injunction",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
24 min agoPassed402317 ms$0.01
4 h agoPassed402256 ms$0.01
8 h agoPassed402292 ms$0.01
12 h agoPassed402232 ms$0.01
16 h agoPassed402338 ms$0.01
Show 10 older checks
20 h agoPassed402704 ms$0.01
24 h agoPassed402268 ms$0.01
27 h agoPassed402408 ms$0.01
30 h agoPassed402237 ms$0.01
33 h agoPassed402276 ms$0.01
36 h agoPassed402179 ms$0.01
39 h agoPassed402277 ms$0.01
42 h agoPassed402334 ms$0.01
46 h agoPassed402275 ms$0.01
2 days agoPassed402369 ms$0.01