POST /agent/v1/vending/create-payment-link
Generate an EIP-681 crypto payment link for end-user wallets. Agent pays a micro-fee via x402. Generic mode: pass payTo and token in the body. Optional mode=botpay uses BotPay vending infrastructure.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://agent-api-task.vercel.app/agent/v1/vending/create-payment-link", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"amount",
"currency",
"mode",
"network",
"payTo",
"sessionId"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://agent-api-task.vercel.app/ returned 404.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
EVIDENCE
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call.