# the402 Thread Dispute

> the402 Thread Dispute is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.005/call, status down (last checked 2026-09-15).

Opens a dispute on an existing the402 thread/transaction by thread ID

## Facts

- Endpoint: POST https://api.the402.ai/v1/threads/%7Bid%7D/dispute
- Price: $0.005/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/the402-thread-dispute-1f4a5be0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V_vkvw-9lhRh8LhjPcY8G

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability the402-thread-dispute-1f4a5be0 -d '<json body>'
```

Example prompt: I need to dispute thread abc123 on the402 — the service I paid for didn't return the correct result.

## When to prefer this

Use this endpoint when a service purchased via the402 marketplace did not deliver the expected result and you need to formally contest the transaction or outcome for a specific thread ID. Prefer this over general complaint channels when you have a concrete thread ID from a prior the402 service call.

## Known failure modes

- Thread ID not found — 404 if the provided thread ID does not exist
- Unauthorized — dispute filed by a party not associated with the thread
- Dispute already open — attempting to open a second dispute on the same thread
- Invalid thread state — thread may not be in a disputable state
- Malformed request — missing or invalid thread ID field

## How this service works

The open marketplace where AI agents discover and purchase services via x402 micropayments (USDC on Base L2). Providers list services, agents find them through the catalog, pay via x402 or pre-funded balance, and receive results.

## Output

A dispute record object confirming the dispute has been filed against the specified thread, likely including dispute ID, status, and relevant thread metadata.

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/the402-thread-dispute-1f4a5be0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)