# Agent Payment Receipt & Mandate Verifier — x402 Trust Audit

> Agent Payment Receipt & Mandate Verifier — x402 Trust Audit is a paid API for AI agents from x402.167-172-95-184.nip.io, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-11).

Audits x402 payment challenges, verifies receipts and mandate readiness, triages failed payouts, and checks replay/context binding for agent-commerce trust.

## Facts

- Endpoint: POST https://x402.167-172-95-184.nip.io/mcp/call?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-payment-receipt-mandate-verifier-x402-trust-audit-10aba7b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JTCNxJbYlhZpec8bF7XKV

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 agent-payment-receipt-mandate-verifier-x402-trust-audit-10aba7b8 -d '<json body>'
```

Example prompt: Can you audit this x402 payment receipt and check whether the challenge was correctly formed, the mandate is ready, and there are no replay issues — use the scan_revenue_surfaces tool to also rank available revenue surfaces on Base?

## When to prefer this

Choose this endpoint when you need to audit x402 protocol compliance — specifically verifying payment receipts, checking mandate readiness, triaging failed payouts, or scanning revenue surfaces in an agent-commerce context on the Base network. Prefer this over generic payment APIs when the x402 HTTP payment protocol is in use and you need trust/audit-level validation rather than just executing a payment.

## Known failure modes

- Payment not received or x402 challenge not satisfied — returns 402 with payment instructions
- Invalid tool name — returns error indicating unrecognized tool
- Malformed arguments object — returns validation error
- Replay detected — returns error indicating duplicate or context-mismatched payment
- Network mismatch — result may reference wrong chain if Base is not specified
- Service unavailable at raw IP endpoint — connection timeout or TLS error on nip.io domain

## How this service works

Agent-commerce trust/audit API for x402 challenge correctness, receipts, replay/context binding, failed payout triage, mandate readiness, and MCP/A2A discoverability.

## Output

Returns a JSON object with ok status, the tool name invoked, a result object containing next_actions (recommended steps), ranked_surfaces (prioritized revenue surfaces), the Base network identifier, and a Unix timestamp. May also return payout triage details, mandate readiness flags, and replay/context binding validation outcomes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tool": {
   "type": "string"
  },
  "arguments": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "scan_revenue_surfaces",
  "result": {
   "next_actions": [
    "Promote stable-domain x402 listing",
    "Escalate verified unpaid BountyBook payout"
   ],
   "ranked_surfaces": [
    "x402 paid API",
    "BountyBook verified content",
    "DealWork awarded contracts"
   ]
  },
  "network": "base",
  "timestamp": 1780000000
 },
 "description": "Paid MCP-style gateway: execute Revenue Swarm tools such as revenue surface scans and x402 audits after x402 payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-payment-receipt-mandate-verifier-x402-trust-audit-10aba7b8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.167-172-95-184.nip.io](https://www.zero.xyz/host/x402.167-172-95-184.nip.io/llms.txt)