Archipelago token reports
payment-ready until 2026-10-12
Paid reports on tokens traded on Arc, for AI agents and programs.
Call it x402 v2
x402 v2
- Base URL
- https://idx.archipelagodex.xyz
- Payment
- x402 v2, header channel
$ curl -i 'https://idx.archipelagodex.xyz/x402/report/0x3945df1f8dd8f753fb62e428f3aaeb2c185a6e26' An unpaid request returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.
Endpoints 1 paid route on idx.archipelagodex.xyz
Prices as captured in the 402 response: $0.01, unchanged since first capture.
Example 402 response
Endpoints and prices
| Method | Path | Description | Price | Network | Asset | 402 channel | Captured |
|---|---|---|---|---|---|---|---|
| GET | / | No description | $0.01 | - | USDC | header | since 10-05 |
Payment evidence
402 payload captured at . Check evidence JSON · Measurement methodology.
1 payload captured by the monitor.
25 lines, scroll inside
{
"error": "PAYMENT-SIGNATURE header is required",
"accepts": [
{
"asset": "0x3600000000000000000000000000000000000000",
"extra": {
"name": "USDC",
"version": "2",
"assetTransferMethod": "eip3009"
},
"payTo": "0xDcf7a2683aCaaC06E85a50c15BAf59c8E8b1e681",
"amount": "10000",
"scheme": "exact",
"network": "eip155:5042",
"maxTimeoutSeconds": 120
}
],
"resource": {
"url": "https://idx.archipelagodex.xyz/x402/report/0x3945df1f8dd8f753fb62e428f3aaeb2c185a6e26",
"mimeType": "application/json",
"description": "Archipelago token report: market, pools, launchpad, copy and contract checks for one Arc token"
},
"extensions": {},
"x402Version": 2
} Can I trust it score from our own monitoring
score from our own monitoring
#124 of 350 in Data. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.
- Reliability
- 100% uptime 30d
- Compliance
- A 14/14 checks pass
- Price
- $0.01 p61 in Data
- Risk
- clean no risk flag
- Traction
- ---
14/14 compliance checks
- 402 payload captured
- accepts[] array present
- payTo address recoverable
- payTo at accepts[0].payTo (conformant shape)
- payTo is a valid on-chain address
- atomic price declared
- atomic price in a sane range
- asset (token) address declared
- network resolves to CAIP-2
- payment scheme declared
- served over HTTPS
- declares the current x402 version (2)
- EIP-712 domain parameters present on every EVM entry
- x402 v2 envelope delivered in the payment-required header
402 terms unchanged since 2026-10-05. Last up 2026-10-05.
── Site signals
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
How the score works
What the score read on this service: status online, 100% uptime, latest daily rollup (no 30d window yet), 374ms response p95, x402 compliance 14 of 14, $0.01 price against the category, no known payTo, so no on-chain traction to read. Each of those is measured, and each is published in full below.
The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.
Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.
It is a score inside Data, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 350 listings, this one among them: the same 350 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.
All measured facts
What it does
Paid reports on tokens traded on Arc, for AI agents and programs. One JSON report per token: price, liquidity, 2% depth, 24h volume, every pool with its fee and hook, the launchpad that launched it, copy and same-ticker flags, CoinGecko listing, pulled liquidity, and contract checks (proxy, owner, mint, pause). 0.01 USDC per report over x402 v2, exact scheme, on Arc mainnet (eip155:5042), settled by Circle's Facilitator Service. Facts read from Arc, not a rating.
Archipelago token reports is a listed x402 Data API. No payment network has been captured yet. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.
Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.
Page rendered at . This response time is separate from the observation and computation times attached to each measurement.
Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.
Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.
Observed daily coverage: 2026-10-05 to 2026-10-05 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.
Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.
x402 List home · Services · Data
- uptime · latest daily rollup
- -
- uptime 7d
- -
- uptime 30d
- -
- uptime 90d
- -
- response p95
- 374ms
- avg response
- 374ms
- total checks
- 1
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
- price (min)
- $0.01
- category percentile (min)
- p61 in Data
- endpoints / prices
- 1 / 1
- model
- flat
- stability
- 100%
No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.
- domain age
- 8d
- registrar
- HOSTINGER operations, UAB
- hosting
- custom
- domain created
- 2026-09-26
Identity facts, not a risk score.
No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.
- member since
- 2026-10-05
Recent checks
| Checked at (UTC) | Status | HTTP | Response | Endpoints |
|---|---|---|---|---|
| Online | 402 | 361ms | 1 | |
| Online | 402 | 379ms | 1 | |
| Online | 402 | 395ms | 1 | |
| Online | 402 | 373ms | 1 | |
| Online | 402 | 398ms | 1 | |
| Online | 402 | 374ms | 1 |
Over time
No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.
- Uptime
- no completed-day data
No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.
More charts
10-05* UTC
Each series spans only the dates it has data for. Every series is also served as JSON at /api, /scores, /volume and /buyers.
Values
* today so far, partial (UTC).
The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.
Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.
| Day | Uptime | Response | Compliance | Price percentile | Site signals |
|---|---|---|---|---|---|
| 2026-10-05* | 100% | 383.80ms | 14/14 | p61 | 2/6 |
Alternatives in Data
5 of 349 other ranked services in Data, ordered by the same measured score.
Own this service?
Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.
Update this listingEarn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.
Verify this service ($0.25)Embed a badge
HTML
<a href="https://x402-list.com/services/ archipelago-token-reports? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ archipelago-token-reports.svg" alt="Archipelago token reports listed on x402-list" height="28"> </a>
Markdown
[](https://x402-list.com/ services/ archipelago-token-reports? utm_source=badge& utm_medium=referral& utm_campaign=embed)
HTML, live uptime variant
<a href="https://x402-list.com/services/ archipelago-token-reports? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ archipelago-token-reports.svg? data=uptime" alt="Archipelago token reports uptime on x402-list" height="28"> </a>
Delisting
To request delisting, email info@x402-list.com or update your listing at /services/archipelago-token-reports/update.