# LupaRiel Settle Receipt Attestation (SKU#17)

> LupaRiel Settle Receipt Attestation (SKU#17) is a paid API for AI agents from lupariel.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-01).

Returns an informational on-chain USDC settlement attestation confirming a transaction was settled, explicitly distinguishing settle from consent or fiat authorization.

## Facts

- Endpoint: GET https://lupariel.com/api/settle/receipt?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lupariel-settle-receipt-attestation-sku-17-a9bf88c5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dYvoJKBPVyj0UKawbetg1

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 lupariel-settle-receipt-attestation-sku-17-a9bf88c5
```

Example prompt: Can you get me a LupaRiel settle receipt for transaction 0x6ec312ffab72460da6fae791711471a80b6375e0c89ccf1a509f73249caea14b on Base — I need the informational attestation confirming USDC settled and that this is not a consent or OAuth hop.

## When to prefer this

Choose this endpoint when you need a formal, paid informational attestation confirming that a USDC transaction settled on Base (eip155:8453) and require explicit documentation that the settle event is not a fiat consent, OAuth hop, or 3DS condition. Prefer it over generic blockchain explorers when the distinction between 'settle' and 'consent' needs to be formally attested with a structured receipt, particularly in x402 payment flows or agent-driven payment audits.

## Known failure modes

- Invalid or unrecognized transaction hash returns error
- Transaction not found on Base network
- Insufficient payment (requires $0.01 USDC per call via x402)
- Network mismatch if transaction is not on eip155:8453
- Malformed request body causes 400 error

## How this service works

Directorio público de x402, AP2, ACP y MPP. Fuente + fecha. No inventamos precios ni estados.

## Output

A JSON object containing the transaction hash, kind ('settle-receipt'), language, asset (USDC), network (eip155:8453/Base), product name, ruleset version, settled boolean, a summary description in the requested language, a disclaimer clarifying this is informational only and not a Basescan re-oracle, an attested_at timestamp, and a structured settle_vs_consent field explicitly distinguishing on-chain USDC settle from fiat/OAuth/3DS consent hops.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tx": "0x6ec312ffab72460da6fae791711471a80b6375e0c89ccf1a509f73249caea14b",
  "kind": "settle-receipt",
  "lang": "es",
  "asset": "USDC",
  "network": "eip155:8453",
  "product": "LupaRiel",
  "ruleset": "settle-receipt-v1",
  "settled": true,
  "summary": "Atestación informativa del settle on-chain Exact USDC en Base. No es consentimiento fiat ni un hop OAuth/3DS.",
  "disclaimer": "Not a consent hop or payment-plan condition. Informational settle attestation only. settled=true attests this paid response, not a Basescan re-oracle.",
  "attested_at": "2026-09-23T00:00:00.000Z",
  "settle_vs_consent": {
   "settle": "on-chain Exact USDC Base",
   "consent": "fiat/OAuth/3DS hop — NOT this endpoint"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lupariel-settle-receipt-attestation-sku-17-a9bf88c5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lupariel.com](https://www.zero.xyz/host/lupariel.com/llms.txt)