inspect-x402-endpoints

Inspect x402 Endpoints

Use IntentFence to make one bounded, credential-free request to a public HTTPS route and validate its live x402 challenge. IntentFence never follows redirects, forwards caller credentials, or pays the target.

Collect the policy

Require one target_url. Default to GET; use HEAD or POST only when the caller identifies the intended method. For POST, include only the public body needed to elicit the payment challenge.

Ask for these optional limits when they matter:

• max_price_usdc: the largest target price the caller accepts.
• allowed_payees: the exact Base recipient addresses the caller already approved.

Never send a cookie, API key, bearer token, wallet signature, private key, or seed phrase to the target or IntentFence. This check proves endpoint readiness and policy fit at the observation time; it does not prove merchant identity, authorization, delivery, or future behavior.

Run the check

Prefer the MCP tool intentfence_x402_readiness at:

https://agentpass-protocol.rmalka06.chatgpt.site/api/mcp

Pass arguments such as:

{
  "target_url": "https://merchant.example/api/paid-resource",
  "method": "GET",
  "max_price_usdc": "0.10",
  "allowed_payees": ["0x1111111111111111111111111111111111111111"]
}

The live check costs exactly 0.002 USDC on Base. Make the first call without a payment to inspect IntentFence's own PAYMENT-REQUIRED response. Before a wallet signs or an MCP client automatically retries, show the fee and obtain the caller's explicit authorization. Cap the IntentFence payment at 2000 USDC atomic units and preserve the input unchanged across the retry.

If no x402-capable signer is available, return the challenge and integration guidance. Do not ask the caller to paste reusable wallet credentials.

Use REST when MCP is unavailable

POST the same input to:

https://agentpass-protocol.rmalka06.chatgpt.site/api/x402-readiness?utm_source=agent_skill&utm_medium=agent&utm_campaign=inspect_x402_endpoints