Verify a third-party x402 endpoint before your agent pays it: does it return a valid 402, what payTo/network/price does it advertise, is that payee real on-chain, and how diverse…
Verify a third-party x402 endpoint before your agent pays it: does it return a valid 402, what payTo/network/price does it advertise, is that payee real on-chain, and how diverse are its payers? Multichain verdict with raw evidence.
| Method | Endpoint | Price | Description |
|---|---|---|---|
GET | /v1/marketplace/api/trust-resource | $0.023 | Invoke Trust Resource (Crypto Data) and return the upstream response. |
Requests are paid per call over the x402 protocol. Call the endpoint, receive a 402 Payment Required quote, then repeat the request with the signed payment header. The SDKs do both steps for you.
# 1. Ask for a quote
curl -i https://api.jarvisclaw.ai/v1/marketplace/api/trust-resource
# 2. Pay it (the SDK signs and retries for you)
curl -H "X-PAYMENT: <signed-payload>" https://api.jarvisclaw.ai/v1/marketplace/api/trust-resource
Open in the marketplace
Docs: Getting started · x402 payments · x402 discovery · All APIs