Low-friction public trial path

Preview free. Pay only when receipt evidence matters.

Use this page as the first link from public replies. It shows exactly how to preview the strongest current endpoint without payment, then how to move to the paid x402 host when settlement and receipt evidence matter.

Preview Lead Brief Lite Paid x402 endpoint Use JSON quickstart
Step 1

Preview the exact response.

Call the Vercel endpoint first. No wallet, account, or subscription is needed to inspect the response shape.

Step 2

Pay $0.03 only if useful.

Replay the same payload on Render when the brief is worth keeping and the buyer needs x402 settlement evidence.

Step 3

Check the receipt before acting.

Use receipt, human_summary, missing_fields, and proof_boundary before outreach, CRM writeback, or another paid call.

Who should use it

Target buyers

  • 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

Proof-safe claim

Live x402-paid endpoints with internal seed/payment proof and a free preview path; no customer revenue or adoption claim.

Step 1: preview without payment

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.

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}}'

What comes back

  • 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

Agent purchase decision

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.

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

Recent x402 builders are asking less about whether payment can settle and more about payload safety, spend control, receipts, and proof after settlement.

Sanitize before payment

Use before attaching payment evidence or sending a payload that may contain email, API key, wallet, phone, IP, or private context.

Call first: /pii-redact

Market language: before the paywall, pre-settlement metadata, PII in payload, clear the junk before payment

Preview pattern

Check budget and route before spend

Use before model, search, API, or tool spend when the agent needs a recommended route, budget summary, and risk decision.

Call first: /runtime-route-preflight

Market language: spending cap, budget, policy engine, control layer, agent finance gateway

Preview pattern

Audit a chained paid workflow

Use when multiple paid/tool steps are chained and the buyer needs missing receipts, policy gaps, or handoff risks surfaced before execution.

Call first: /workflow-audit

Market language: discover route use pay prove, audit trail, pre-action checks, agent workflow safety

Preview pattern

Verify after settlement

Use after payment or tool execution when the buyer needs to verify receipt fields and decide whether to trust the result.

Call first: /receipt-verify

Market language: receipts, proofs, evidence, after the charge, buyer intent after payment

Preview pattern

Agent wallet / CLI first call

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.

/lead-brief-lite $0.03

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.

Preview: https://boundary-guard.vercel.app/lead-brief-lite

Paid: https://boundary-guard-x402.onrender.com/lead-brief-lite

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

Step 2: pay with x402 when ready

https://boundary-guard-x402.onrender.com/lead-brief-lite $0.03

Network: eip155:8453. Currency: USDC.

Payment 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.

Wallet integration handoff

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.

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.
const payload = previewPayload;
const challenge = await x402Client.requestChallenge({
  method: "POST",
  url: "https://boundary-guard-x402.onrender.com/lead-brief-lite",
  json: payload
});
const paymentHeader = await x402Client.settle({
  challenge,
  wallet,
  network: "eip155:8453",
  currency: "USDC",
  maxAmount: "0.03"
});
const result = await x402Client.postJson({
  url: "https://boundary-guard-x402.onrender.com/lead-brief-lite",
  json: payload,
  paymentHeader
});
await saveReceiptEvidence({
  endpoint: "/lead-brief-lite",
  receipt: result.receipt,
  humanSummary: result.human_summary,
  revenueClass: payer.isInternalSeed ? "seed-proof" : "non-seed-buyer"
});

Why pay after preview

What payment buys

  • 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.

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 the endpoint fast

/lead-brief-lite $0.03

I have public lead facts and need a brief for outreach or research.

Preview endpoint

/data-enrich-lite $0.02

I have messy public fields, URLs, emails, domains, or source snippets to normalize.

Preview endpoint

/runtime-route-preflight $0.02

My agent is about to spend on a model/API route and needs a budget/policy check.

Preview endpoint

/workflow-audit $0.03

My workflow has multiple paid/tool steps and needs pre-run audit evidence.

Preview endpoint

/receipt-verify $0.03

I need to verify Boundary Guard receipt or payment evidence before trusting a result.

Preview endpoint

Public reply guardrails

Use this link 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 reply examples

Lead brief preview reply

Use when: The post asks how an agent should preview a useful paid endpoint before wiring x402 settlement.

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.

PII and receipt safety reply

Use when: The post is about payload safety, receipts, logs, or PII before payment, storage, or sharing.

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.

Do not count internal seed payments as revenue. Use non-seed buyer evidence before claiming traction.