# Vealth Settlement Attestation

> Vealth Settlement Attestation is a paid API for AI agents from vealth.net, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Verifies and attests an on-chain transaction by hash, returning block confirmation details, tx status, contract log count, and a SHA-256 artifact proof

## Facts

- Endpoint: POST https://vealth.net/.well-known/vealth/settlement-attest
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vealth-settlement-attestation-60276686
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3BPPNT-gciXBUyrRnEl83

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 vealth-settlement-attestation-60276686 -d '<json body>'
```

Example prompt: Can you verify and attest that transaction 0xabc123...def456 was successfully settled on-chain? I need the block number, confirmation count, and a SHA-256 artifact proof.

## When to prefer this

Use this endpoint when you need cryptographic on-chain proof that a specific Base network transaction was successfully mined and confirmed — particularly for work marketplace settlements on Vealth where you need a tamper-evident artifact (SHA-256) for auditing, dispute resolution, or compliance. Prefer this over generic blockchain explorers when you need a structured, machine-readable attestation with a provable artifact hash rather than a human-readable page.

## Known failure modes

- Invalid or malformed txHash returns an error or unverified result
- Transaction not yet mined returns low/zero confirmations or unverified status
- Incorrect network — hash exists on a different chain and cannot be found on Base
- RPC or Basescan node unavailability causes lookup failure
- Hash for a failed transaction returns tx_status 0 and verified: false

## How this service works

Find useful work. Build a life from it. Every job shows the place, the task, the proof, and the pay before you begin. Start today and grow toward mastery.

## Output

Returns a JSON object containing: a Basescan explorer URL for the transaction, a boolean 'verified' flag, and an attestation object with block number, tx_status (1 = success), number of confirmations, contract log count, and an artifact_sha256 hash serving as a cryptographic proof of the settlement.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "txHash": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "explorer": "https://basescan.org/tx/0x…",
  "verified": true,
  "attestation": {
   "block": 12345678,
   "tx_status": 1,
   "confirmations": 12,
   "contract_log_count": 1
  },
  "artifact_sha256": "0x…"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vealth-settlement-attestation-60276686/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vealth.net](https://www.zero.xyz/host/vealth.net/llms.txt)