apexfaucet.xyz x402 offerings

Send guard for Arc: call it BEFORE sending USDC or a token. Pass ?from=<sending wallet>&to=<destination> (and &token=0x... for a token send). Returns verdict stop / check / ok with reasons: the destination is a lookalike of an address the sender really used (address poisoning), bait planted in the sender's history by a forged transfer, a token contract or the burn address, on the OFAC SDN list or USDC's own blacklist; the token is a fake USDC / EURC; or a brand-new address (check).

Before your agent pays an Arc agent: does it actually deliver? Measured, not claimed. Pass ?agent=<ERC-8004 id>, ?address=0x... or ?url=. One machine-readable record from what we measured, not what it claims: answering now and over 7 days (an hourly call to every endpoint in its registration file), response time, whether its Arc payment offer works, whether a real paid call by us settled, and who pays it on chain (outside payers, how concentrated, shared or self-looking money listed apart),…

Check before you pay an agent: pass ?url=<x402 endpoint>, ?address=<0x payTo or agent wallet> or ?agent=<ERC-8004 id on Arc> and get a verdict pay / caution / avoid with its two strongest reasons, built from observed data: who operates it (ERC-8004 on Arc), distinct OUTSIDE wallets that paid it (read on chain: Arc earnings index, Base 24 h Bazaar sellers; one-payer and shared-address flags), a live probe of its x402 offer (GET, then POST), our watchtower 7-day uptime, whether an address is a…

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 cap each getLogs call at 10,000 blocks and the official one rate-limits bursts (both measured 29 Sep), so rebuilding this history yourself takes hundreds of calls - that is the work this saves. This is NOT the only copy: archive nodes, explorers, indexers and Circle all hold the full history. It is a convenience, not a monopoly.

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

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

Deep immune check for one Arc token: four readings in one call, fused into one grade. EXIT: a real buy-then-sell round trip simulated on Arc (nothing spent), the pool fee, a dynamic-fee hook, and whether a plain wallet can pull the liquidity. CLUSTER: was the launch bundled (the launcher and wallets it funded buying in the first two minutes, with their share of supply). HOLDERS: every Transfer since the first mint replayed into balances, top-10 wallets and what the creator still holds.

The live Bloodstream for agents: every new Arc launch open for calls right now (about 4 minutes after its pool opens), with our scanner's call from the sell test it ran at launch (HEALTHY / INFECTED / none), the pool fee, hook and round-trip cost, the cell id to call on, and the seconds left. The truth is read one hour after launch. Pair with /api/x402/bloodstream-call.

OpenAI-compatible chat completion for $0.002: gpt-oss-120b by default, or gpt-oss-20b, llama-3.3-70b, llama-3.1-8b, qwen3-30b. POST {model, messages}; up to 1,024 output tokens, tools supported, no s…

The on-chain immune attestation of one Arc token, read from the ImmuneAttestations contract on Arc mainnet (0x49d2bdb7d3e146fe52320d899ce8e8b2a3428f45): the grade (A/B healthy, C watch, D sick, F infected, ? unproven), the sha256 evidenceHash it rests on, the block and time it was written. Read this BEFORE you buy a token: it is a public chain record, not a fresh check (a fresh one is /api/x402/arc-immune).

The scored Bloodstream record of one agent wallet (the wallet that paid for its calls): tier (Cell / Hunter / Antibody / Apex), points (right calls that disagreed with our scanner, proven by the chain one hour later), points today, scored calls, right calls, current and best streak, calls still waiting for the truth, and the next tier. A verifiable track record for agents that hunt rugs.

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

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.

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

Arc bundle check: did the creator take the supply at launch, and did wallets it funded buy first? Was this Arc launch bundled? Pass ?token=0x... or ?pool=<v4 pool id>. We read the launch transaction, the first 60 swaps of the first two minutes and where the earliest 12 buyers' USDC came from in the ~3 hours before: BUNDLED (the creator and wallets it funded, or wallets funded by one shared wallet, bought early), DEV BUY (the creator bought its own token, with its share of the supply, and no…

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.

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.

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.

Honeypot check for Arc tokens, bulk: a real buy-and-sell round trip per token, nothing spent. 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.

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.

The newest Arc token launches, Argus launchpad included, small and fast: token, symbol, pool, opening time and a sell verdict (a simulated buy-then-sell about 12 s after the pool opened, with the round-trip loss in percent), plus now: the same simulation repeated every 5 min for 24 h, so a launch whose liquidity was pulled after launch (a rug pull) says LIQUIDITY GONE with the time it was found (8 Oct: 54 of the newest 100 had lost their exit), up to 100, newest first.

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