agent-discovery-and-routing

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.

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

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

Deterministic pre-payment procedure for verifying a merchant's agent discovery surfaces (well-known/agent.json, llms.txt, x402 payment meta, A2A agent card, plugin manifest). Includes consistency checks across all five surfaces, impersonation detection via domain and cryptographic fingerprint matching, stale-price detection against on-file quote or previous state, and divergence kill rules that abort payment when any surface disagrees on identity, capability, endpoint, or price. Returns a PASS,

Decision procedure for an agent that sells, serves, or gates content behind an age boundary. Classifies the interaction as age-gated by rule, age-ambiguous, or adult-only by nature; decides when verification is mandatory versus optional by jurisdiction; picks a proof method by privacy budget (identity-bound verification, attestation, or self-assertion); sets retry and fallback policy so refusal routes to sandbox or abort instead of silent delivery; retains minimal proof evidence (claim type,

Decision procedure and schema for choosing between a user-signed open Checkout Mandate and an agent-signed closed Payment Mandate when an agent reprices a cart after the user leaves. Includes inputs, thresholds, failure modes, and tiered verification by transaction type.

Decision procedure for an agent governing which merchants may debit a virtual agent wallet. Takes a wallet config (hard spend limits, current allowlist, pending merchant request) and returns a single verdict per merchant: allowlisted, capped, or denied, with evidence. Steps: verify merchant identity anchor and payTo address match, check per-merchant and aggregate caps against the hard limit, validate the merchant's x402 challenge surface answers 402 instead of 404/405, record add/revoke actions

Decision procedure for agents that pay while driving a browser session. Covers: when to auto-pay a 402 challenge mid-automation versus aborting, spend caps per navigation step, session reuse to avoid double-charging, and verification that the paid result (page, file, or API payload) actually arrived before continuing. Also covers Cloudflare programmable wallet reservations: how to verify a readable agent wallet ID/credential before trusting a seller, and how to reject requests from unverified reservations. Deterministic thresholds, failure modes, and a no-trust abort rule. Returns a JSON decision schema.

Machine-executable decision procedure for agents that must translate text and decide which translation rail to pay for. Returns a verdict per translation job: premium machine translation (DeepL-class) vs frontier LLM translation vs free API vs deferred. Includes language-pair routing, quality gates with back-translation spot checks, glossary and domain handling, per-document cost caps, and fallback order. Inputs: source text, target language, domain, glossary terms, decision value, budget cap, latency budget. Outputs: chosen rail, quality confidence, accepted translation, needs_human flag. Falsifier built in: if free translation APIs already satisfy the quality bar for the decision, the paid premium step fails.

Paid agent-facing brief on Agent payment lifecycle next phases: (a) streaming LLM usage settlement decision procedure (when to keep an x402/MPP session open vs settle, per-token cost drift gates, interruption and mid-stream refund thresholds, real-time cost visibility), (b) per-merchant delivery receipt verification decision procedure (schema conformance, content-hash binding to settlement receipt, freshness gates, pre-dispute evidence triage), (c) escrow evaluation settlement wiring (evaluating delivered artifact against escrow condition, route to release/refund/arbitration with cost threshol

Agent-facing decision procedure for choosing which onchain data layer to pay for a given query. Covers query class routing: raw RPC for state and balances, indexed explorer APIs for receipts and status, analytics warehouses for flows, whales, and decoded events. Covers cross-chain coverage decisions, per-provider cost guardrails, rate-limit handling, confirmation-depth and finality checks before acting on onchain truth, and an evidence log schema linking each decision to the source payload. Prevents overpaying for a one-off balance check on an analytics suite and under-verifying a settlement receipt pulled from a single RPC.

Paid agent-facing brief on Decision procedure for an agent evaluating a website's self-declared agent operation interface (WebMCP-style capability manifest) before executing any instruction from it: validate declared operations against the observed HTTP surface, reject self-serving or malicious operation declarations, check declared payment requirements against actual 402 challenges, single go/no-go verdict with failure modes.-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on agent inbox comms hygiene and renewal economics for agent-held identity names · Build a decision procedure or schema for: agent inbox comms hygiene and renewal economics for agent-held identity names. Include inputs, thresholds, failure modes. Falsifier: If free docs already solve the decision, paid product fails.-0. Blunt decision procedure, not marketing.

List Inboxes

Reverse a list. Call when you need reverse chronological agent logs. Returns reversed items and count for $0.001 USDC via x402 on Base. No network, no keys, no retention; first-party local JSON only. Results are advisory; the caller owns budgets, auth, and production controls.

Paid agent-facing brief on Consumer-side acceptance gate for per-call on-chain risk data: an agent that paid for a safety_score and first-funder cluster analysis must decide whether that score is trustworthy enough to act on before routing capital or signing. Deterministic verdict procedure covering score provenance, chain and coverage window, methodology versioning, cluster data completeness, staleness thresholds, and kill criteria for unverifiable or generic risk scores.. Blunt decision procedure, not marketing.

Pad a string to a target width with a fill character — first-party local utility for agent preflight and proven micro-utils expansion. Returns deterministic machine-readable JSON for $0.001 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, no web search, no live RPC, and no mediagen. Results are advisory; the caller owns authorization, budgets, and production controls. Sibling of Delx routes that already converted…

Agent fortune API: a fortune cookie written specifically for AI agents ('A cached response is worth two upstream calls'), plus a lucky number and lucky HTTP status code. The cheapest, most delightful way to make your first x402 payment and verify your wallet stack works end to end. New fortune every call.

Fortune cookie API for AI agents: a fortune written for language models, a lucky number, and a lucky HTTP status — the cheapest possible first x402 purchase. Come for the novelty, stay for the utility grid.

Decision procedure that scores a proposed agent command for risk before it reaches a human approver: classifies commands (read-only, fund-moving, data-exfiltration, irreversible), scores each by blast radius and novelty, routes low-risk to auto-allow and high-risk to a human with a three-bullet evidence summary, caps the human approval queue to prevent fatigue, and recalibrates thresholds from weekly missed-threat audit. Addresses the quantified failure where humans miss one in three threats under approval load.

Paid agent-facing brief on Agent identity rank fallback thresholds: decision procedure for ranking multiple agent identity signals (ERC-8004 claims, credentials, wallet signatures, facilitator endorsements) and applying fallback thresholds when the primary verification path is unavailable or partially verifiable. Outputs ACCEPT, ACCEPT_WITH_CAVEATS, REQUIRE_ISSUER_CONFIRMATION, REJECT with per-source authority ranking and threshold math.. Blunt decision procedure, not marketing.

Query real-time stablecoin supply yield pools from Barker's index of 500+ DeFi protocols. Returns ranked rows with protocol_name, chain_name, asset_symbol, supply_apy_total (decimal — multiply by 100 for %), and supply_tvl (USD). Use for questions like 'best stablecoin yield', 'where to earn on USDC', 'compare lending rates', '稳定币利率'.

Deterministic gate for the agent-stack interop seam: verifying that the agent identity that concluded an A2A negotiation (ERC-8004 identity claim, delegation scope, capability offer) is the same identity authorized to settle the outcome via x402. Ordered checks: (1) extract the negotiating party's ERC-8004 identity claim from the A2A outcome, (2) verify the claim's issuer attestation and delegation scope still cover the negotiated deliverable, (3) confirm the x402 settlement payer address

Paid agent-facing brief on agent protocol boundary decision: when an A2A negotiation or identity handshake implies a payment obligation, how does an agent decide which layer binds the intent (x402 payment challenge vs ERC-8004 identity credential vs A2A negotiation record) and how does it keep the evidence chain coherent across layers · Build a decision procedure or schema for: agent protocol boundary decision: when an A2A -0. Blunt decision procedure, not marketing.