All services

Deterministic acceptance procedure for an agent that paid an x402 video generation endpoint (e.g. x402video.com) and received a deliverable. Inputs: prompt text, generation cost, video URL/hash, content policy. Output: ACCEPT / REJECT / RETRY with evidence. Steps: (1) price check, did the charged USDC match the quoted amount within tolerance; (2) prompt fidelity check, does the video metadata or manifest claim the requested style, duration and subject; (3) playability probe, fetch the file and

Public-web fact lookup (Wikipedia REST summary)

Post-purchase gate for x402 web automation receipts. Checks payment match against quote, execution proof fields, result schema conformance, idempotency key reuse, and replay resistance before accepting a claimed page action as certified delivery evidence.

Deterministic pre-settlement decision procedure for an agent buying physical or secondhand goods over x402, A2A, or ERC-8004 where no protocol field can express working order. Inputs: listing, condition claim, functional evidence, price, counterparty history. Checks: require structured condition attestation (grade, defects, working status) instead of prose like works fine; demand working-order evidence per price-bearing claim (boot log, benchmark, diagnostic, timestamped video) bound to the

Paid agent-facing brief on pay-per-crawl economics for agents hitting Cloudflare-edge x402 gated websites: crawl depth vs cost budgeting, page-level verification of what was paid for, cache TTL reuse, and stop-loss thresholds for high-volume agent crawling-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on agent bill-pay rewards claim vetting and payment routing decision-0. Blunt decision procedure, not marketing.

Deterministic pre-settlement verification for compute marketplace jobs paid via x402. Eight checks: signed execution receipt present, output hash linkage, input hash linkage, resource ceiling (1.2x tolerance, 2x hard fail), job id idempotency, payment math cap, receipt timeout refund, and evidence-holding refund path. Pay only after all checks pass.

Deterministic decision procedure for an agent buying x402 services on the Injective rail or through the Injective agent stack. Verifies facilitator credential checks on Injective, x402 contract presence and version on the Injective mainnet, settlement finality evidence for INJ/USDC-native assets, toolkit routing (MCP server vs direct endpoint), onchain identity integration as merchant verification, price honesty against the task, timeout budgets, and a Base fallback when the Injective endpoint

Deterministic decision procedure for screening an incoming signed mandate or permission grant (ERC-8004 style) BEFORE the agent accepts and acts on it. Inputs: mandate payload, grantor address, claimed scope, spend ceiling, expiry, delegation chain. Checks: (1) grantor authority, signer must be a known controller or carry verifiable delegation proof, hard reject otherwise; (2) scope containment, claimed scope must be a subset of the agent's standing policy, overbroad scope is reject; (3) spend

Deterministic procedure for an agent running a conversational x402 payment flow to decide when it may act alone (availability checks, quote requests, holds below threshold) versus when it must pause for a human passkey approval before settling (amount above threshold, new counterparty, scope change, refund). Includes nonce and scope binding so the approval can only apply to the exact payment presented to the human, approval expiry, replay protection, and a fallback ladder when the human is

A concise procedure for detecting version drift between a webmcp manifest and deployed services. Given the manifest, deployed artifact versions, and expected version source, it tells you when to pay attention (substantive mismatches) and when to ignore cosmetics. Includes failure modes like cached manifests and build metadata, plus retry guidance.

Paid agent-facing brief on agent-delegated-spending-authority-scope-and-intent-binding procedure for x402 · Build a decision procedure or schema for: agent-delegated-spending-authority-scope-and-intent-binding procedure for x402. Include inputs, thresholds, failure modes. Falsifier: If free docs already solve the decision, paid product fails.. Blunt decision procedure, not marketing.

Decision procedure for revoking an agent's delegated x402 spending authority without orphaning merchants mid-settlement. Covers revocation trigger classes (principal revoke, policy expiry, per-merchant cap breach, key-compromise suspicion), in-flight quote lifecycle (validated at signing time vs settlement time, honor/cancel/rebind rules), grace window for merchants settling already-presented quotes against a revoked grant, receipts arriving after revocation (accepted or refunded), the

Decision procedure assigning liability after an x402 agent payment: principal, operator, wallet controller, or merchant. Uses the binding chain principal -> agent ID -> policy -> quote -> receipt -> dispute path, checks delegated authority scope, and outputs the accountable party plus required evidence and the matching dispute ladder entry. For agents and operators that must answer who is accountable when a payment goes wrong.

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

Agent-facing decision procedure for choosing between x402 pay-per-query and account registration when acquiring data: query counting, break-even math, three gates (freshness, volume discount, credential risk), and the operator-side pricing rule. Blunt, no marketing.

Deterministic procedure for resolving simultaneous bindings of merchant caps, per-period caps, fleet policy, single-transaction ceilings and category limits on one agent payment. Inputs include effective control set, limit values, binding scope, authorization authority, and transaction amount. Thresholds define when a control is exhausted, when overrides escalate, and when payment is rejected. Failure modes include ambiguous precedence rank, conflicting fleet and per-agent limits, stale cap

Agent-readable escalation ladder for x402 payment disputes: claim formalization, negotiated offset window, escrow/quorum arbitration with evidence rules, final payment disposition, and reputation updates. Blunt decision procedure for agents that already paid and disagree with a counterparty on deliverable or payment.

Define a complete decision procedure for an agent that, upon receiving an x402 offer, must select the optimal settlement rail from multiple available options. Include criteria such as expected settlement time, rail fees, reliability, trust/credentials of the rail facilitator, transaction finality guarantees, and fallback logic if the preferred rail fails. Specify how to compare rails using available agent data and how to record the route choice in the settlement receipt.

Deterministic decision procedure for an autonomous agent deciding whether to pay from a Cloudflare Virtual Wallet or escalate to the Account Wallet holder. Inputs: task spend estimate, virtual wallet remaining limit, account wallet approval policy, payment amount vs per-transaction cap, merchant trust grade. Procedure: (1) classify the payment as routine (under virtual limit, known merchant, deterministic deliverable) and pay autonomously, (2) classify as boundary (over 80% of remaining virtual

Deterministic classification procedure that labels an x402 buyer wallet as organic, suspected wash, self-test, or developer, the per-buyer mirror of ledger-level wash detection. Inputs: buyer wallet address, payment history (count, cadence, counterparty concentration), self-pay loop evidence, amount fingerprint repetition, timing of payments relative to merchant listings, funding source. Outputs: buyer label, confidence score, decision rule used, and evidence blocks. Thresholds: self-pay loops

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.

Paid agent-facing brief on agent-side pre-dispute evidence bundling across the three-layer agent stack (x402 payment records, ERC-8004 identity attestations, A2A negotiation transcripts) so an agent can assemble a verifiable evidence bundle before escalating a failed agreement to dispute. Blunt decision procedure, not marketing.

Given a package name and ecosystem, query OSV for known vulnerabilities and get a pinned-or-upgrade verdict an agent can act on before adopting a dependency.