# AgentServices Dispute Resolution

> AgentServices Dispute Resolution is a paid API for AI agents from agentservices.to, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Submits a structured dispute claim between two parties (agents or addresses) under a named policy template, requesting a specified remedy

## Facts

- Endpoint: POST https://agentservices.to/v1/disputes
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentservices-dispute-resolution-b071ab62
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XKkiAk6CH4uVlik2II_KU

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 agentservices-dispute-resolution-b071ab62 -d '<json body>'
```

Example prompt: File a dispute under the 'freelance-delivery' policy — I'm agent 0xABC123 and I'm claiming against 0xDEF456 because they failed to deliver the agreed design assets. My evidence is the signed contract and the missed deadline email, and I want a full refund.

## When to prefer this

Choose this endpoint when an AI agent or autonomous system needs to programmatically file a structured dispute between two identified parties under a defined policy template, especially in agent-to-agent commerce, freelance delivery, or DeFi payment contexts. Prefer this over manual arbitration when the parties are identified by on-chain addresses or agent IDs and the dispute needs to be logged with evidence and a desired remedy in a machine-readable format. It is particularly well-suited for autonomous agents that need to escalate failed transactions or service breaches without human intervention.

## Known failure modes

- Missing required fields (policy, claimant, or respondent) returns a 400 validation error
- Unknown or unsupported policy template name causes rejection
- Invalid agent ID or address format for claimant or respondent causes a parsing error
- Payment failure via x402 prevents the request from being processed
- Duplicate dispute submission for the same parties and claim may be rejected or flagged
- Evidence array items that are malformed or too large may be truncated or rejected

## How this service works

Paid data APIs for AI agents. Crypto market data, DeFi yields, IP geolocation, dispute resolution, marketing intelligence. Powered by x402 micropayments on Base.

## Output

Returns a dispute case record including a unique case ID, the submitted policy, claimant and respondent identifiers, the claim description, evidence items, desired remedy, and an initial status indicating the dispute has been received and queued for adjudication.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "policy",
  "claimant",
  "respondent"
 ],
 "properties": {
  "claim": {
   "type": "string",
   "description": "What happened"
  },
  "policy": {
   "type": "string",
   "description": "Policy template name (e.g. freelance-delivery)"
  },
  "claimant": {
   "type": "string",
   "description": "Plaintiff address or agent ID"
  },
  "evidence": {
   "type": "array",
   "description": "Evidence items"
  },
  "respondent": {
   "type": "string",
   "description": "Respondent address or agent ID"
  },
  "desired_remedy": {
   "type": "string",
   "description": "What the claimant wants"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentservices-dispute-resolution-b071ab62/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentservices.to](https://www.zero.xyz/host/agentservices.to/llms.txt)