# StillOS Notary Dispute

> StillOS Notary Dispute is a paid API for AI agents from stillosdigitalholdings.com, paid per call via x402, $1/call, status unknown (last checked 2026-09-15).

Submits a dispute against a previously recorded notarized transaction or claim using an agent identifier and receipt hash, returning machine-readable dispute intelligence.

## Facts

- Endpoint: POST https://stillosdigitalholdings.com/notary/dispute
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stillos-notary-dispute-9f1ddbf2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Brd3-_YJBtP214BKtApqo

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 stillos-notary-dispute-9f1ddbf2 -d '<json body>'
```

Example prompt: File a dispute on StillOS against the notarized record with receipt hash 0xabc123def456 on behalf of my agent agent-7f3c — the claim recorded there is incorrect and I need it contested.

## When to prefer this

Use this endpoint when an autonomous agent needs to formally contest or dispute a previously notarized record, receipt, or claim within the StillOS intelligence infrastructure. Prefer this over generic dispute APIs when the dispute is tied to a machine-readable receipt hash and needs to propagate through trust and track-record systems that autonomous agents rely on.

## Known failure modes

- Invalid or missing agent identifier returns an error
- Malformed or unrecognized receipt_hash returns a rejection
- Duplicate dispute on the same receipt may return a conflict or idempotency error
- Receipt hash not found in the notary system returns a 404-equivalent
- Insufficient payment (requires 1 USDC via x402) causes a 402 Payment Required response

## How this service works

StillOS transforms signals, claims, counterparties, and track records into machine-readable intelligence that autonomous systems can act on with confidence.

## Output

Returns a machine-readable object confirming the dispute submission, likely including a dispute ID, status, or acknowledgment that the contested receipt has been flagged for review within the StillOS intelligence infrastructure.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "agent",
  "receipt_hash"
 ],
 "properties": {
  "agent": {
   "type": "string",
   "description": "string"
  },
  "receipt_hash": {
   "type": "string",
   "description": "string"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stillos-notary-dispute-9f1ddbf2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stillosdigitalholdings.com](https://www.zero.xyz/host/stillosdigitalholdings.com/llms.txt)