Source-backed web, company, product, news, website and deep research with citations, plus document research, Python data analysis, comparisons, and text embeddings for AI agents.
VERDICT
ranking generation 3weak 39/100 #130 of 130 in AI by measured score
What the score read on this service: status offline, 0% uptime 24h (no 30d window yet), response time not measured, no gradeable x402 checklist (scored on the unverified prior), price not captured, 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.
It is a score inside AI, 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 130 listings, this one among them. That set is wider than the 130 the position above is counted against, 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.
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.
ALTERNATIVES IN AI
Other AI services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).
| SERVICE | BAND | SCORE | UPTIME 30D | VOL 30D |
|---|---|---|---|---|
| Otto AI | strong | 96 | 100% | $61.84 |
| x402engine | strong | 93 | 100% | $26.31 |
| Agent402.tools | solid | 92 | 98.8% | $136.44 |
| Exa | solid | 89 | 99.9% | $45.95 |
| vaaya | solid | 89 | 100% | $33.09 |
ASSESSMENT
updated 2h agoThe parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.
reliability 0%
- uptime 24h
- -
- uptime 7d
- -
- uptime 30d
- -
- uptime 90d
- -
- response p95
- -
- avg response
- -
- total checks
- 1
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
compliance unknown, stale (probe failing)
x402 compliance not evaluated yet.
price -
- price (min)
- -
- category percentile (min)
- -
- endpoints / prices
- 0 / 0
- model
- unknown
- stability
- -
risk clean
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
- 3d
- registrar
- HOSTINGER operations, UAB
- hosting
- custom
- domain created
- 2026-09-11
Identity facts, not a risk score.
traction ---
No settlement address is mapped for this service yet, so on-chain volume cannot be measured. Shown as unmeasured, not zero.
WHAT IT DOES
ai-derivedNo AI synthesis has been produced for this service yet.
ENDPOINTS
| METHOD | PATH | DESCRIPTION | PRICE | NETWORK | ASSET | 402 CHANNEL |
|---|---|---|---|---|---|---|
| GET | /answer | --- | USDC | - | ||
| GET | /company-research | --- | USDC | - | ||
| GET | /compare | --- | USDC | - | ||
| GET | /data-analysis | --- | USDC | - | ||
| GET | /ecommerce-research | --- | USDC | - | ||
| GET | /embeddings | --- | USDC | - | ||
| GET | /file-research | --- | USDC | - | ||
| GET | /news-research | --- | USDC | - | ||
| GET | /product-research | --- | USDC | - | ||
| GET | /research | --- | USDC | - | ||
| GET | /website-research | --- | USDC | - |
REQUEST / RESPONSE EXAMPLE
An unpaid request to GET /answer returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.
curl -i 'https://scopeapi.dev/answer'
No 402 response body has been captured for this service yet.
OVER TIME
All charts use the 30d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/scope-research-api/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.
checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression
COMPLIANCE
not evaluated · stale (probe failing)last 402 captured --- · last up ---
- 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
SITE PILLARS
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
recent checks (7) live · click to expand
EMBED THIS BADGE
<a href="https://x402-list.com/services/scope-research-api?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/scope-research-api.svg" alt="SCOPE Research API listed on x402-list" height="28"> </a>
[](https://x402-list.com/services/scope-research-api?utm_source=badge&utm_medium=referral&utm_campaign=embed)
<a href="https://x402-list.com/services/scope-research-api?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/scope-research-api.svg?data=uptime" alt="SCOPE Research API uptime on x402-list" height="28"> </a>