80trust / 100

Law Case Search

by 2s in Search & web

x402 APIPassing, checked 2 h ago

Search US court opinions (SCOTUS, federal circuits, state appellate/supreme — ~9M opinions). Query by free-text (party names, keywords, docket #, citation). Filter by court slug (e.g., "scotus", "ca9", "nysupct"), filing date range, and order (relevance/dateFiled-desc/dateFiled-asc/citeCount-desc). Returns clusterId, caseName, court, year, docket, reporter citations, citationCount, snippet, canonical URL. Discovery-side complement to case-verify. Backed by CourtListener (Free Law Project); underlying opinions are public domain.

GET
https://2s.io/api/law/case-search
Price
$0.009
per call in USDC
Uptime
100%
last 30 days
Response time
274 ms
507 ms slowest 5%
Last check
Passed
2 h ago, next any minute now

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

GET https://2s.io/api/law/case-search

Each call costs $0.009 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.

GET https://2s.io/api/law/case-search?court=example&filedAfter=2024-01-01&filedBefore=2024-01-01&limit=10&order=relevance&q=xx

Parameters

ParameterTypeRequiredDescription
courtstringNo
filedAfterstringNo
filedBeforestringNo
limitintegerNo Default: 10.
orderstringNo One of: relevance, dateFiled-desc, dateFiled-asc, citeCount-desc.
qstringYes

Example response

The listing has no example response.

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.009.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://2s.io/api/law/case-search?court=example&filedAfter=2024-01-01&filedBefore=2024-01-01&limit=10&order=relevance&q=xx'

# 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 - 'https://2s.io/api/law/case-search?court=example&filedAfter=2024-01-01&filedBefore=2024-01-01&limit=10&order=relevance&q=xx' \
  | 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.009 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.009" });
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.009 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F2s.io%2Fapi%2Flaw%2Fcase-search
const res = await pay("https://2s.io/api/law/case-search?court=example&filedAfter=2024-01-01&filedBefore=2024-01-01&limit=10&order=relevance&q=xx");
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.009 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.009"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://2s.io/api/law/case-search?court=example&filedAfter=2024-01-01&filedBefore=2024-01-01&limit=10&order=relevance&q=xx")
    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
2 h agoPassed402274 ms$0.009
6 h agoPassed402251 ms$0.009
11 h agoPassed402539 ms$0.009
15 h agoPassed402260 ms$0.009
20 h agoPassed402286 ms$0.009
Show 10 older checks
24 h agoPassed402499 ms$0.009
28 h agoPassed402254 ms$0.009
32 h agoPassed402231 ms$0.009
36 h agoPassed402359 ms$0.009
41 h agoPassed402218 ms$0.009
45 h agoPassed402225 ms$0.009
2 days agoPassed402266 ms$0.009
2 days agoPassed402301 ms$0.009
2 days agoPassed402381 ms$0.009
3 days agoPassed402356 ms$0.009