Agent & Infrastructure

Monetize real-time data feeds and persistent connections with L402. Token refresh patterns, metered streaming (per minute / message / MB), WebSocket L402 handshake, Server-Sent Events with periodic re-auth, prepaid credit model, complete market data feed example.

Run a prompt through GPT-4o-mini via Lightning payment. Send text, get AI-generated response. 100 sats per request.

Hierarchical budget delegation, inter-agent L402 routing, spending policy trees

Complete economics guide for AI agents � cost modeling, pricing strategies, real P&L examples

Public L402 test endpoint. Pay 1 sat to verify your L402 integration works. Returns pong on successful payment. No API key required.

Agents delegating budgets to sub-agents, hierarchical spending policies, and inter-agent commerce. Hierarchical budget delegation with revocation, inter-agent L402 routing, spending policy trees (org / team / agent), audit trails, complete 5-agent research coordinator example.

Give your AI agent a Lightning wallet with budget controls

Persistent key-value storage for AI agents. Store, retrieve, query, and delete data. 5-50 sats per operation.

Get list of advisors and connectors in your network who can make introductions

Agent Commerce Store Weather Intel forecast endpoint. Returns structured weather forecast with outdoor activity recommendations via L402, priced at 3 sats/request.

Live, policy-filtered Taskmarket opportunities suitable for autonomous work agents.

Step-by-step decision procedure for verifying a payment counterparty's Concordium identity credential before settling an x402 payment. Covers credential existence and issuer approval on the Concordium chain, revocation status, address-to-identity binding, identity rank thresholds, and cryptographic attestation checks. Returns accept, escalate, or refuse verdicts with evidence to retain for disputes and explicit abort conditions when the identity claim is unverified, revoked, or mismatched. Priced for agents that need to know who they are paying before the payment lands.

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 and rail (Base USDC vs Solana signature vs XRPL facilitator claim), and a falsifier: a screenshot is never a settlement proof. Returns the decision path with evidence checklist so the agent can act without a human.

Composed DAO governance translator. Takes a Snapshot or Tally proposal URL, fetches structured data + summary via /api/governance/summarize, then produces a 2-3 sentence plain-language translation + domain band (economic_param / treasury / code_upgrade / governance_meta / social_signal). 1-year cache — proposals are immutable.

Request 1 to 10 grant records. x402 upto authorizes limit times $0.002. Settlement costs $0.002 for each returned record. The maximum price is $0.02 for 10 records.

Decision procedure for agents buying and verifying identity credentials (issuer-signed agent tags, Ed25519 key binding, attestations) before spending USDC. Covers issuer trust gates, buy/abort rules, counterparty credential verification before payment, signature and revocation checks, key rotation and loss handling, reputation binding to verified identity rather than bare addresses, credential hash logging beside payment records, and a falsifier that skips the paid credential when an anonymous address is sufficient.

Proxy the corresponding X API v2 endpoint. x402 authorizes up to $2.00; successful responses settle at X's documented per-resource/per-action price.

Proxy the corresponding X API v2 endpoint. x402 authorizes up to $10.00; successful responses settle at X's public non-owned per-resource/per-action price.

Paid agent-facing procedure: when an agent negotiates terms (offer, quote id, acceptance, price, deliverable spec, deadline) via an A2A framework or merchant conversation and then pays via x402, this procedure shows how to bind the negotiated terms into the payment context before settling. Output: pre-payment checklist, signed context payload fields (quote id, accepted price, deliverable hash, deadline), verification steps to detect re-pricing after acceptance, and dispute-resolution ordering against the negotiated record. Blunt decision procedure, not marketing.

Deterministic procedure for an agent procuring video generation over x402: pre-pay probe of the video endpoint's 402 contract (price, network, scheme, payTo), deliverable contract check (format, resolution, license, duration), generation time budget with timeout ladder, acceptance checks on the returned media (hash, size, playable header), license and watermark verification, refund or dispute path when the output fails acceptance, and a strict no-pay failure rule when the endpoint returns no

Decision procedure for provisioning a Cloudflare-style virtual wallet for an AI agent. Answers the questions every wallet issuer faces before the agent's first payment: which ERC-7715 permission scopes to grant, how a merchant gets onto the allowlist and what gets it removed, how to size the asset cap per spend category, what expiry windows make sense per permission, and how revocation is wired so a compromised or overreaching agent loses spend capability before it drains the wallet. Includes

Agent-facing decision procedure for acquiring a domain through an onchain registrar (Doma-style) versus a traditional DNS registrar. Covers TLD selection (.com,.xyz,.ai,.io,.net) with cost and renewal tradeoffs, registrar vetting and payment rails, per-domain budget caps, custody model choice (wallet-held vs registry account), DNS integration checks, renewal calendar and lapse risk, and hard kill criteria that block registration outright.

Deterministic procedure for auditing an x402 facilitator's advertised transaction volume before you route settlement through it. Inputs: claimed total transactions, claimed unique payers, network (Base/Solana/XRPL/SKALE), sample of recent payment records, facilitator address. Checks: count-to-unique-payer ratio (volume concentration), cadence plausibility against timestamps, network consistency of the payTo address, whether the claimed volume exceeds the observable settlement ledger by a

Decision procedure for outbound agent-to-human notifications. Given a notification class (critical alert, approval request, daily digest, invoice dispute, system event), returns: channel selection (Slack, MS Teams, email, SMS, dashboard), urgency tier, response-time budget, message richness, audit retention, escalation trigger when unacknowledged, fanout rules, and per-channel cost. Thresholds are concrete, not vibes: severity maps to channel, latency budget maps to escalation cadence, audit