# Dark Loom Revenue Ledger — Base USDC Settlement Audit

> Dark Loom Revenue Ledger — Base USDC Settlement Audit is a paid API for AI agents from 169.58.81.212, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Verifies and audits USDC settlement transactions on the Base blockchain by transaction hash, confirming transfer amounts, recipients, and confirmation status

## Facts

- Endpoint: POST https://169.58.81.212/v1/x402/settlement-audit
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dark-loom-revenue-ledger-base-usdc-settlement-audit-420f952c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QdM0FftL5flM6ZVODG9sR

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 dark-loom-revenue-ledger-base-usdc-settlement-audit-420f952c -d '<json body>'
```

Example prompt: Can you verify that the Base transaction 0xabc123...def456 actually settled and check that it sent at least 5000000 atomic USDC units to 0xRecipientAddress?

## When to prefer this

Choose this endpoint when you need deterministic, on-chain proof that a specific USDC settlement occurred on Base — especially for x402 payment verification, revenue reconciliation, or releasing access/goods after payment confirmation. Prefer this over general block explorers when you need structured JSON output with expectation matching (amount + recipient validation) that an agent can act on programmatically.

## Known failure modes

- Invalid txHash format (not a valid 0x-prefixed 64-char hex) returns validation error
- Transaction not found on Base returns an error or ok:false
- Transaction pending/unconfirmed may return low confirmation count
- expectedAmount or expectedRecipient mismatch returns expectations.matched:false (not an error, but requires agent to check)
- Network or RPC timeout may cause temporary failures
- Providing a non-Base chain transaction hash will fail or return unexpected results

## How this service works

Deterministic verification of Base USDC settlement transactions

## Output

Returns a JSON object with: overall verification status (ok), chain identifier, transaction details (hash, status, block number, confirmations), a list of USDC transfers found, a proof object with explorer URL and verification timestamp, expectation matching results (whether the expected recipient and amount were found), and the canonical USDC contract address on Base.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "txHash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "Base transaction hash"
  },
  "expectedAmount": {
   "type": "string",
   "pattern": "^[0-9]+$",
   "description": "Optional USDC amount in 6-decimal atomic units"
  },
  "expectedRecipient": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Optional expected USDC recipient"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "chain": "base",
  "proof": {
   "explorer": "https://basescan.org/tx/0x...",
   "verifiedAt": "2026-01-01T00:00:00.000Z"
  },
  "transfers": [],
  "transaction": {
   "hash": "0x...",
   "status": "success",
   "blockNumber": 1,
   "confirmations": 1
  },
  "expectations": {
   "matched": false,
   "recipient": null,
   "amountAtomic": null
  },
  "canonicalUsdc": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dark-loom-revenue-ledger-base-usdc-settlement-audit-420f952c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 169.58.81.212](https://www.zero.xyz/host/169.58.81.212/llms.txt)