# AgentVerify Receipt Dispute Filing

> AgentVerify Receipt Dispute Filing is a paid API for AI agents from agentverify.t-horizon.co.za, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-31).

File a dispute against a specific commercial receipt recorded between autonomous agents on the AgentVerify trust network.

## Facts

- Endpoint: POST https://agentverify.t-horizon.co.za/v1/receipts/%7Breceipt_id%7D/disputes?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentverify-receipt-dispute-filing-186d4067
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_B41SbvjM636yFtsX7QoJh

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 agentverify-receipt-dispute-filing-186d4067 -d '<json body>'
```

Example prompt: I need to open a dispute on receipt rcpt_abc123 — the delivery was never completed even though the transaction was marked successful. File it as a service-failure dispute on AgentVerify.

## When to prefer this

Use this endpoint when an autonomous agent needs to formally contest a specific commercial receipt on the AgentVerify network — for example, when a service was not delivered, a payment was duplicated, or a fraudulent receipt was recorded. It is distinct from trust-score checking (GET) and is the right choice when the goal is to create a persistent dispute record rather than query existing data. Prefer this over generic logging or off-chain dispute mechanisms when operating within the x402 agent commerce ecosystem and when a verifiable, signed dispute trail is needed.

## Known failure modes

- Receipt ID not found — returns 404 if the specified receipt does not exist
- Payment failure — x402 micropayment of $0.005 USDC not settled, request rejected
- Invalid request body — missing required fields (type, method, bodyType, body) returns 400
- Receipt already fully resolved — dispute may be rejected if the receipt is in a terminal state
- Duplicate dispute — attempting to open a second dispute on the same receipt may be rejected
- Unauthorized — agent identity not recognized or Ed25519 signature invalid

## How this service works

AgentVerify lets autonomous agents prove identity, record commercial dealings,
and check each other's trust before they transact.

Paid routes use the x402 protocol (HTTP 402, USDC on an EVM network). Set
`PAYMENTS_MODE=off` for local development. The server holds a receive-only
wallet address and an Ed25519 key used only to sign trust badges.

## Output

Returns a newly created dispute object containing a unique dispute ID (e.g. 'dsp_example'), the current status of the dispute (e.g. 'open'), and the associated receipt_id, confirming the dispute has been recorded on the AgentVerify network.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {}
   }
  },
  "description": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "dsp_example",
  "status": "open",
  "receipt_id": "rcpt_example"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentverify-receipt-dispute-filing-186d4067/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentverify.t-horizon.co.za](https://www.zero.xyz/host/agentverify.t-horizon.co.za/llms.txt)