Check an x402 seller's 402 terms and OFAC-screen payTo before you pay
Use before your agent pays an unfamiliar x402 seller: pre-flight check of the endpoint's payment requirements (network, amount, asset, payTo) plus an OFAC screen of payTo. Verdict ok|warn|block|not_402. GET https://api.moneytools.dev/v1/precheck?url=<endpoint you plan to pay>&method=GET. Price: 0.005 USDC per call via x402 (USDC on Base). HTTP free tier: 5 calls/day per IP on this /v1 endpoint (no payment header). MCP: 20 free tool calls per client per day. Failed calls are not settled. Our own product (MoneyTools). MoneyTools Team. Docs: https://api.moneytools.dev/llms.txt
1 route settlement-verified · $0.005 USDC/request · 1 endpoint · Verification · base network · x402 protocol
Verified routes
GET /v1/precheck· $0.005 · Verified with a $0.005 test payment on 15 Nov 2026 · receipt
Other routes are unverified.
Networks: Base (settlement-verified)
Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.
url https://payapi.market/mcp
Listing facts
- Provider
- MoneyTools
- Hosted at
api.moneytools.dev- Category
- Verification
- Price
- $0.005 USDC per request
- Payment networks
- Base
- Settlement-verified
- 1 route, last checked 2026-11-15
- Listed on PayAPI Market
- 2026-11-15
Try Check an x402 seller's 402 terms and OFAC-screen payTo before you pay
Call a verified route without paying first. The server should answer HTTP 402 Payment Required with the price, the USDC asset, the network and the wallet to pay. An x402 client pays that amount on Base and retries with the payment header.
curl -i "https://api.moneytools.dev/v1/precheck?url=https%3A%2F%2Ftools.moneytools.dev%2Fv1%2Fmcp-lint&method=GET&utm_source=payapi"
About this API
Check an x402 seller's 402 terms and OFAC-screen payTo before you pay is listed in the Verification category with pricing at $0.005 USDC/request. One route has been settlement-verified by PayAPI Market on 2026-11-15. View receipt on Basescan.
Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.
This API exposes 1 endpoint.
Add this badge to your README
Paste this on your site. The link points at this listing. Listing is free and PayAPI takes 0% of each job.
Markdown
[](https://payapi.market/api/check-an-x402-seller-s-402-terms-and-ofac-screen-payto-before-you-pay)
HTML
<a href="https://payapi.market/api/check-an-x402-seller-s-402-terms-and-ofac-screen-payto-before-you-pay"><img src="https://payapi.market/badge/check-an-x402-seller-s-402-terms-and-ofac-screen-payto-before-you-pay.svg" alt="Settlement-verified on PayAPI Market" height="20"></a>
Questions about this API
What does Check an x402 seller's 402 terms and OFAC-screen payTo before you pay do?
Use before your agent pays an unfamiliar x402 seller: pre-flight check of the endpoint's payment requirements (network, amount, asset, payTo) plus an OFAC screen of payTo. Verdict ok|warn|block|not_402. GET https://api.moneytools.dev/v1/precheck?url=<endpoint you plan to pay>&method=GET. Price: 0.005 USDC per call via x402 (USDC on Base). HTTP free tier: 5 calls/day per IP on this /v1 endpoint (no payment header). MCP: 20 free tool calls per client per day. Failed calls are not settled. Our own product (MoneyTools). MoneyTools Team. Docs: https://api.moneytools.dev/llms.txt It is provided by MoneyTools.
How much does Check an x402 seller's 402 terms and OFAC-screen payTo before you pay cost?
Check an x402 seller's 402 terms and OFAC-screen payTo before you pay is priced at $0.005 USDC per request, paid per call with no subscription. Verified with a $0.005 test payment on 15 Nov 2026. The exact amount for each call is in the HTTP 402 response before any money moves.
Do I need an API key or account to use Check an x402 seller's 402 terms and OFAC-screen payTo before you pay?
No. Check an x402 seller's 402 terms and OFAC-screen payTo before you pay uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.
Has Check an x402 seller's 402 terms and OFAC-screen payTo before you pay been verified?
Yes, 1 route. PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC settlement on-chain, most recently on 2026-11-15.
How does an AI agent find Check an x402 seller's 402 terms and OFAC-screen payTo before you pay?
Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.
More Verification APIs · Browse the marketplace · List your own API
Related APIs
- Basenames resolver API (Base names, * · 1 route verified · Basenames resolver API (Base names, *.base.eth): resolve a Basename to its address, or an address to its verified primary Basename, with owner, resolver, avatar, url and twitter records. Payment settles only after a successful (2xx) response; input errors are never charged.
- Inspect an x402 endpoint's payment challenge · 1 route verified · Inspect an x402 endpoint's payment challenge. One call, paid in USDC, no API key.
- OMENZ Authorize (pre-payment check for agents) · 1 route verified · OMENZ Authorize: the authorization step for agent payments. One call before paying any x402 endpoint: live quote + preflight (up, price within max, network, stablecoin, expected payTo), payee check (k
- HTML Table Schema Conformance · 1 route verified · Check already-extracted table headers and row widths against expected headers, required fields, optional order rules, and extra-header policy. Reports row numbers and schema findings without cell values. Does not fetch or parse HTML.
- Webhook Delivery Evidence Bundle · 1 route verified · Build a reproducible post-hoc bundle from caller-supplied webhook attempts. Hashes JSON payloads, normalizes attempt times, and flags retry, status, sequence, and payload-consistency anomalies. Does not send webhooks or prove source authenticity/delivery.
- x402 Resource Metadata Consistency · 1 route verified · Compare an x402 v1/v2 challenge with a caller-supplied resource manifest, including URL, version, metadata, and exact payment-offer set. Returns mismatch codes without echoing submitted values; deterministic and model-free.
More from MoneyTools
- Lint an MCP server's tool definitions (names, JSON Schema, required params)
- Ask "is this within my agent's budget
- For when an unattended AI agent needs a human to approve an irreversible
- Use this when an agent must turn a public web page or raw HTML into clean,
- ERC-20 token facts + balance: Name, symbol, decimals, total supply, owner,
- View all from MoneyTools
By MoneyTools