# LupaRiel AR Agent-Spend Settle-Ready Check

> LupaRiel AR Agent-Spend Settle-Ready Check is a paid API for AI agents from lupariel.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-30).

Checks whether a given Argentine payment hop (e.g. Mercado Pago) is ready for USDC settlement versus only fiat consent/auth, returning a boolean readiness flag with reasons.

## Facts

- Endpoint: GET https://lupariel.com/api/condition/settle-ready?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lupariel-ar-agent-spend-settle-ready-check-c00c3e0d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ARGjIO0UTCcBzjqDfGa2j

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-ar-agent-spend-settle-ready-check-c00c3e0d
```

Example prompt: Check whether Mercado Pago is settle-ready for USDC agent-spend in Argentina — I need to know if it passes the ar-settle-ready-v1 ruleset or why it fails.

## When to prefer this

Use this endpoint when your AI agent needs to pre-validate whether a specific Argentine fiat payment hop (like Mercado Pago) can actually settle in USDC before committing to an agentic spend flow. It is specifically designed for the Argentine market and x402 protocol context, making it the right choice when you need a structured, rule-based settle-readiness verdict with explicit reasons rather than a generic payment status check.

## Known failure modes

- Unknown or unsupported hop identifier returns an error or null result
- Network timeout on paid-per-call endpoint returns no response
- Malformed request body causes validation error
- Ruleset version mismatch if client expects a different ruleset than ar-settle-ready-v1
- Payment failure (x402) blocks the call before evaluation occurs

## How this service works

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

## Output

Returns a JSON object with a boolean `settle_ready` field, the hop name (e.g. 'mercado_pago'), a list of human-readable reasons explaining the readiness or failure, the ruleset version applied ('ar-settle-ready-v1'), and a disclaimer clarifying these are explicit LupaRiel rules rather than legal or oracle advice.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "hop": "mercado_pago",
  "reasons": [
   "Fiat consent/auth ≠ USDC settle",
   "Falta puente stable/PSP o riel x402."
  ],
  "ruleset": "ar-settle-ready-v1",
  "disclaimer": "Reglas explícitas LupaRiel; no es oráculo ni consejo legal.",
  "settle_ready": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lupariel-ar-agent-spend-settle-ready-check-c00c3e0d/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)