malformedlisted in Coinbase#27 by calls of 66 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- malformed
- Uptime, 7 / 30 / 90 days
- 0% / 0% / 0%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-08 23:23 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 29 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
courtlistener cases answered the sweep of 2026-09-15 with a 402 that failed the required check bazaar.routeTemplate.matches_resource.
For courtlistener cases the failing check asks whether the declared route template matches the resource path.
courtlistener cases answers POST requests at vaaya.ai; it is listed in the Coinbase registry and TOLL files it under inference.
courtlistener cases is priced at 0.01 USDC on Base.
Callers of courtlistener cases supply a json body with the fields q and court.
A response from courtlistener cases, as declared, includes ok, data and charged_cents.
courtlistener cases drew 2 calls from one payer in the trailing 30 days.
The last call to courtlistener cases came 7 days before the snapshot, 2026-09-08.
courtlistener cases shares vaaya.ai with 65 other listed endpoints and is tied 27th by calls with 13 others.
courtlistener cases is priced above 25% of comparable listings in inference.
Closest in price to courtlistener cases within inference: chat completions at x402.aispace.bot and who gho timeseries at api.hergertsynthora.com.
The wallet paid by courtlistener cases is the payee of 69 endpoints on one host.
The seller's tags on courtlistener cases are courtlistener, ai-agents and pay-per-call.
Exactly this price appears on 915 other listings in inference.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x7c655d…806C40 |
the checks, as of 2026-09-15 05:43 UTC · method · pinnableendpoint answered HTTP 402
bazaar.routeTemplate.matches_resource· the declared route template matches the resource path
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 05:43 UTC | malformed | 1 | daily-2026-09-15 |
| 2026-09-14 05:16 UTC | malformed | 1 | daily-2026-09-14 |
| 2026-09-13 05:11 UTC | malformed | 1 | daily-2026-09-13 |
| 2026-09-12 07:28 UTC | malformed | 1 | daily-2026-09-12 |
| 2026-09-11 11:13 UTC | malformed | 1 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-08 23:22 UTC · method · live
The input and output block
{
"input": {
"body": {
"q": "trade secret injunction",
"court": "cand"
},
"type": "http",
"method": "POST",
"bodyType": "json",
"pathParams": {}
},
"output": {
"type": "json",
"example": {
"ok": true,
"data": {},
"charged_cents": 1
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "courtlistener cases on vaaya.ai", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/vaaya-ai-api-run-courtlistener-cases-84f781/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-vaaya-ai-api-run-courtlistener-cases-84f781-2026-09-15T21-20Z,
author = {TOLL},
title = {courtlistener cases on vaaya.ai},
howpublished = {\url{https://tollindex.com/e/vaaya-ai-api-run-courtlistener-cases-84f781/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.