Instant x402 Testbench
Pick. Probe. Pay. Retry.
A public route chooser and copy-paste test surface for buyer agents that want the fastest safe path from expected unpaid HTTP 402 to paid HTTP 200.
Base mainnet accepted No auto-spend Kite Passport ready Stripe Link watched Agent Inbox inbound-only Public metrics aggregate-only/api/opportunity-check
Company Intel or Vendor Risk when one decision is clear.
Deep Diligence only for serious proof gaps.
The challenge is the checkout handoff, not a service failure.
Fastest Paid Test Path
Use the route ladder without guessing.
Pick the cheapest useful route for the decision.
Copy the sample JSON payload and send the route unpaid first.
Expect HTTP 402. That is the normal x402 challenge, not a broken service.
Pay the listed route price with your own x402 client on Base mainnet.
Retry the same POST and expect HTTP 200 with structured JSON.
Escalate only when the paid result shows a real proof gap.
Manual payment rules
Pay only when the next decision is clear.
- No subscription: pay once, get JSON once.
- Unpaid protected routes return HTTP 402 with the route price and x402 payment requirements.
- Inspect the schema and sample payload before deciding whether to pay.
- Buyer agents should start with /api/opportunity-check at $0.01. Use /api/agent-revenue-audit at $5 only when the agent/operator specifically wants monetization guidance.
- Start cheap with /api/opportunity-check unless you already know you need the $5 /api/agent-revenue-audit route.
- Do not buy high-value routes for vague or high-stakes decisions without outside verification and a specific decision to make.
Buyer-agent challenge
Authorized buyer agents should start with the $0.01 route.
Buyer agents should start with /api/opportunity-check at $0.01. Use /api/agent-revenue-audit at $5 only when the agent/operator specifically wants monetization guidance.
Open /buyer-agent-challenge · Read /api/buyer-agent-challenge
{
"subject": "External buyer-agent x402 test",
"goal": "Confirm this buyer agent can complete one x402 paid call and receive JSON.",
"buyerType": "buyer-agent",
"source": "external-buyer-agent-test-001"
}HubSpot-oriented agent builders
Readiness-only external x402 lane.
HubSpot-oriented builders can evaluate ApexScout as an external x402 trust and monetization API. This release does not connect to HubSpot CRM or use HubSpot OAuth.
Open /hubspot-agent-readiness · Read /api/hubspot-agent-readiness
Route Chooser
Choose the paid route that matches the proof gap.
Copy Payload
Opportunity Check
Use this when you are unsure whether a target or claim deserves more paid work.
Expected Flow
/api/opportunity-check
Do not use this when: Do not use this when you already know the blocker and need a company snapshot, vendor review, claim check, lead brief, or premium diligence map.
curl -i -X POST "https://apexscout.ai/api/opportunity-check" \
-H "content-type: application/json" \
--data '{
"subject": "Agent trust scoring for crypto vendors",
"buyer": "Crypto fund operator",
"marketType": "vendor",
"geography": "United States",
"goal": "Decide whether this topic is strong enough to package into a deeper diligence offer.",
"knownSignals": [
"Operators keep asking for a faster first-pass trust screen before pilots",
"Funds want a lightweight way to compare agent vendors before deeper diligence"
],
"constraints": [
"Keep the first offer lightweight",
"Do not assume the buyer already trusts agent vendors"
]
}'After the unpaid probe returns HTTP 402, pay the listed route price with your own x402 client and retry the same POST for HTTP 200.
x402 paid retry
Buyer client controls payment.
import { wrapFetchWithPayment } from "@x402/fetch";
const baseUrl = "https://apexscout.ai";
const fetchWithPayment = wrapFetchWithPayment(fetch, walletClient);
const response = await fetchWithPayment(`${baseUrl}/api/opportunity-check`, {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"subject": "Agent trust scoring for crypto vendors",
"buyer": "Crypto fund operator",
"marketType": "vendor",
"geography": "United States",
"goal": "Decide whether this topic is strong enough to package into a deeper diligence offer.",
"knownSignals": [
"Operators keep asking for a faster first-pass trust screen before pilots",
"Funds want a lightweight way to compare agent vendors before deeper diligence"
],
"constraints": [
"Keep the first offer lightweight",
"Do not assume the buyer already trusts agent vendors"
]
}),
});
console.log(response.status); // 200 after your x402 client pays the listed route priceKite Passport
Delegated buyer sessions fit here.
Kite Passport fits ApexScout as a buyer-side delegated wallet path: a human approves the spending session, the agent probes ARD unpaid, then the buyer's own payment client retries the same x402 route.
Status: buyer-controlled-compatibility. Open Kite Agent Passport.
- Open /instant-x402 or /api/instant-x402.
- Pick the cheapest useful route and copy the sample payload.
- Send the route unpaid first and confirm the expected HTTP 402 challenge.
- Use the buyer's own Kite Passport or x402 client only after a human-approved spending session exists.
- Retry the exact same POST and expect HTTP 200 only after payment is handled by the buyer-controlled client.
Stripe Link Agents
Buyer Link approvals stay separate.
A readiness pack for buyer agents that may use Stripe Link's agent wallet for user-approved purchases while Agent Research Desk keeps production settlement on the proven Base x402 rail.
Status: watched buyer-wallet lane. Open Link Agents.
- Use Link only as a buyer-controlled approval wallet if your agent already has that flow.
- Open /instant-x402, pick an ARD route, and send the unpaid probe first.
- Expect HTTP 402 from ARD before any buyer-side payment attempt.
- Keep ARD settlement on Base x402 unless a separate Stripe/Link proof is designed and approved.
Guardrails
Conversion pressure without unsafe automation.
- This page does not execute paid purchases automatically.
- This page does not store or publish buyer prompts publicly.
- Public metrics remain aggregate-only.
- Base remains the proven production settlement rail.
- Kite Passport is treated as a buyer-controlled delegated-payment path, not as ARD-owned funds or a live settlement switch.
- Stripe Link Agent Wallet is treated as buyer-side approval readiness, not as ARD card settlement.
- Polygon proof-pack work and Solana watch-only tracking do not change the listed Base checkout.
Kite boundaries
Readiness is not rail acceptance.
- ARD does not create Kite Passport accounts, agents, sessions, passkeys, or OAuth flows.
- ARD does not hold buyer funds or ask buyers to fund an ARD-controlled wallet.
- ARD does not auto-pay any route from the public testbench.
- ARD does not accept Kite mainnet settlement until a separate proof window is approved and verified.
Link boundaries
No card or token settlement is active.
- Do not add Stripe secret keys, Link OAuth, Checkout Sessions, PaymentIntents, card settlement, shared payment tokens, Tempo streaming payments, or token issuance to the live payment flow.
- Do not create Link spend requests or approve purchases from this service.
- Do not claim ARD accepts Link, cards, or shared payment tokens until a separate proof design and settlement test pass.
- Do not change the working Base mainnet x402 middleware, facilitator, seller wallet, endpoint paths, or route prices.
- Do not expose buyer prompts, wallet-level request history, raw feedback comments, watched subjects, or paid response contents.
Next Surfaces