Agent Commerce Guard Paid PackageGET /api/x402-download · x402 API by fxjim
AI agent spending controls and agent workflow guardrails for x402 commerce security. Download the Agent Commerce Guard CLI, policy templates, examples, and installable buyer skill for payments, deployments, posting, token launches, wallet access, credentials, and destructive commands after a verified 1 USDC Base payment.
What does this x402 API do?
Agent Commerce Guard Paid Package. This is an x402-gated GET API resource from fxjim. TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-08-05. The listing records $1 USD-denominated per request on Base. No settled paid call has been verified.
- Published price
- $1 USD-denominated per request
- Networks
- Base
- Latest evidence
- TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-08-05
- Resource ID
- 9bd4d29a9081b438a8dd3184
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://agent-commerce-guard.vercel.app/api/x402-download", {
method: "GET",
});
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.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Observed in 402-index
Discovered through self-registered.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- Origin reachable
HEAD https://agent-commerce-guard.vercel.app/ returned 200.
- Registry record checked
Registry health: healthy.
What evidence supports this listing?
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. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is $1 USD-denominated per request. Raw protocol requirements remain visible below for implementation and audit use.