Back to Browse
LupaRiel AR Agent-Spend Settle-Ready Check
x402
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-10-03).
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.
Price / call$0.02
Success—
StatusUnknown
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.
Example use cases
Pre-flight check before autonomous AR payment
“Before my agent pays for a service in Argentina through Mercado Pago, check if that hop is actually settle-ready for USDC or if it's stuck at fiat consent only.”
Debugging a failed agentic payment rail
“My agent tried to settle through a Mercado Pago hop in Argentina and it failed — can you run the settle-ready check on that hop and tell me exactly why it's not ready?”
Evaluating PSP options for AR agent wallet
“I'm building an agent that spends in Argentina and I need to know which fiat hops like Mercado Pago actually support USDC settlement versus just doing consent auth — can you check settle-readiness for Mercado Pago?”
Technical details
Endpoint
GEThttps://lupariel.com/api/condition/settle-ready?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Output
Schema · Response
{
"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
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"