MARKET MONITOR / CATALOGUE Services 139,498 MCP listed 41,963 x402 97,642 Rails Base / Solana / Polygon / Arbitrum Imported 2026-11-03 · 3 sources
Provider

api.genesistokenlabs.com

api.genesistokenlabs.com · 5 listed services · provider site

Web extract x402 REST usage

Use when an agent needs any web page as clean LLM-ready markdown (no ads, nav, or scripts) for RAG, research, or summarizing. Example input: GET /x402/v1/web-extract?url=https://example.com/article. Example output: {"url...

api.genesistokenlabs.com Search & Research 8 calls / 30d checked 2026-11-03
0.005 USDC per call per call

Bank gov lookup x402 REST usage

Use when an agent needs structured public bank or government records (institution by name/routing number, agency, or registry entry) for compliance, due diligence, or lead research. Example input: GET /x402/v1/bank-gov-l...

api.genesistokenlabs.com Search & Research 2 calls / 30d checked 2026-11-01
0.02 USDC per call per call

Wallet profile x402 REST usage

Use when an agent needs an onchain wallet summary (token balances, native gas, recent tx count, first/last activity) for risk checks, KYC-lite, or airdrops. Example input: GET /x402/v1/wallet-profile?address=0xd8dA…6045&...

api.genesistokenlabs.com Crypto & Payments 2 calls / 30d checked 2026-11-01
0.01 USDC per call per call

Token price x402 REST usage

Use when an agent needs a live crypto token spot price in USD for trading, pricing, or portfolio math, for $0.001 per call. Example input: GET /x402/v1/token-price?symbol=ETH (or ?address=0x…&chain=base). Example output:...

api.genesistokenlabs.com Data & Finance 1 calls / 30d checked 2026-11-01
0.001 USDC per call per call

Protected demo x402 REST usage

Use when testing an x402 client or wallet end-to-end: pay $0.01 USDC and get a signed JSON receipt proving payment settled. Example input: GET /x402/v1/protected-demo. Example output: {"ok":true,"paid":true,"network":"ei...

api.genesistokenlabs.com Crypto & Payments 1 calls / 30d checked 2026-11-01
0.01 USDC per call per call

Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.