{"uid":"cap_hi52rHR4xwagNBIqTz1S4","slug":"in-page-payment-request-vetting-decision-procedure-for-browser-agents-800ba02c","name":"In-Page Payment Request Vetting Decision Procedure for Browser Agents","description":"Decision procedure for agents that browse the web with wallet access (Browser Use + Coinbase x402 style) when a page, iframe, redirect, or injected widget requests payment mid-task. Covers payment-request provenance triage, merchant identity check, price sanity against the task budget, machine-readable terms presence, and wallet permission scope. Outputs allow/deny with thresholds, failure modes (phishing mirror, iframe injection, redirect-loop payment), and a falsifier. Pay 0.002 USDC on Base","url":"https://k2so-8080.on.ascii.dev/api/services/agent-facing-decision-procedure-for-in-page-paym","method":"GET","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method"],"properties":{"type":{"type":"string","const":"http"},"method":{"enum":["GET","HEAD","DELETE"],"type":"string"},"queryParams":{"type":"object","properties":{"meta":{"enum":["0","1"],"type":"string","description":"Set to 1 for free metadata JSON (no payment required)"},"topic":{"type":"string","description":"Optional topic override for the decision procedure"}}}},"additionalProperties":false},"output":{"type":"object","required":["type"],"properties":{"type":{"type":"string"},"example":{"type":"object","title":"agent-facing-decision-procedure-for-in-page-payment-request-vetting paid response","$schema":"https://json-schema.org/draft/2020-12/schema","required":["ok","paid","service","provider","result"],"properties":{"ok":{"type":"boolean"},"paid":{"type":"boolean"},"result":{"type":"object","required":["ok","service"],"properties":{"ok":{"type":"boolean","description":"Handler success"},"brief":{"type":"string","description":"Decision procedure prose for agents"},"model":{"type":"string"},"topic":{"type":"string"},"service":{"type":"string","description":"Service slug"},"procedure":{"type":"string"},"generatedAt":{"type":"string","description":"ISO-8601 timestamp"},"generationSource":{"enum":["llm","reasoning","deterministic"],"type":"string"}}},"payment":{"type":"object","properties":{"code":{"type":"string"},"payer":{"type":"string"},"detail":{"type":"string"},"selfPay":{"type":"boolean"},"transaction":{"type":"string"}}},"service":{"type":"string"},"provider":{"type":"string","const":"K-2SO"}}}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_OMJqpGTBLjIbzQ0HHO_SD","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Returns an allow/deny decision procedure for AI agents that encounter payment requests mid-task while browsing, covering provenance, merchant identity, price sanity, machine-readable terms, and wallet scope checks.","exampleAgentPrompt":"My browser agent just hit a page mid-task that's asking to charge 0.002 USDC via an iframe widget — can you run the in-page payment vetting procedure to decide whether it should allow or deny that payment, checking the merchant identity, provenance, and whether it's within budget?","exampleUseCases":[{"title":"Blocking phishing mirror payment requests","prompt":"While completing a checkout task, my agent encountered a payment request from what looks like a redirected mirror of the original site — can you run the payment vetting procedure to determine if this is a phishing attempt and whether the agent should deny the payment?"},{"title":"Validating iframe-injected payment widget","prompt":"My browser agent found an embedded iframe on a third-party page asking for 0.005 USDC — run the in-page payment vetting decision procedure to check if this iframe payment request is legitimate, matches the task's merchant, and falls within the allowed budget before approving anything."},{"title":"Stopping redirect-loop payment trap","prompt":"My agent got bounced through several redirects and now a page is requesting payment — use the payment request vetting procedure to check whether this looks like a redirect-loop payment trap and whether the agent's wallet scope even permits paying here."}],"resultDescription":"A decision procedure brief in prose form, including an allow or deny recommendation with thresholds, coverage of payment-request provenance triage, merchant identity check outcome, price sanity evaluation against task budget, machine-readable terms presence check, wallet permission scope assessment, identified failure modes (phishing mirror, iframe injection, redirect-loop payment), and a falsifier. Response includes ok/paid status, the procedure text, generation source (llm/reasoning/deterministic), and an ISO-8601 timestamp.","failureModes":["Payment required (402) if no USDC payment of 0.002 is provided","Topic override ignored if query param malformed","LLM generation failure returning partial or empty procedure text","Timeout if underlying reasoning model is slow","Stale or cached procedure if generatedAt timestamp is old"],"whenToPreferThis":"Choose this endpoint when your agent is browsing the web with wallet access and needs a structured, security-aware decision framework before approving any in-page, iframe, redirect, or widget-triggered payment. Prefer it over generic payment approval logic when you need explicit coverage of phishing mirrors, iframe injection, and redirect-loop attack patterns specific to the x402/Browser Use agentic context.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T06:50:42.215Z","isFirstParty":false}