apexfaucet.xyz

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

Every agent registered on Arc (ERC-8004 identity registry) with its agentId, owner and registration file — the full directory of who is operating on Arc, read from the chain. The free endpoint returns only the count and the first few.

Every token launch recorded by the Arc launchpad Portal, kept so you do not need to run an archive node. Public Arc JSON-RPC endpoints serve getLogs for roughly 69 hours and refuse anything older, so ordinary tooling cannot reach it - we watched that floor move while building this. This is NOT the only copy: archive nodes, explorers, indexers and Circle all hold the full history. It is a convenience, not a monopoly.

What it really costs to bring USDC into Arc over Circle CCTP, measured from arrivals rather than quoted. Every arrival we hold with its recipient, the amount credited, the fee CCTP took and the transaction, plus observed fees grouped by transfer size. Read from MintAndWithdraw on TokenMessengerV2 0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d, whose event signature we verified by hashing it rather than assuming it, and filtered to the USDC contract on every single log.

What a given operation SHOULD cost on Arc right now, in dollars - a price list computed at the gas price read at this block, and the companion to /api/x402/arc-gas which measures what transactions ACTUALLY cost across a spread of blocks. Use this one to quote an operation, that one to budget for the tail: the 20 gwei floor holds most of the time but is not a cap, and the response says so.

Who launched what on Arc, and did any of it ever trade. Every creator in our index with more than one launchpad token, with each token, the fees its vault holds, and the risk flags its pools carry. Fees accrue only from REAL swaps, so what a creator launches have earned is expensive to fake: EVERY COUNT LIVES IN summary (vaultsIndexed, distinctCreators, creatorsWithMoreThanOneToken) and none is quoted here: our vault index grew from 80 to 120 repeat creators inside a single evening on…

Arc exit check, bulk: up to 25 tokens or v4 pool ids on Arc (ids=a,b,c), each answered by a real buy-and-sell round trip with nothing spent (the probe contract for native-USDC pools, a sequential eth_simulateV1 through the launchpad router for ERC-20-USDC pools), sorted worst first: cannot sell, heavy loss, not measured, cannot buy. Each result states its method and the pool fee. Hooks run inside the check. Single checks are free at /api/arc/exit-check/{token}.

Arc fresh launches, REAL TIME, each with a sell verdict. About 92% of new Uniswap v4 pools on Arc are caught by a WebSocket on PoolManager Initialize and exit-checked ~12 s after they open (the watcher drops the oldest job when its queue passes 60), so you learn whether a launch can actually be sold before you buy it.

What a transaction on Arc ACTUALLY costs, measured from real receipts rather than quoted from the docs. The companion to /api/x402/arc-cost, which prices a named operation at the current gas price: that one is the quote, this one is the measurement and the tail. The most repeated claim about Arc is that USDC-as-gas means predictable low fees. The low half is true; the predictable half does not survive measurement, and that is what you are buying.

Every token symbol on Arc that more than one contract is using, with how many contracts wear each name and the canonical address where we have verified one. EVERY COUNT LIVES IN summary (symbolsReused, poolsIndexed, worstSymbol, worstCount) and NO count is quoted here, on purpose: the Arc index grows fast enough that a figure written into this text is stale within hours.

Arc launchpad fee vaults: every vault holding USDC right now, with its creator, its token and the change we measured since our previous scan, largest first. Fees only accrue from real swaps and a wash trader pays them on both legs, so vault growth is a costly-to-fake measure of genuine trading, unlike reported volume. Balances are the creator share and only the creator can collect them: distribute() pays creator() and treasury() and pays its caller nothing.

Did that Arc payment actually land? Pass ?tx=0x… and optionally ?to=0x… and ?expect=1.50 to get the payer, the amount, whether it reached your address, confirmations, finality and the gas paid — all in USDC. Handles the thing that breaks most Arc integrations: USDC is the NATIVE gas token at 18 decimals in tx.value AND has a 6-decimal ERC-20 view, so a verifier that only reads Transfer logs reports real payments as zero. Read-only: checking never consumes the payment.

Arc pre-trade risk in microseconds, no chain call: pass ?hook=0x… and get the verdict read straight out of the Uniswap v4 permission bits encoded in the hook address. It tells you what the hook is ALLOWED to do (run on every swap, rewrite the amounts, touch liquidity), not what it does: permission is not behaviour. No trap rate is quoted - the 83.7% we used to state came from a pre-buy sell quote and was withdrawn on 2026-09-22 after a real round trip sold 10 of 10 pools with that signature.

Arc sniper intelligence, full: every address we resolved buying a new Arc pool first (pools hit, median and fastest seconds to entry, USDC spent), plus the 300 most recent pools with swaps, volume, first buyer, depth at last swap and risk flags, rebuilt from PoolManager events every few minutes.

You receive EVERY address we have scored in scoreboard[], not a top-and-bottom sample, and summary.addresses states the exact count in the same response (it covers the scanner's rolling 24-hour window, so it rises and falls - which is why the live field is the promise and not a figure frozen in this text); until 2026-09-17 this returned only the best 50 and worst 50 while calling itself the full scoreboard. Arc FIRST-BUY scoreboard.

Every signed x402-style payment on Arc since launch, read from the chain (plain USDC transfers carry no marker of what they paid for and are not counted): each EIP-3009 authorization spent on Arc USDC (AuthorizationUsed on 0x3600..., joined to the transfer it moved, in either of the two forms Arc logs it) and every Circle Gateway batch (net flows per address, decoded from submitBatch).

Can you get out of this Base token, and what does it cost? Pass a Base token address: we find its deepest Uniswap v2, v3 or v4 pool against WETH or ETH (hooks included), then EXECUTE a buy and a full sell in one simulated Base block and return the ETH that comes back, the round-trip cost, and the revert reason if either leg fails. Plus name, supply and whether ownership is renounced. Executed, not estimated.

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.

Counterparty report for any Arc address: how often it is the FIRST buyer into a new pool and how fast it enters (a 2-second median is a machine, not a person), plus what it spent on those entries. IMPORTANT LIMIT: our scanner records only a pool's first buyer and only that pool's first 8 swaps, so later sales are NOT observed — treat the money figures as entry spend and early exits, not a full ledger. Behaviour, not identity; absent from our index means unknown, not safe.

Demo endpoint — proves your payment flow works.

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.

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.

Live Citizens City activity feed — agent actions, builds, transfers.

OHLC candles for a token, built from indexed trades. Pass ?tf=1m, 5m, 15m, 1h, 4h or 1d (default 5m) and ?limit=N up to 1000 (default 200); ?before=<unix seconds> pages backwards. Timestamps are unix seconds. The description used to name the timeframes without naming the PARAMETER, so a paying agent had no way to ask for one and silently got 5m whatever it sent (found 2026-09-17).

One call, one answer: should you buy this Arc pool? Pass ?pool=<v4 pool id> or ?token=0x… and get a 0-100 safety score with the reasons, fusing the pool fee from its key (on Arc the commonest trap: some pools take 49-93% of every trade), our launch watcher's real buy-then-sell round trip and what it cost, the hook's Uniswap v4 permission bits, and what the pool's FIRST buyer did within its first 8 swaps (we do not observe later buyers or later sells).

Render a web page in a real browser and return its full text and links.

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.

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.

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.

Recent whale-sized swaps across all tokens.

Render a whole section of a site - up to 25 pages - in a real browser and return every page as clean text.

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).

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.

The agent economy on Arc, mapped: every agent in the ERC-8004 identity registry that publishes a registration file (summary.registered and summary.withRegistrationFile carry both counts live; the registry grows, so no count is quoted here) with its name, what it does, the services it sells, its owner, its registration file and whether it accepts x402 payment — plus ?q= to search by capability ('audit', 'escrow', 'data').

The Arc pool graveyard, in full: every Uniswap v4 pool on Arc we measured above a lifetime volume floor (minVolumeUsdc), each with its pool id, its state (empty = zero liquidity at the moment of the read, or alive), its lifetime USDC volume, its fee and its hook. The counts live in summary (poolsMeasured, empty, alive, emptyPct, USDC volume through empty and live pools) and the time of the read in generatedAt.

The EURO rail on Arc, which nothing else reports. Circle EURC (0xbEf5f6d51CB62b58e6A8f77868681825C6fe21c1) is live on Arc and every other Arc data product, ours included until now, is about new launches and the people sniping them. You get every EURC transfer in the scanned window with from, to, amount, block and transaction, the full top-10 net receivers and senders, and the live counts in summary.

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).

Top 20 holders for a token, deduped by owner.

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.

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.

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.

Which agents registered on Arc actually answer. Every endpoint every agent lists in its ERC-8004 registration file (web, A2A, MCP, x402, the file itself) is called once an hour through an address-checked fetcher: A2A cards are read, MCP servers get the initialize handshake, x402 paywalls are parsed the way a standard client would and checked against the on-chain EIP-712 domains of USDC and EURC on Arc (a wrong domain means every signature fails - we name it).

X1 chain health: epoch, slot, TPS, validator count + delinquency, total/activated stake, supply. Sources api.x1.xyz cluster.

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.

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 Coinbase's own validator. Each problem comes with its fix.

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.

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.