dispute readiness derived
peoplescourt.aiMarket dataderived
POST https://peoplescourt.ai/api/x402/dispute-readiness
passlisted in Coinbasecounted above 39% of Market data
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-02 14:36 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 2
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 28 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.
At peoplescourt.ai, dispute readiness takes POST requests, is listed in the Coinbase registry, and falls under market data by TOLL's rules.
dispute readiness is priced at 0.01 USDC on Base Sepolia.
The request to dispute readiness is a json body with the fields remedy, claimantType, respondentType, settlementRail, corpusAmountUsd, amountInDisputeUsd and 2 others.
dispute readiness accepts payment on Base Sepolia and Base, 2 options in all, to 2 different wallets.
A response from dispute readiness, as declared, includes lane, timing, filingFee, composition, disclaimers, readyToFile and 2 others.
dispute readiness answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
dispute readiness is the only listed endpoint on peoplescourt.ai.
The registry's counters give dispute readiness 2 calls and 2 unique payers over 30 days, every call from a different payer.
The last call to dispute readiness came 13 days before the snapshot, 2026-09-02.
Closest in price to dispute readiness within market data: price at svm402.com and address current balance at api.nansen.ai.
dispute readiness is priced above 37% of comparable listings in market data.
Its payee wallet receives for this endpoint alone.
The seller's tags on dispute readiness are arbitration, disputes, readiness and agents.
Exactly this price appears on 1,309 other listings in market data.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x1f08Ba…4C1157 |
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x1DB047…19FBd3 |
the checks, as of 2026-09-15 06:52 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 06:52 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:20 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:10 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:28 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:36 UTC | pass | 0 | 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-02 14:36 UTC · method · live
The input and output block
{
"input": {
"body": {
"remedy": "corpus_allocation",
"claimantType": "ai_agent",
"respondentType": "ai_agent",
"settlementRail": "x402r",
"corpusAmountUsd": 20,
"amountInDisputeUsd": 20,
"escrowWindowEndsAt": "2026-07-25T12:00:00.000Z",
"fastTrackClaimClass": "non_delivery",
"claimantEvidenceReady": true,
"mutualConsentReported": true,
"authorityToBindReported": true,
"respondentEvidenceReady": true,
"microClaimsTierConsentReported": true,
"remedialJurisdictionOptInReported": false
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"lane": "agent",
"timing": {
"warning": null,
"escrowWindowEndsAt": "2026-07-25T12:00:00.000Z"
},
"filingFee": {
"tier": "panel",
"percent": 5,
"currency": "USD",
"floorUsd": 10,
"amountUsd": 10,
"collectionNote": "This published filing-fee quote is separate from the $0.01 price paid for this readiness report.",
"panelSurchargeUsd": 0
},
"composition": {
"value": "panel",
"reason": "human_or_mixed_three_member_panel"
},
"disclaimers": {
"caseFiled": false,
"statement": "This automated report checks structured technical readiness only. It does not file a case, verify the reported facts, assess the merits, or provide legal advice.",
"legalAdvice": false,
"meritsAssessed": false,
"reportedFactsVerified": false
},
"readyToFile": true,
"requirements": [
{
"code": "bilateral_consent",
"detail": "Both parties must provide case-bound consent under the published Rules before merits review.",
"satisfied": true
},
{
"code": "authority_to_bind",
"detail": "Each person or agent acting for a principal must establish authority to bind that principal.",
"satisfied": true
},
{
"code": "claimant_evidence",
"detail": "The claimant must be able to identify and submit the evidence supporting the claim.",
"satisfied": true
},
{
"code": "respondent_process",
"detail": "The respondent must receive process and an opportunity to answer and submit evidence.",
"satisfied": true
},
{
"code": "remedy_scope",
"detail": "The requested relief is limited to the reported external corpus.",
"satisfied": true
}
],
"supportedLane": true,
"corpusCompatibility": {
"detail": "The requested relief is limited to the reported external corpus.",
"compatible": true
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "dispute readiness on peoplescourt.ai", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/peoplescourt-ai-api-x402-dispute-readiness-e7bb9a/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-peoplescourt-ai-api-x402-dispute-readiness-e7bb9a-2026-09-15T16-57Z,
author = {TOLL},
title = {dispute readiness on peoplescourt.ai},
howpublished = {\url{https://tollindex.com/e/peoplescourt-ai-api-x402-dispute-readiness-e7bb9a/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.