Arc Archive

Every token launch recorded by the Arc launchpad Portal, kept so you do not need to run an archive node.

Overview

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. Each row is the block, the token contract, the addresses the Portal emitted (including the fee vault) and the transaction. The response states how many launches are held (held) from block 21001113 onward, growing hourly, with any range we could not read recorded as a gap rather than hidden. One call returns the NEWEST 5,000 by default; ?limit= raises that to 50,000 and ?sinceBlock= pages through the rest, so the whole archive takes several calls. This is a record, not a feed: it says what launched and when, and nothing about whether any of it was worth buying - for that see /api/x402/arc-exit-check-bulk.

Endpoint

Method	Endpoint	Price	Description
GET	/v1/marketplace/api/arc-archive	$0.1035	Invoke Arc Archive (Blockchain) and return the upstream response.

How to call it

Requests are paid per call over the x402 protocol. Call the endpoint, receive a 402 Payment Required quote, then repeat the request with the signed payment header. The SDKs do both steps for you.

# 1. Ask for a quote
curl -i https://api.jarvisclaw.ai/v1/marketplace/api/arc-archive

# 2. Pay it (the SDK signs and retries for you)
curl -H "X-PAYMENT: <signed-payload>" https://api.jarvisclaw.ai/v1/marketplace/api/arc-archive

Open in the marketplace