The io.github.jblaz6335/ai-data-marketplace MCP server provides access to a catalog of 43 audited, pay-per-use data and security products. It supports x402 v2 USDC payments and is deployed on Base, enabling usage of the offered products via the server.
🛠️ Key Features
43 audited data and security products
Pay-per-use access model
x402 v2 USDC payments
Base deployment
🚀 Use Cases
Purchasing and using audited data and security products on a pay-per-use basis
Integrating Base-based x402 v2 USDC payment flow with data/security offerings
⚡ Developer Benefits
Centralized catalog access to 43 audited products
Clear billing approach: pay-per-use with x402 v2 USDC on Base
Model Context Protocol (MCP) server and machine-to-machine data API gateway powered by the x402 Payment Protocol on Base Mainnet.
No API key. No account. No subscription. A live-source catalog of pay-per-call products — EVM chain reads, stock quotes and SEC filings, FX rates, token security audits, OFAC sanctions screening, LEI and VIN lookups, and more — priced from $0.001 per call and paid per request in USDC.
Try any product free before you pay. Every billable route accepts ?preview=true and returns a bounded sample of the real deliverable from the real live source, so an agent can verify the data is worth buying first. Previews are for evaluation: long lists and long fields are clipped, every response says whether it was truncated, and short results come back complete.
Version 2.8.3 can complete the x402 challenge, authorization, retry, and settlement automatically. The buyer key stays inside the buyer's local MCP process; the marketplace never receives it. Use a dedicated low-balance Base wallet, not a primary wallet.
Call any product with auto_pay: true. The adapter refuses a price above X402_MAX_PAYMENT_USDC, refuses conflicting payment inputs, and never falls back to an uncapped purchase. Without these environment variables, preview and manual-signature behavior remains unchanged.
Official MCP Registry name: io.github.jblaz6335/ai-data-marketplace.
PulseMCP: queued for ingestion through its Official MCP Registry feed
Every product in the catalog is billable and backed by a declared live source, a verified snapshot, or a transparent deterministic processor - there are no sample fixtures. Every API response identifies its data mode, availability, billing state, and backing source. Counts and prices always come from the live OpenAPI document, never from this README.
The newest demand-led lanes add low-cost atomic calls and answer-ready bundles for:
read-only agent transaction preflight, ERC-20 allowances, and contract proxy evidence;
The paid OpenAPI contract contains exactly the billable products - nothing more. Withdrawn concepts return HTTP 404 rather than lingering as unpayable routes.
Data Schema Inspection Mode
Client applications and autonomous agents can evaluate response schemas and data quality without executing a paid transaction by adding the preview=true parameter. The preview is a bounded sample of the same live result, carries preview_truncated and a purchase block describing the paid call, and is rate limited per tool so it stays an evaluation step rather than a free tier:
Beyond the loop lane: market data, SEC filings, sanctions screening, VIN and entity verification, token security, and composite research briefs. The complete current list with live prices is always the OpenAPI document - this README deliberately does not duplicate it.
Standard x402 v2 Payment Flow
Every billable product uses x402 v2 exact payments on Base mainnet, settled through the Coinbase CDP facilitator:
Call a paid endpoint without payment and read the base64-encoded PAYMENT-REQUIRED response header.
Use an x402 v2 client and buyer wallet to sign the exact USDC authorization.
Retry with the resulting PAYMENT-SIGNATURE header.
On success, read the settled transaction details from PAYMENT-RESPONSE.
The MCP adapter returns both the decoded challenge and the original payment_required_header. A compatible buyer can sign that challenge and retry the same tool with the payment_signature input. Buyers who configure the optional capped local wallet can instead set auto_pay: true and complete the entire flow in one tool call. Successful responses include payment_response_header.
The server advertises Bazaar-compatible discovery schemas on every 402 challenge while keeping seller-owned OpenAPI, MCP, sitemap, and agent-purchase documents canonical. The Coinbase CDP facilitator handles verification and settlement; USDC is delivered directly to the configured marketplace wallet.
Legacy Integration Client (client.py)
The included Python helper preserves the confirmed-transaction fallback for older integrations that do not yet use an x402 v2 signing client:
python
import requests
MARKETPLACE_URL = "https://ai-data-marketplace-1042299154756.us-central1.run.app"# 1. Request the standard challenge and legacy invoice body
invoice_response = requests.get(f"{MARKETPLACE_URL}/api/v1/candles?ticker=bitcoin")
invoice = invoice_response.json()["x402_invoice"]
print("Pay this Base USDC invoice with an external wallet:", invoice)
# 2. After paying externally, retry with the real Base transaction hash and invoice ID
headers = {
"x-402-payment-tx": "0x_YOUR_REAL_BASE_TRANSACTION_HASH",
"x-402-payment-id": invoice["payment_id"]
}
data = requests.get(f"{MARKETPLACE_URL}/api/v1/candles?ticker=bitcoin", headers=headers).json()
print("Payload Result:", data)
License
MIT License. Open-source Model Context Protocol server.
