{"name":"Boundary Guard Agent Router","version":1,"updated_at":"2026-06-06","purpose":"Tell wallet-capable agents which Boundary Guard x402 endpoint to call for the buyer job in front of them.","service":"Boundary Guard","serviceName":"Boundary Guard","providerName":"Boundary Guard","providerUrl":"https://boundary-guard.vercel.app","category":"Data","categories":["Data","Infra","Search","Security","Agent observability","Lead enrichment"],"tags":["a2a","action-safety","agent-logs","agent-observability","agent-safety","agent-to-agent","agents","ai-runtime","audit-trail","before-payment-safety","budget-guard","chunking","contact-extraction","crm","data-enrichment","data-loss-prevention","data-quality","email-redaction","embeddings","evidence","guardrails","handoff","inference","ingestion","json","json-repair","json-schema","lead-brief","lead-enrichment","lead-gen","llm-output","logs","masking","mcp","model-routing","no-secret","normalization","parsing","payload-safety","payment-evidence","payment-safety","phone-redaction","pii","pii-detect","pii-detect-api","pii-redactor","pii-redactor-api","policy","privacy","prompt-injection","prospecting","rag","receipt-verification","receipts","redaction","research","retrieval","runtime-trust","safety","sales-intelligence","schema","scraping","scrubbing","search","secret-redaction","settlement-evidence","source-pack","spend-policy","storage-safe-text","structured-output","tool-calling","tool-gating","trust","validation","workflow-audit","workflow-routing","x402","x402-buyer-safety","x402-pii"],"network":"eip155:8453","currency":"USDC","first_public_link":"https://boundary-guard.vercel.app/buyer-quickstart","first_machine_link":"https://boundary-guard-x402.onrender.com/agent-router.json","default_flow":["Read this router manifest and choose the route whose buyer_job matches the current task.","Preview on the Vercel URL when the agent or human wants to inspect response shape without payment.","Pay through the Render x402 URL only when settlement, receipt evidence, or marketplace-visible paid usage is needed.","Keep internal seed payments separate from non-seed buyer revenue in any reporting."],"current_market_context":{"target_monthly_revenue_usd":10000,"strongest_current_offer":"/lead-brief-lite","why":"Data/search/enrichment and AI runtime access are high-volume x402 categories; Boundary Guard competes by packaging proof-safe, buyer-ready outputs with receipt evidence.","agentic_listing_gap":"Live Agentic normalized detail currently shows endpoint URLs/pricing/quality but blank provider/category/listing fields; this router is the canonical fallback for agent routing."},"agent_purchase_decision":{"decision_label":"Preview first; pay only when the next agent needs receipt-backed action evidence.","call_lead_brief_lite_when":["The buyer has public lead, company, contact, URL, or source facts and needs an outreach-ready brief.","The next workflow step is outreach, CRM prep, research handoff, AgentMail-style communication, or workflow audit.","A cheap x402-paid proof point is useful before spending on deeper enrichment, model routing, or human review."],"preview_is_enough_when":["The buyer is only comparing response shape, expected fields, proof boundary, or sample usefulness.","The payload is still missing enough public facts that the brief would not guide a next action.","The caller cannot make x402 payments and does not need settlement evidence."],"pay_when":["The previewed response is useful enough to act on and the buyer wants Base-mainnet x402 settlement evidence.","The buyer needs a Boundary Receipt, human_summary, missing_fields, and proof_boundary for audit or handoff.","The result will feed a paid or irreversible next action such as outreach, CRM writeback, workflow execution, or another paid API call."],"what_payment_buys":["Decision-ready lead or company brief from caller-supplied public facts.","Source summary, missing-field flags, next agent actions, qualification questions, and proof boundary.","Boundary Receipt evidence tied to the request, response, policy decision, and post-settlement handoff."],"after_payment_check":["Read receipt, human_summary, missing_fields, and proof_boundary before any outreach or CRM writeback.","Persist endpoint, amount, network, tx hash when available, receipt, and payer label.","Classify as non-seed revenue only when payer evidence is not an internal seed wallet."]},"x402_buyer_safety_patterns":{"market_signal":"Recent x402 builders are asking less about whether payment can settle and more about payload safety, spend control, receipts, and proof after settlement.","use_this_when":["A buyer already has an x402 client, wallet adapter, or payment challenge flow and needs guardrails around it.","A post or integration mentions spending caps, policy, receipts, audit trails, metadata leaks, PII, or proof after payment.","The agent needs to decide whether a paid API result is safe to trust or hand off to another tool."],"patterns":[{"pattern":"Sanitize before payment","market_language":["before the paywall","pre-settlement metadata","PII in payload","clear the junk before payment"],"call_first":"/pii-redact","follow_with":["/risk-scan","/workflow-audit"],"why":"Use before attaching payment evidence or sending a payload that may contain email, API key, wallet, phone, IP, or private context.","preview_url":"https://boundary-guard.vercel.app/pii-redact"},{"pattern":"Check budget and route before spend","market_language":["spending cap","budget","policy engine","control layer","agent finance gateway"],"call_first":"/runtime-route-preflight","follow_with":["/workflow-audit"],"why":"Use before model, search, API, or tool spend when the agent needs a recommended route, budget summary, and risk decision.","preview_url":"https://boundary-guard.vercel.app/runtime-route-preflight"},{"pattern":"Audit a chained paid workflow","market_language":["discover route use pay prove","audit trail","pre-action checks","agent workflow safety"],"call_first":"/workflow-audit","follow_with":["/receipt-verify"],"why":"Use when multiple paid/tool steps are chained and the buyer needs missing receipts, policy gaps, or handoff risks surfaced before execution.","preview_url":"https://boundary-guard.vercel.app/workflow-audit"},{"pattern":"Verify after settlement","market_language":["receipts","proofs","evidence","after the charge","buyer intent after payment"],"call_first":"/receipt-verify","follow_with":["/agent-handoff"],"why":"Use after payment or tool execution when the buyer needs to verify receipt fields and decide whether to trust the result.","preview_url":"https://boundary-guard.vercel.app/receipt-verify"}],"reply_boundary":"Useful for x402 safety/control/receipt discussions only; do not imply customer traction, revenue, adoption, ranking, endorsement, or solved Agentic metadata."},"primary_agent_discovery_pack":{"canonical_intent":"Create a proof-safe sales or research brief from caller-supplied public lead facts. Call after you have public lead hints and the next step is a usable brief plus receipt evidence; use the receipt + proof_boundary + missing_fields + guardrails after x402 settlement clears before any agent acts on the lead.","buyer_control_plane":{"thesis":"Payment execution is the rail; proof and control are the buyer-side control plane.","use_when":"The agent can already pay an x402 or MCP-style tool, but the buyer still needs to know what should be checked before spend, what came back after payment, and what evidence can be trusted before the next action.","route_sequence":[{"stage":"before_spend","endpoint":"/runtime-route-preflight","price":"$0.02","buyer_question":"Is this model, API, or paid route allowed and inside budget before the agent spends?"},{"stage":"before_payload_or_logging","endpoint":"/pii-redact","price":"$0.01","buyer_question":"Does this request, response, or log contain PII or secret-like values before payment evidence is attached?"},{"stage":"after_public_lead_context","endpoint":"/lead-brief-lite","price":"$0.03","buyer_question":"Can the agent turn public/caller-supplied facts into a usable brief with missing-field flags and receipt evidence?"},{"stage":"after_settlement","endpoint":"/receipt-verify","price":"$0.03","buyer_question":"Can the buyer verify the receipt package before trusting or reporting the paid result?"},{"stage":"before_chained_action","endpoint":"/workflow-audit","price":"$0.03","buyer_question":"Can the workflow prove receipts, policy checks, and handoff boundaries before the next paid or irreversible step?"}],"lead_brief_role":"Lead Brief Lite is the paid artifact layer for public lead context: preview free, pay $0.03 when the next agent needs a decision-ready brief plus source summary, missing fields, proof boundary, and receipt evidence.","proof_boundary":"Internal seed/indexing proof is not customer traction; count revenue only from non-seed buyer evidence."},"route_when":["The agent has a company/person name, URL, email, location, or short public lead note.","The agent already holds caller-supplied or public facts (name, URL, email, location, short note) and the next useful output is an outreach-ready or research-ready brief.","The buyer needs one $0.03 paid call that returns decision-ready brief + source pack + explicit missing fields + proof boundary + Boundary Receipt instead of raw fields that still require interpretation.","The workflow has gathered public lead context and now requires the post-payment trust layer: inspect receipt, proof_boundary, and missing_fields before the next agent does outreach, CRM write, or further paid work.","You want auditable evidence of exactly what public facts were known at payment time and what the guardrails explicitly left unknown."],"post_payment_trust_use_cases":["After x402 settlement clears on the paid host, the calling agent MUST read the receipt, human_summary, proof_boundary, and missing_fields before acting on the brief. This is the guardrail that prevents hallucinated private data or over-trust in the output.","Chain the brief + receipt into downstream steps (outreach, AgentMail prep, workflow-audit, CRM) only after confirming the proof boundary matches the no-secret policy.","Record the receipt_id and hashes for later /receipt-verify or /workflow-audit calls so multi-step agent runs carry forward evidence of what was paid for and what was intentionally not enriched.","Before logging revenue or buyer traction, classify the call as seed/internal or non-seed customer usage.","Classify the call (seed vs non-seed) using the receipt before any revenue or adoption claim."],"do_not_route_when":["The buyer expects Apollo, Exa, Firecrawl, Serper, private CRM, inbox, or paid upstream lookup that was not supplied in the request.","The input is only messy raw fields and the next step is normalization rather than a brief; use /data-enrich-lite first.","The agent is about to spend on models, search, or other paid APIs before deciding the route; use /runtime-route-preflight first."],"buyer_intent_queries":["x402 lead brief API","sales research brief API","outreach prep API","proof-safe lead enrichment","company brief for sales agent","source-linked lead research","lead enrichment with receipt","no-secret sales intelligence","research brief with missing fields","pay per request lead brief","x402 post payment trust","x402 lead brief after payment","post payment trust guardrail","receipt evidence before outreach","agent paid data proof boundary","lead brief + missing fields + receipt"],"agent_prompt_examples":["I have a public company URL, contact email, and location. Create a source-linked sales brief with receipt for $0.03, then use the proof_boundary and missing_fields as guardrails before any outreach.","Turn these caller-supplied lead notes into useful facts, missing fields, next agent actions, proof boundaries, and receipt hashes. After payment clears, the next step must respect the guardrails.","Preview whether this lead has enough public context for outreach, then pay only if the brief is usable and the receipt will let me prove what was known.","I just settled x402 for lead context. Package it as a proof-safe brief with explicit proof_boundary and missing fields so the downstream agent does not hallucinate private data."],"expected_after_call":["brief.headline","brief.buyer_fit_signal","brief.useful_facts","brief.source_summary","brief.next_agent_actions","brief.qualification_questions","brief.missing_fields","brief.proof_boundary","source_pack","receipt","human_summary"],"competitor_positioning":"Use this when the buyer wants a usable brief from public/caller-supplied facts. Use StableEnrich-style raw enrichment when the buyer primarily wants broad upstream field access.","measurement_hint":"Count only non-seed paid calls, unique buyers, x402scan rows, or qualified inbound demand as revenue traction."},"routing_rules":[{"rank":1,"buyer_job":"Create an outreach-ready lead or company brief from public facts.","call":"/lead-brief-lite","why_this_first":"Best current revenue path: agents can preview without payment, then pay $0.03 for a decision-ready brief and receipt evidence.","price":"$0.03","preview_url":"https://boundary-guard.vercel.app/lead-brief-lite","paid_url":"https://boundary-guard-x402.onrender.com/lead-brief-lite","buyer_queries":["x402 lead brief API","sales research brief API","outreach prep API","proof-safe lead enrichment","company brief for sales agent","source-linked lead research","lead enrichment with receipt","no-secret sales intelligence","research brief with missing fields","pay per request lead brief","x402 post payment trust","x402 lead brief after payment","post payment trust guardrail","receipt evidence before outreach","agent paid data proof boundary","lead brief + missing fields + receipt","lead brief","sales research","outreach prep","source pack","no-secret enrichment","proof-safe lead enrichment","lead enrichment with receipt","company brief for sales agent","research brief with missing fields","x402 lead enrichment API"],"expected_response_fields":["brief.headline","brief.buyer_fit_signal","brief.useful_facts","brief.source_summary","brief.next_agent_actions","brief.qualification_questions","brief.missing_fields","brief.proof_boundary","source_pack","receipt","human_summary","decision","brief.headline","brief.fit_summary","brief.buyer_fit_signal","brief.useful_facts","brief.source_summary","brief.next_agent_actions","brief.qualification_questions","brief.missing_fields","brief.proof_boundary","source_pack","receipt.receipt_id","receipt.input_sha256","receipt.output_sha256","human_summary"],"agent_discovery_pack":{"canonical_intent":"Create a proof-safe sales or research brief from caller-supplied public lead facts. Call after you have public lead hints and the next step is a usable brief plus receipt evidence; use the receipt + proof_boundary + missing_fields + guardrails after x402 settlement clears before any agent acts on the lead.","buyer_control_plane":{"thesis":"Payment execution is the rail; proof and control are the buyer-side control plane.","use_when":"The agent can already pay an x402 or MCP-style tool, but the buyer still needs to know what should be checked before spend, what came back after payment, and what evidence can be trusted before the next action.","route_sequence":[{"stage":"before_spend","endpoint":"/runtime-route-preflight","price":"$0.02","buyer_question":"Is this model, API, or paid route allowed and inside budget before the agent spends?"},{"stage":"before_payload_or_logging","endpoint":"/pii-redact","price":"$0.01","buyer_question":"Does this request, response, or log contain PII or secret-like values before payment evidence is attached?"},{"stage":"after_public_lead_context","endpoint":"/lead-brief-lite","price":"$0.03","buyer_question":"Can the agent turn public/caller-supplied facts into a usable brief with missing-field flags and receipt evidence?"},{"stage":"after_settlement","endpoint":"/receipt-verify","price":"$0.03","buyer_question":"Can the buyer verify the receipt package before trusting or reporting the paid result?"},{"stage":"before_chained_action","endpoint":"/workflow-audit","price":"$0.03","buyer_question":"Can the workflow prove receipts, policy checks, and handoff boundaries before the next paid or irreversible step?"}],"lead_brief_role":"Lead Brief Lite is the paid artifact layer for public lead context: preview free, pay $0.03 when the next agent needs a decision-ready brief plus source summary, missing fields, proof boundary, and receipt evidence.","proof_boundary":"Internal seed/indexing proof is not customer traction; count revenue only from non-seed buyer evidence."},"route_when":["The agent has a company/person name, URL, email, location, or short public lead note.","The agent already holds caller-supplied or public facts (name, URL, email, location, short note) and the next useful output is an outreach-ready or research-ready brief.","The buyer needs one $0.03 paid call that returns decision-ready brief + source pack + explicit missing fields + proof boundary + Boundary Receipt instead of raw fields that still require interpretation.","The workflow has gathered public lead context and now requires the post-payment trust layer: inspect receipt, proof_boundary, and missing_fields before the next agent does outreach, CRM write, or further paid work.","You want auditable evidence of exactly what public facts were known at payment time and what the guardrails explicitly left unknown."],"post_payment_trust_use_cases":["After x402 settlement clears on the paid host, the calling agent MUST read the receipt, human_summary, proof_boundary, and missing_fields before acting on the brief. This is the guardrail that prevents hallucinated private data or over-trust in the output.","Chain the brief + receipt into downstream steps (outreach, AgentMail prep, workflow-audit, CRM) only after confirming the proof boundary matches the no-secret policy.","Record the receipt_id and hashes for later /receipt-verify or /workflow-audit calls so multi-step agent runs carry forward evidence of what was paid for and what was intentionally not enriched.","Before logging revenue or buyer traction, classify the call as seed/internal or non-seed customer usage.","Classify the call (seed vs non-seed) using the receipt before any revenue or adoption claim."],"do_not_route_when":["The buyer expects Apollo, Exa, Firecrawl, Serper, private CRM, inbox, or paid upstream lookup that was not supplied in the request.","The input is only messy raw fields and the next step is normalization rather than a brief; use /data-enrich-lite first.","The agent is about to spend on models, search, or other paid APIs before deciding the route; use /runtime-route-preflight first."],"buyer_intent_queries":["x402 lead brief API","sales research brief API","outreach prep API","proof-safe lead enrichment","company brief for sales agent","source-linked lead research","lead enrichment with receipt","no-secret sales intelligence","research brief with missing fields","pay per request lead brief","x402 post payment trust","x402 lead brief after payment","post payment trust guardrail","receipt evidence before outreach","agent paid data proof boundary","lead brief + missing fields + receipt"],"agent_prompt_examples":["I have a public company URL, contact email, and location. Create a source-linked sales brief with receipt for $0.03, then use the proof_boundary and missing_fields as guardrails before any outreach.","Turn these caller-supplied lead notes into useful facts, missing fields, next agent actions, proof boundaries, and receipt hashes. After payment clears, the next step must respect the guardrails.","Preview whether this lead has enough public context for outreach, then pay only if the brief is usable and the receipt will let me prove what was known.","I just settled x402 for lead context. Package it as a proof-safe brief with explicit proof_boundary and missing fields so the downstream agent does not hallucinate private data."],"expected_after_call":["brief.headline","brief.buyer_fit_signal","brief.useful_facts","brief.source_summary","brief.next_agent_actions","brief.qualification_questions","brief.missing_fields","brief.proof_boundary","source_pack","receipt","human_summary"],"competitor_positioning":"Use this when the buyer wants a usable brief from public/caller-supplied facts. Use StableEnrich-style raw enrichment when the buyer primarily wants broad upstream field access.","measurement_hint":"Count only non-seed paid calls, unique buyers, x402scan rows, or qualified inbound demand as revenue traction."}},{"rank":2,"buyer_job":"Normalize caller-supplied public company, person, URL, domain, or lead hints.","call":"/data-enrich-lite","why_this_first":"Use when the agent needs structured public fields before composing a brief, writing to CRM, or routing another paid step.","price":"$0.02","preview_url":"https://boundary-guard.vercel.app/data-enrich-lite","paid_url":"https://boundary-guard-x402.onrender.com/data-enrich-lite","buyer_queries":["data enrichment","lead enrichment","source pack","no-secret enrichment","normalize public fields"],"expected_response_fields":["decision","normalized_fields","missing_fields","source_pack","receipt","human_summary"]},{"rank":3,"buyer_job":"Choose an AI runtime, model, search, or API route before spending.","call":"/runtime-route-preflight","why_this_first":"Use before high-volume inference/API spend because current x402 demand is strongest around model/runtime access.","price":"$0.02","preview_url":"https://boundary-guard.vercel.app/runtime-route-preflight","paid_url":"https://boundary-guard-x402.onrender.com/runtime-route-preflight","buyer_queries":["model routing","runtime preflight","budget guard","agent spend check","x402 runtime"],"expected_response_fields":["decision","recommended_route","budget_summary","risk","findings","receipt","human_summary"]},{"rank":4,"buyer_job":"Audit a multi-step agent workflow before it runs paid tools, writes, sends, or hands off.","call":"/workflow-audit","why_this_first":"Use when one wrong step could create spend, policy, or trust risk across a chained agent workflow.","price":"$0.03","preview_url":"https://boundary-guard.vercel.app/workflow-audit","paid_url":"https://boundary-guard-x402.onrender.com/workflow-audit","buyer_queries":["workflow audit","agent workflow safety","paid tool audit","multi-agent receipt","pre-action check"],"expected_response_fields":["decision","findings","recommended_action","workflow_receipt","receipt","human_summary"]},{"rank":5,"buyer_job":"Verify receipt or payment evidence before trusting a paid API result.","call":"/receipt-verify","why_this_first":"Use when the buyer already has a result and needs to decide whether settlement and receipt evidence are trustworthy.","price":"$0.03","preview_url":"https://boundary-guard.vercel.app/receipt-verify","paid_url":"https://boundary-guard-x402.onrender.com/receipt-verify","buyer_queries":["receipt verification","payment evidence","x402 settlement proof","agent payment trust"],"expected_response_fields":["decision","findings","verified_fields","recommended_action","receipt","human_summary"]}],"do_not_route_when":["The caller expects private CRM, Apollo, Exa, Firecrawl, Serper, or web-browsed enrichment that was not supplied in the request.","The buyer needs guaranteed customer revenue, adoption, marketplace ranking, or third-party endorsement proof.","The agent cannot make x402 payments and does not need the free preview path."],"proof_boundary":"Boundary Guard is live and internally seeded on Base-mainnet x402. This router does not claim customer revenue, customer adoption, marketplace ranking, or third-party endorsement.","measurement":["non-seed paid transactions","unique non-seed buyers","x402scan rows for Boundary Guard","Agentic l30d call movement","qualified inbound demand from public replies or direct buyers"],"links":{"html_quickstart":"https://boundary-guard.vercel.app/buyer-quickstart","json_quickstart":"https://boundary-guard-x402.onrender.com/buyer-quickstart.json","buyer_conversion_guide":"https://boundary-guard-x402.onrender.com/buyer-conversion-guide","buyer_conversion_guide_json":"https://boundary-guard-x402.onrender.com/buyer-conversion-guide.json","market_health_json":"https://boundary-guard-x402.onrender.com/market-health.json","x402_inventory":"https://boundary-guard-x402.onrender.com/.well-known/x402","openapi":"https://boundary-guard-x402.onrender.com/openapi.json","llms_txt":"https://boundary-guard-x402.onrender.com/llms.txt","trust":"https://boundary-guard-x402.onrender.com/trust","trust_json":"https://boundary-guard-x402.onrender.com/trust.json","ops_status":"https://boundary-guard-x402.onrender.com/ops-status","ops_status_json":"https://boundary-guard-x402.onrender.com/ops-status.json","agentic_reingest_request":"https://boundary-guard-x402.onrender.com/agentic-reingest-request.json","agentic_market":"https://agentic.market/?service=boundary-guard-x402-onrender-com"},"quickstart":{"name":"Boundary Guard Buyer Quickstart","headline":"Preview free. Pay only when receipt evidence matters.","mode":"low-friction public buyer activation","target_buyer":["x402 builders evaluating paid agent tools","agent workflow builders who need a pre-action receipt or proof-safe brief","sales, research, CRM, and outreach agents comparing raw enrichment with buyer-ready outputs"],"buyer_control_plane":{"thesis":"Payment execution is the rail; proof and control are the buyer-side control plane.","use_when":"The agent can already pay an x402 or MCP-style tool, but the buyer still needs to know what should be checked before spend, what came back after payment, and what evidence can be trusted before the next action.","route_sequence":[{"stage":"before_spend","endpoint":"/runtime-route-preflight","price":"$0.02","buyer_question":"Is this model, API, or paid route allowed and inside budget before the agent spends?"},{"stage":"before_payload_or_logging","endpoint":"/pii-redact","price":"$0.01","buyer_question":"Does this request, response, or log contain PII or secret-like values before payment evidence is attached?"},{"stage":"after_public_lead_context","endpoint":"/lead-brief-lite","price":"$0.03","buyer_question":"Can the agent turn public/caller-supplied facts into a usable brief with missing-field flags and receipt evidence?"},{"stage":"after_settlement","endpoint":"/receipt-verify","price":"$0.03","buyer_question":"Can the buyer verify the receipt package before trusting or reporting the paid result?"},{"stage":"before_chained_action","endpoint":"/workflow-audit","price":"$0.03","buyer_question":"Can the workflow prove receipts, policy checks, and handoff boundaries before the next paid or irreversible step?"}],"lead_brief_role":"Lead Brief Lite is the paid artifact layer for public lead context: preview free, pay $0.03 when the next agent needs a decision-ready brief plus source summary, missing fields, proof boundary, and receipt evidence.","proof_boundary":"Internal seed/indexing proof is not customer traction; count revenue only from non-seed buyer evidence."},"primary_try_path":{"label":"Preview Lead Brief Lite without payment","why":"Best first public link from X replies because it lets a builder inspect the exact response shape, see the proof boundary, and decide whether a buyer-ready brief is the next useful step before wiring a wallet-capable x402 client.","method":"POST","url":"https://boundary-guard.vercel.app/lead-brief-lite","copy_paste_curl":"curl -X POST https://boundary-guard.vercel.app/lead-brief-lite -H 'content-type: application/json' --data '{\"entity_type\":\"company\",\"query\":\"Acme Robotics sales lead: https://example.com/about, sales@example.com, Raleigh, makes warehouse automation software.\",\"known_fields\":{\"name\":\"Acme Robotics\",\"location\":\"Raleigh, NC\"},\"brief_goal\":\"sales\",\"policy\":{\"no_secret_mode\":true,\"require_source_pack\":true,\"max_bullets\":5}}'","expected_in_response":["decision","brief.headline","brief.buyer_fit_signal","brief.useful_facts","brief.source_summary","brief.next_agent_actions","brief.qualification_questions","brief.proof_boundary","receipt","human_summary"]},"paid_x402_path":{"label":"Pay for the same call when settlement and receipt evidence matter","method":"POST","url":"https://boundary-guard-x402.onrender.com/lead-brief-lite","price":"$0.03","network":"eip155:8453","currency":"USDC","flow":["Send the same POST request to the paid Render host.","Read the standard x402 payment challenge returned by the host.","Settle the Base-mainnet USDC payment with a wallet-capable x402 client.","Retry the request with the x402 payment header and keep the Boundary Receipt."],"do_not_count_as_revenue_until":"The call is non-seed buyer usage verified through x402scan, wallet/accounting evidence, repeat buyer signal, or qualified inbound demand."},"agent_cli_onboarding":{"label":"AgentCash, MCP, or CLI wallet onboarding facts","why":"The strongest early x402 revenue examples make the first paid call easy for agents and CLI users: inspect the free preview, then route one cheap paid call through a wallet-capable x402 client.","recommended_first_endpoint":"/lead-brief-lite","preview_first":{"method":"POST","url":"https://boundary-guard.vercel.app/lead-brief-lite","purpose":"Inspect response shape, proof boundary, missing fields, and human_summary before any payment."},"paid_try":{"method":"POST","url":"https://boundary-guard-x402.onrender.com/lead-brief-lite","price":"$0.03","network":"eip155:8453","currency":"USDC","pay_when":"The preview is useful and the downstream agent needs settlement plus Boundary Receipt evidence."},"router_prompt":"Try Boundary Guard Lead Brief Lite when you have public lead facts and need an outreach-ready brief. Preview on Vercel first; pay $0.03 USDC on Base only if the next agent needs receipt-backed proof.","store_after_paid_call":["endpoint","price","network","payer label","tx hash or x402 payment reference when available","receipt.receipt_id","receipt.input_sha256","receipt.output_sha256","human_summary","proof_boundary","missing_fields"],"do_not_claim":["customer revenue until payer evidence is non-seed","private enrichment sources that were not supplied in the request","marketplace ranking or partner endorsement"]},"agent_purchase_decision":{"decision_label":"Preview first; pay only when the next agent needs receipt-backed action evidence.","call_lead_brief_lite_when":["The buyer has public lead, company, contact, URL, or source facts and needs an outreach-ready brief.","The next workflow step is outreach, CRM prep, research handoff, AgentMail-style communication, or workflow audit.","A cheap x402-paid proof point is useful before spending on deeper enrichment, model routing, or human review."],"preview_is_enough_when":["The buyer is only comparing response shape, expected fields, proof boundary, or sample usefulness.","The payload is still missing enough public facts that the brief would not guide a next action.","The caller cannot make x402 payments and does not need settlement evidence."],"pay_when":["The previewed response is useful enough to act on and the buyer wants Base-mainnet x402 settlement evidence.","The buyer needs a Boundary Receipt, human_summary, missing_fields, and proof_boundary for audit or handoff.","The result will feed a paid or irreversible next action such as outreach, CRM writeback, workflow execution, or another paid API call."],"what_payment_buys":["Decision-ready lead or company brief from caller-supplied public facts.","Source summary, missing-field flags, next agent actions, qualification questions, and proof boundary.","Boundary Receipt evidence tied to the request, response, policy decision, and post-settlement handoff."],"after_payment_check":["Read receipt, human_summary, missing_fields, and proof_boundary before any outreach or CRM writeback.","Persist endpoint, amount, network, tx hash when available, receipt, and payer label.","Classify as non-seed revenue only when payer evidence is not an internal seed wallet."]},"x402_buyer_safety_patterns":{"market_signal":"Recent x402 builders are asking less about whether payment can settle and more about payload safety, spend control, receipts, and proof after settlement.","use_this_when":["A buyer already has an x402 client, wallet adapter, or payment challenge flow and needs guardrails around it.","A post or integration mentions spending caps, policy, receipts, audit trails, metadata leaks, PII, or proof after payment.","The agent needs to decide whether a paid API result is safe to trust or hand off to another tool."],"patterns":[{"pattern":"Sanitize before payment","market_language":["before the paywall","pre-settlement metadata","PII in payload","clear the junk before payment"],"call_first":"/pii-redact","follow_with":["/risk-scan","/workflow-audit"],"why":"Use before attaching payment evidence or sending a payload that may contain email, API key, wallet, phone, IP, or private context.","preview_url":"https://boundary-guard.vercel.app/pii-redact"},{"pattern":"Check budget and route before spend","market_language":["spending cap","budget","policy engine","control layer","agent finance gateway"],"call_first":"/runtime-route-preflight","follow_with":["/workflow-audit"],"why":"Use before model, search, API, or tool spend when the agent needs a recommended route, budget summary, and risk decision.","preview_url":"https://boundary-guard.vercel.app/runtime-route-preflight"},{"pattern":"Audit a chained paid workflow","market_language":["discover route use pay prove","audit trail","pre-action checks","agent workflow safety"],"call_first":"/workflow-audit","follow_with":["/receipt-verify"],"why":"Use when multiple paid/tool steps are chained and the buyer needs missing receipts, policy gaps, or handoff risks surfaced before execution.","preview_url":"https://boundary-guard.vercel.app/workflow-audit"},{"pattern":"Verify after settlement","market_language":["receipts","proofs","evidence","after the charge","buyer intent after payment"],"call_first":"/receipt-verify","follow_with":["/agent-handoff"],"why":"Use after payment or tool execution when the buyer needs to verify receipt fields and decide whether to trust the result.","preview_url":"https://boundary-guard.vercel.app/receipt-verify"}],"reply_boundary":"Useful for x402 safety/control/receipt discussions only; do not imply customer traction, revenue, adoption, ranking, endorsement, or solved Agentic metadata."},"wallet_integration_handoff":{"label":"Implementation handoff for wallet-capable agents","use_when":"Give this packet to a coding or payment agent after the free preview proves the payload is useful and the buyer wants x402 settlement plus Boundary Receipt evidence.","adapter_contract":["POST the preview payload to the paid URL and capture the standard x402 challenge.","Ask the buyer-approved x402 wallet adapter to settle the challenge on eip155:8453 in USDC.","Retry the same POST with the payment header returned by the wallet adapter.","Persist response.receipt, response.human_summary, endpoint, amount, network, payer label, and tx hash when available.","Classify the usage as revenue only when the payer is not an internal seed wallet."],"node_adapter_pseudocode":"const payload = previewPayload;\nconst challenge = await x402Client.requestChallenge({\n  method: \"POST\",\n  url: \"https://boundary-guard-x402.onrender.com/lead-brief-lite\",\n  json: payload\n});\nconst paymentHeader = await x402Client.settle({\n  challenge,\n  wallet,\n  network: \"eip155:8453\",\n  currency: \"USDC\",\n  maxAmount: \"0.03\"\n});\nconst result = await x402Client.postJson({\n  url: \"https://boundary-guard-x402.onrender.com/lead-brief-lite\",\n  json: payload,\n  paymentHeader\n});\nawait saveReceiptEvidence({\n  endpoint: \"/lead-brief-lite\",\n  receipt: result.receipt,\n  humanSummary: result.human_summary,\n  revenueClass: payer.isInternalSeed ? \"seed-proof\" : \"non-seed-buyer\"\n});","validation_checklist":["Free preview returns the expected brief fields before any wallet action.","Paid host returns an x402 challenge before settlement.","Wallet adapter is buyer-approved and never exposes private key material to Boundary Guard.","Retried paid response includes receipt and human_summary fields.","Revenue dashboard separates seed-proof calls from non-seed buyer calls."]},"why_pay_after_preview":["You get a decision-ready brief, not another raw field bundle to interpret later.","The response includes source summary, missing-field flags, and proof boundary guidance before the next agent acts.","The paid call keeps Boundary Receipt evidence so the buyer can prove what was checked after settlement.","Replay the same payload on Render only after the preview proves the brief is useful and the buyer needs x402 settlement evidence."],"why_not_raw_enrichment":["Choose /lead-brief-lite when the buyer wants an outreach-ready or research-ready brief from public or caller-supplied facts.","Choose /data-enrich-lite when the buyer still needs normalized fields, URL cleanup, or source extraction before another tool decides what to do.","Do not imply private CRM, Apollo, Exa, Firecrawl, Serper, inbox, or other upstream paid/private data access that Boundary Guard did not use."],"choose_endpoint_fast":[{"buyer_job":"I have public lead facts and need a brief for outreach or research.","call":"/lead-brief-lite","price":"$0.03","first_link":"https://boundary-guard.vercel.app/lead-brief-lite"},{"buyer_job":"I have messy public fields, URLs, emails, domains, or source snippets to normalize.","call":"/data-enrich-lite","price":"$0.02","first_link":"https://boundary-guard.vercel.app/data-enrich-lite"},{"buyer_job":"My agent is about to spend on a model/API route and needs a budget/policy check.","call":"/runtime-route-preflight","price":"$0.02","first_link":"https://boundary-guard.vercel.app/runtime-route-preflight"},{"buyer_job":"My workflow has multiple paid/tool steps and needs pre-run audit evidence.","call":"/workflow-audit","price":"$0.03","first_link":"https://boundary-guard.vercel.app/workflow-audit"},{"buyer_job":"I need to verify Boundary Guard receipt or payment evidence before trusting a result.","call":"/receipt-verify","price":"$0.03","first_link":"https://boundary-guard.vercel.app/receipt-verify"}],"public_reply_guidance":{"safe_link_for_x_replies":"https://boundary-guard.vercel.app/buyer-quickstart","use_when":["The post is already about x402 trust, receipts, agent payment safety, pre-action checks, prompt-injection risk, or paid API routing.","The author is building, asking, comparing, or inviting concrete resources."],"hold_when":["The post is generic hype or unrelated market commentary.","The reply would imply customer traction, revenue, adoption, endorsement, or a solved Agentic metadata blocker.","The author is announcing a directly competing launch and did not invite comparisons or tools."],"proof_safe_claim":"Live x402-paid endpoints with internal seed/payment proof and a free preview path; no customer revenue or adoption claim.","reply_templates":[{"label":"Lead brief preview reply","use_when":"The post asks how an agent should preview a useful paid endpoint before wiring x402 settlement.","reply":"Preview the exact brief first at https://boundary-guard.vercel.app/buyer-quickstart, then pay only when the next agent needs settlement plus receipt-backed action evidence. Proof boundary: live preview + internal seed/indexing proof only, not customer traction."},{"label":"PII and receipt safety reply","use_when":"The post is about payload safety, receipts, logs, or PII before payment, storage, or sharing.","reply":"If the risk is PII or receipt-bearing payloads, start with https://boundary-guard.vercel.app/pii-redact before payment, storage, or public sharing. Same proof boundary: live preview + internal seed/indexing proof only."}]},"links":{"html":"/buyer-quickstart","json":"/buyer-quickstart.json","html_absolute":"https://boundary-guard-x402.onrender.com/buyer-quickstart","json_absolute":"https://boundary-guard-x402.onrender.com/buyer-quickstart.json","main_preview_absolute":"https://boundary-guard.vercel.app/buyer-quickstart","buyer_conversion_guide":"/buyer-conversion-guide","buyer_conversion_guide_json":"/buyer-conversion-guide.json","paid_catalog":"https://boundary-guard-x402.onrender.com/.well-known/x402"}}}