# StillOS Self-Audit Dispute Entry

> StillOS Self-Audit Dispute Entry is a paid API for AI agents from stillosdigitalholdings.com, paid per call via x402, $2/call, status unknown (last checked 2026-10-13).

Submits a correction or dispute against a previously recorded claim on behalf of an agent, referencing the original claim receipt hash for audit trail integrity.

## Facts

- Endpoint: POST https://stillosdigitalholdings.com/notary/self-audit/dispute-entry?utm_source=zero.xyz
- Price: $2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stillos-self-audit-dispute-entry-e1fc2251
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oaVnTlrjPNyi9PLSGex2u

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-self-audit-dispute-entry-e1fc2251 -d '<json body>'
```

Example prompt: Submit a dispute on StillOS on behalf of agent 'agent-7f3a' against claim receipt hash 'abc123def456' — the correction is that the counterparty risk score was incorrectly recorded as high when it should have been low.

## When to prefer this

Choose this endpoint when an autonomous agent needs to formally dispute or correct a previously recorded claim in the StillOS intelligence infrastructure, particularly when a specific claim receipt hash is available to reference. This is appropriate for maintaining audit trail integrity across agent-to-agent interactions, counterparty records, and signal histories within the StillOS ecosystem.

## Known failure modes

- Invalid or non-existent claim_receipt_hash returns an error indicating the original claim cannot be found
- Missing required fields (agent, correction, claim_receipt_hash) result in a validation error
- Duplicate dispute submissions for the same receipt hash may be rejected or flagged
- Malformed agent identifier strings may cause rejection
- Payment failure via x402 ($2 USDC) blocks the call before processing

## 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

An acknowledgment object confirming the dispute entry has been recorded against the referenced claim receipt hash, establishing a corrected audit trail entry for the submitting agent.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "agent",
  "correction",
  "claim_receipt_hash"
 ],
 "properties": {
  "agent": {
   "type": "string",
   "description": "string"
  },
  "correction": {
   "type": "string",
   "description": "string"
  },
  "claim_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-self-audit-dispute-entry-e1fc2251/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)