Email verification: is one address deliverable, disposable or a role account? Check ONE email address before you send to it: pass ?email=name@domain.com and get a verdict (deliverable-domain, role-account, disposable, bad-shape or no-mail-domain) from its shape, its MX records read live over DNS, 25 known disposable-mail domains and 27 role-account names like info, support and admin. The mailbox itself is not probed, and the answer says so. Paid in USDC on Base.

Bulk email verification: up to 100 addresses in one call. Clean an email list: pass ?emails=a@b.com,c@d.com (up to 100 in one call) and get a verdict per address plus totals. Each address is checked for usable shape, for MX records read live over DNS, against 25 known disposable-mail domains and against 27 role-account names like info, support and admin. Verdicts are deliverable-domain, role-account, disposable, undeliverable, unknown or invalid, and each one says in words what it means.

Portfolio exit analysis: pass up to 25 mints and get back which positions you are trapped in, ranked worst first. Single-token analysis is free.

Exit analysis: sell $N of a token and see what you actually receive, the slippage, and the largest position that exits under 5%. Constant-product maths on live pool reserves, not a safety grade.

Exit analysis: sell $N of a token and see what you actually receive, the slippage, and the largest position that exits under 5%. Constant-product maths on live pool reserves, not a safety grade.

APEX faucet metrics — claims, unique wallets, total XNT/APEX paid out.

The 200 most recent trades across all X1 tokens, newest first: token, side, amounts, wallet, signature, slot. 200 is the hard cap of this feed, not a sample of something larger.

X1 wallet threat report, per call: pass ?wallet=<address> and get that wallet's blacklist status, its links to known rug operators and the live alerts against it. Same answer the 5 XNT subscription gives, but priced per lookup so you do not have to commit — pay in USDC on Arc, Base or Solana, or XNT on X1.

Top 20 holders for a token, deduped by owner.

Web page extract: render a page in a real browser and return its text and links. Render a web page in a real browser and return its full text and links.

HTML to Markdown: any web page, JavaScript rendered, as clean Markdown for LLMs. A web page as clean Markdown for an LLM: pass ?url= and the page is rendered in a real headless Chrome (JavaScript runs), then its main content comes back with headings, lists, links, code blocks, quotes and tables kept as Markdown, and the menus, header, footer and forms left out. Bot walls and empty renders are refused before any charge. Paid in USDC on Base.

Website screenshot: capture any public URL as an image in a real headless Chrome, with its text. See a web page the way a person does: pass ?url= and get a 1280x900 screenshot (JPEG, base64) of the first screen, rendered in a real headless Chrome with JavaScript executed, plus the page title, its full visible text and its links. Bot walls and empty renders are refused before any charge. Paid in USDC on Base.

PDF to text: extract the text of any public PDF, page by page. The text of a public PDF, page by page: pass ?url= of a whitepaper, filing, invoice or paper and get every page's text with page markers, the page count and the file size. Parsed with pdf.js; up to 15 MB and 200 pages. A file that is not a PDF, will not open, or has no text layer (scanned images) is refused before any charge.

Forecast, weather alerts, nearby earthquakes, flood warnings and grid carbon for one latitude/longitude, each with its licence. What is happening at this place? Pass ?lat=51.5074&lon=-0.1278 and get, in one call: the forecast (US National Weather Service in the US, MET Norway elsewhere), active weather alerts (US), earthquakes within 300 km in the last 7 days (USGS, worldwide), flood warnings within 15 km (England, Environment Agency) and the Great Britain grid carbon intensity (inside Great…

Every pool we index on X1 with liquidity, volume and depth: the length of pools[] is the count, because it moves with the chain (1,368 on 2026-09-17, and the figure in this sentence is the one that rots, not the array). Until 2026-09-17 a hard cap returned 1,000 of them while calling itself the full inventory; it now returns all of them, and ?limit=N still works if you want fewer. Rows carry the age of their liquidity figure, and a stale one is labelled rather than dropped.

Search Wikipedia, Wikidata, Wikivoyage, Wiktionary, PsychonautWiki (harm reduction), arXiv, OpenAlex, Hacker News and Stack Overflow in one call. Research search in one call: Wikipedia, Wikidata (structured facts, CC0), Wikivoyage (travel guides), Wiktionary (meanings, translations), PsychonautWiki (harm reduction: name a substance and the answer leads with dose ranges, duration and dangerous combinations), Open Targets (drugs, diseases and genes, CC0), ChEMBL (drug molecules, phases, ATC…

Token screener, the top 200 by liquidity with every metric we hold for each. Not every token: the index is larger and this returns 200 of it (corrected 2026-09-22).

Website crawler: up to 25 pages of one site as clean text, robots.txt obeyed. Render a whole section of a site - up to 25 pages - in a real browser and return every page as clean text.

Sitemap reader: every URL a website publishes, from robots.txt and its sitemaps, with last-modified dates. Every URL a website publishes, from its own sitemaps: pass ?url= and we read robots.txt for Sitemap: lines (else /sitemap.xml and /sitemap_index.xml), follow nested sitemap indexes and gzipped files, and return each URL with its lastmod, up to 5,000. Unreadable files are listed with the reason. A site with no sitemap is answered before any charge.

Known vulnerabilities for one package version from OSV.dev, with CISA exploited-in-the-wild flag and the fixed version. Should I install this? Pass ?package=lodash&ecosystem=npm&version=4.17.15 (npm, PyPI, Go, crates.io, Maven, NuGet, RubyGems, Packagist, Hex, Pub) and get every known advisory for that exact version from OSV.dev (GitHub, PyPA, Go and RustSec databases), whether any of them is on CISA's Known Exploited Vulnerabilities list, severity, and the version that fixes each.

X1 threat intelligence, full machine-readable database: every blacklisted wallet and token with its reason, plus the related-wallet network built from on-chain funding links (463 related addresses as of 2026-09-17) that maps a rug creator to the rest of their cluster before they launch again. The public page warns people for free; this is the structured feed for machines.

Single token detail (price, holders, liquidity, change windows).

Find the MCP server or API for a job: 37,000+ MCP servers and 2,500+ APIs, refreshed hourly, plus measured status for Arc agents. Which MCP server or API does this? Pass ?q=weather forecast and get matches from the official MCP registry (37,000+ servers, CC0) and the APIs.guru OpenAPI directory (2,500+ APIs, CC0), refreshed every hour: how to connect (remote URL or package), description, repository, docs and OpenAPI spec, last-updated date with a flag for entries untouched for a year.

X1 chain (not Arc): top traders leaderboard ranked by NET XNT FLOW per wallet and token - XNT received from sells minus XNT spent on buys. It is NOT realized profit and loss: there is no cost basis, so a wallet still holding what it bought looks like a loser and one that sold an airdrop looks like a genius. The MCP twin was corrected on 2026-09-17 and this paid description was missed until the 2026-09-22 audit. For a cost-basis view use /api/x402/wallet, which prices the position proportionally.

Honeypot check before a swap: a simulated buy AND sell at your size on Arc, BNB Chain or X1, then an unsigned transaction; honeypots refused. APEX Trade Rail: before a bot buys a token on Arc, X1 or BNB Chain, simulate the buy AND the sell back at its size; a token you could not sell, or whose round trip costs more than maxLossPct (15 at most), is refused with the reason; otherwise the real pool, expected and minimum out, and UNSIGNED transactions for your own wallet.

Recent on-chain trades for one X1 token, newest first: timestamp, side, the amounts and mints on both legs, the trader address and the transaction signature, so every row can be checked on chain yourself. Returns up to 200 rows (?limit=N, default 50, hard cap 200) or fewer when the token has traded less than that. Read from our own indexed trade history, not from a third-party API.

Explain a transaction in plain English (Base, Arc): the function, every token moved, gas in USD. What did this transaction do? Pass ?chain=base|arc&tx=0x... and get one plain sentence plus the parts: who called which function (named from a table of common ones), every token and NFT that moved and between whom, native value, success or failure, and the gas paid in ETH and dollars on Base (ETH priced from the Uniswap v3 pool on chain) or in USDC on Arc, including native USDC that only appears as…

Is this token's volume real demand? 24h round-trip analysis: how much volume came from wallets buying and selling the same token back and forth (wash trading, arbitrage or market making) versus one-way trades, with the top round-trippers and pool liquidity. Optional ?hours=1..168.

Wallet profile for an X1 address: every token it traded with XNT spent and received, realized and unrealized PnL per token and in total, top winners and losers, and a win rate. The win rate counts closed profit only, on positions of at least 0.1 XNT; positions still held at a loss are counted separately (heldAtLoss), so read it beside totalPnlXnt, never alone.

Web page reader: up to 10 web pages as clean text in one call. Read web pages as clean text: pass ?urls=a.com,b.com (up to 10 in one call) and get each page title, meta description and readable body with script, style, nav and footer stripped, plus the final URL after redirects, the content type, the byte count and whether it was truncated. STATED PLAINLY BECAUSE IT CHANGES WHAT YOU ARE BUYING: this is a fetch, NOT a browser.

X1 chain (not Arc): recent whale-sized swaps across all X1 tokens.

The X1 Agent Registry (ERC-8004 for SVM, which APEX deployed on X1 on 27 Sep 2026), in full: every registered agent with its owner, registration file and the live check of every endpoint it lists (MCP handshake, A2A card, x402 paywall and the networks it accepts, web), whether it can be paid on X1, feedback counts and the registration transaction. Rescanned every 30 minutes; the answer states its age and the count, which is small because the registry is new.

Did that X1 payment actually land? Pass ?sig=<signature> and optionally ?to=<wallet>, ?mint=<token> and ?expect=0.5 to get the payer, how much reached that wallet in XNT or any SPL token, whether it covers what you expected, confirmed vs finalized, memos, fee and slot. Counted by balance change, so a payment sent by a program (escrow, multisig, router) is seen too. Read-only: checking never consumes the payment.

Bazaar SEO for x402 sellers: where your endpoint ranks in Coinbase Bazaar search and what to fix. Where does your x402 endpoint come up when an agent searches Coinbase's Bazaar? Pass ?url= and optionally &query= (up to 3; left out, your own tags are searched). For each search: your rank in the top 20, the sellers above you with their price, tags and 30-day payers, the median price, and the concrete fixes (serviceName, tags, the words your description opens with).

x402 validator: will Coinbase Bazaar list your x402 endpoint, and can a client pay it? Why will Coinbase not list your x402 endpoint, and can a standard client pay it? Pass ?url= (and &method=POST for a POST route). We read its 402 as a client does, check what Coinbase's facilitator and Bazaar enforce (accepts[0] network, the $0.001 minimum, descriptions over 500 characters, a bazaar schema that must describe info, query numbers typed as strings, routeTemplate, exposed headers), and ask…

Is this x402 seller real? Pass ?seller= with a host (api.example.com) or a payTo address (0x...). From Coinbase's own Bazaar counts (re-read every 6 hours) we return its listings, 30-day payers and calls, and the one number that separates customers from a test harness: how many times the average payer came back. For an Arc payTo we add its settlements from our full Arc x402 index: distinct payers and the top payer's share.

X1 chain: live XNT/USD price from the on-chain USDC.X/XNT pool, with the 1h and 24h change. A change is null when our price history does not reach back that far (historyMinutes says how far it does), never a shorter window under the longer name.