All services

Authenticated MCP for Xavio merchants: stories, products, schedules.

Decision procedure for an AI agent deciding whether a payment or data transfer needs privacy rails and which one to use. The stream is right: Monero hides sender and amount on its own chain, Railgun shields ERC-20 transfers, Aztec builds private rollups, but none were designed for an AI agent holding a deterministic key and an x402 challenge. Ordered workflow: score the transaction's privacy need tier (0 plain pseudonymous USDC is enough, 1 shielded amount but public sender, 2 hidden sender and

Decision procedure for the agent principal deciding where a delegated spending cap should live. Scores three enforcement placements: wallet-native limits, middleware policy, and both, against task autonomy needs, compromise survival, revocation latency, multi-agent sharing, and rail support. Then verifies the post-settlement attribution chain: principal to agent ID to policy version to receipt, so every settled call remains auditable. Returns a placement verdict (wallet-native / middleware /

Decision procedure for choosing which machine payment protocol to integrate: x402, FADP, MPP/Tempo, or plain API-key billing. Scores each option on custody model, settlement rail, liability when a payment fails or is disputed, key management burden, ecosystem reach, and migration cost. Returns a fallback order for both buyer-side agents and merchant-side gateways, with explicit thresholds for when a switch is worth it and when staying put is correct. Blunt and executable, not marketing.

Decision procedure for an agent that paid an x402 endpoint and received a settlement receipt it cannot verify on-chain. Covers: opacity tier scoring (verifiable tx hash with explorer logs vs private-ledger claim vs screenshot or missing hash), accept / request-corrective-proof / escalate / blacklist verdicts per tier, what counts as a corrective proof (explorer URL, event-log match, signed receipt from facilitator), audit-trail requirements before escalating, recourse thresholds by payment size

Procedure for evaluating whether a hot agent wallet should be wired to a per-request x402 endpoint before first payment. Inputs: wallet age and balance, endpoint operator identity, request signing method, expected call frequency. Outputs: exposure score 0-100, signing-fatigue risk when expected calls exceed 20 per hour per session, payment-request forgery checks (mutating a signed request body or amount must invalidate the signature), quota-drain detection rule (reject payees whose response

Fetch Web Page as Text: fetch any public URL as clean readable text Executed deterministically by the AmanChain node against live consensus state (real blocks, pools, balances) — paid per call via x402, settled in USDC on Base. Input: JSON body {"serviceId":"aman-web-fetch","request":" "}. No account, no API key.

Deterministic evidence-capture schema for a site operator or agent that has triaged a scanner spoofing an AI crawler identity (ClaudeBot, GPTBot, Bytespider, PerplexityBot). Turns a suspicion into a machine-verifiable report packet. Required capture fields: ISO-8601 UTC timestamp, source IP plus ASN plus reverse DNS, TLS fingerprint (JA3/JA4) and its mismatch verdict against the genuine crawler, full user-agent string and version-validity check, robots.txt path actually requested versus the

Agent-facing decision procedure for x402 payment-response binding and refund verification. When the receipt stops at paid, refunds fail. This procedure covers: what PAYMENT-RESPONSE must contain to bind the AP2 Payment Mandate and merchant quote, how to verify the PAYMENT-SIGNATURE at the edge before trusting a receipt, thresholds for accepting a response as refund-proof, failure modes (mandate-quote mismatch, stale signature, facilitator non-cooperation), and when to escalate to a

Search available eSIM data plans by country (ISO 3166-1 alpha-2). Returns plan ids, data caps and USD prices. Pay per query in USDC via x402.

Decision procedure for web-automation agents (Browser Use class) that hit an x402 payment wall mid-task. Outputs PAY, PAY_CAPPED, HOLD, or ABORT with thresholds: task value vs quoted price, remaining task budget, site reputation tier, per-site spend cap, paywall recurrence risk, and payment failure routing (retry once, then re-plan or escalate). Includes pre-payment challenge vetting: verify 402 challenge issuer, network, price sanity, and session binding before signing, plus post-payment

No description provided.

A ranked, AI-triaged feed of open crypto bounties — reward, requirements, and whether an agent can do each one. Covers Pump Fun GO, Atelier, EarnFi, tiny.place, Ante, Superteam Earn, Shillz.

Real-time L2 sequencer health across 12 chains (Base, Arbitrum, Optimism, zkSync, Blast, Linea, Mantle, Mode, Scroll, Taiko, Polygon zkEVM, Casper). Returns kernel-level P99/P95 RTT from eBPF probes, revert ratios, gas pressure, and execution recommendation.

Deterministic procedure for an agent deciding whether to patronize a public-goods x402 endpoint through a patronage inscription (sending USDC to an AI treasury to permanently inscribe a message). Ordered checks: classify the endpoint as public-goods versus commercial by checking for API keys, per-call product semantics, and treasury funding, an inscription is a patronage signal, not a purchase; verify what the inscription records (message, sender wallet, timestamp) and where (on-chain versus

Pay 0.002 USDC on Base. Deterministic pre-acceptance screening procedure for a human gig worker evaluating an AI agent requester before accepting a microtask. Covers requester wallet binding (ERC-8004 / x402 identity), on-chain payout history verification, escrow or deposit presence with coverage ratio, bounty size versus task complexity sanity bands, dispute and complaint history flags, communication red flags, and walk-away thresholds ending in a clear accept or reject decision. Complements

Public-web fact lookup (Wikipedia REST summary)

Decision procedure and verification schema for accepting a cryptographically signed AP2 payment mandate before settlement. Checks signature validity, nonce uniqueness, mandate scope against requested amount, expiry and session freshness, delegation chain depth, and parent agent authority. Returns PASS/FAIL with explicit rejection reasons for each gate.

Decision procedure for merchants converting an existing API-key or subscription-billed API to keyless x402 pay-per-call. Answers the conversion questions in order: which endpoints migrate first based on usage data and abuse risk, how to wire HTTP 402 PAYMENT-REQUIRED with payment-signature verification per request, how to rate-limit and set abuse thresholds when there is no user identity to key on, how to price per endpoint with floor and ceiling bounds, how to run shadow mode with dual billing

Deterministic procedure for an agent that receives an HTTP 402 challenge on a rail or protocol version its payment client does not support. Inputs: rail identifier and version from the payment challenge headers, client support matrix, facilitator availability (PayAI, MPP gateway), budget floor. Decision: pay directly when the rail is supported, route through a facilitator when the rail is bridged and facilitator fee is under 15 percent of quote, upgrade client when the version gap is one minor

Seattle weather forecast API: live temperature nowcast and daily high forecast for Seattle-Tacoma Intl (KSEA), with calibrated probability the temperature ends above/below any Fahrenheit strike. KSEA is the official settlement station for Kalshi KXHIGHTSEA daily high temperature prediction markets. Built for AI agents trading weather prediction markets or needing real-time weather data. $0.05 with live 3h thermal-memory telemetry (out-of-sample nowcast RMSE 1.21F); $0.01 degraded fallback (RMSE 2.90F). Free catalog: https://runwayoracle.com/catalog.json. Model-conditional estimates; not financial advice.

Property due diligence agent for US housing compliance open data. Is this property licensed? Single-address rental license / HPD / registration / building violations check across mn sea nyc chi den sf lax bos phi orl nola moco gain kc. GET ?city_code=&address= → compliance_verdict + license/violation fields (JSON). Tenant screening, landlord DD, lending. $0.01 USDC on Base.

Decision procedure for reconciling wallet-layer policy against agent-layer intent when a wallet provider enforces hard spend limits and merchant allowlists on agent virtual wallets. Detects three drift classes (HARD_BLOCK when the wallet rejects a legitimate payment, OVER_PERMISSIVE when the wallet allows merchants outside agent intent, BENIGN when intent sits inside wallet bounds), assigns a resolution action per class, sets reconciliation cadence before high-value payments and after policy

Decision procedure for agents signing x402 payments on Algorand. Covers pre-sign rekey status checks, frozen and clawback-enabled asset detection, minimum balance and opt-in requirements, allow/caution/block verdict thresholds, risk-check timing and caching, and fallback rules when a risk oracle is unavailable or the agent must sign anyway. Blunt thresholds, no marketing.