Liveness of the Arc Data API and the list of routes it serves. Returns the §3.5 envelope. Call this first to confirm the API base and see which live routes are wired.

Launchpad concentration on Arc over the recent window: HHI, pools created, v3 vs v4 launch counts, distinct deployer callers, and per-launchpad share/graduations/dead-on-arrival. NO_DATA until an hourly reading has been written; partial windows are NO_DATA, never a false zero.

Realised range-APR for Arc LP pools from the latest scan. Optional filters: pair (e.g. 'usdc/weth'), venue (e.g. 'aero-lite'), range_pct. APR assumes price stayed in range over the window; the warning states this. NO_DATA if no scan has been written.

How many of Arc's four public RPCs agreed at the last reading (of 4), and the head they agreed on. Below 2 the status is REFUSED — treat any Arc figure as not cross-checked until they agree again. A cheap trust gate before acting on other Arc data.

Screen a launched Arc token by contract address: its USDC-paired pool, fee, recent swap count, and the decoy-pool verdict (a fee above the cap, or a dynamic pool whose swaps charged above the cap, is refused). A cheap gate — it does NOT run a live buy/sell. NO_DATA if the token has not traded in the API's discovery window.

Honeypot test for an Arc token: a LIVE sell-simulation (buy then sell in one simulated transaction against current chain state) reporting the round-trip fraction recovered. Below ~0.9 the token is likely a honeypot or a punitive-tax trap. This is a heavy, paid-tier route. NO_DATA if the pool cannot be simulated (it is never scored zero on a failed simulation).

Decoy-pool verdict for a specific v4 poolId: whether this pool is the real venue for its token or a high-fee decoy that a naive buyer would route into. Explains the refusal reason. NO_DATA if the poolId is unknown to the API.

Fetch a BABA Capital ERC-8004 agent-card (the /.well-known/agents/.json identity document). Known names: 'baba-arc-data', 'baba-arc-yield'. Shows the agent's registry, agentId (null until registered), and x402 payment network.

List the ERC-8004 agents registered on Arc, from a validated hourly crawl. Each row carries agentId, owner, agentURI, host, name, skills, status (OK | UNRESOLVED | INVALID), whether it declares x402, and how concentrated its host and owner are. Optional filters: status, host, owner. Paged. An agent whose card will not resolve is listed as UNRESOLVED, never silently dropped.

Full record for one Arc agent by agentId: its on-chain owner and agentURI, the RAW card as served, and a validation report showing the evidence behind every flag (which key supplied the name, which supplied the skills, the exact key and value that prove an x402 or payment declaration, redirects, robots handling, and any fetch error). Use this to check the directory's claims yourself rather than trusting them.

Find an Arc agent that does something, and optionally one you can pay. q matches name, host and skills; skill matches skill ids/names/tags. IMPORTANT: x402=true means the card declares x402 SPECIFICALLY — it is a much smaller set than payment=true, which includes other settlement schemes (most of this registry prices in USDC via ERC-8183, which is not x402). resolvable=true restricts to agents whose card actually fetched.

Shape of Arc's ERC-8004 agent registry in one call: total ids, distinct owners, distinct hosts, how many resolve, how many declare x402 vs payment generally, status counts, and the most concentrated hosts and owners with their share of the registry. Facts only — the concentration numbers are stated so you can draw your own conclusion.