Laevitas API V2
https://apiv2.laevitas.ch/api/v1/V2/historical/futures/expired_expiries/%7Bmarket%7D/%7Bcurrency%7D
● healthy
search
Professional market data API for crypto derivatives, spot markets, prediction markets, Hyperliquid HyperCore data, proprietary volatility surfaces, and analytics. ## Authentication Use an API key for authenticated REST requests: ```http X-API-Key: your-api-key-here ``` Data and history endpoints also accept x402 without an API key: 1, 5 or 10 credits ($0.001 each) for data up to 1 year, 1–...
Category
search
Chains
base, eip155:8453, solana, solana:5eykt4usfv8p8njdtrepy1vzqkqzkvdp
Price
$0.1000–$5040.0000 USDC
Paid verification
How it worksNo sponsored paid call yet.
Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.
Quality grade
How grading works
A
94.8 / 100
Availability
40.0 / 40
Endpoint responded (HTTP 402)
Payability
20.0 / 20
- ✓ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✓ Payment address on record
- ✓ Settlement network declared
- ✓ Price declared
Demand
34.8 / 40
265 distinct payers, 9483 USDC transfers in the last 30 days
Owner verified
0.0 / 3
Nobody has claimed this listing yet
Endpoint last checked 6 h ago.
On-chain activity last read 2 d ago.
Availability and on-chain demand are both re-probed daily; the grade
updates automatically on the next pass. This grade sets search order and
leaderboards; the readiness score below is shown for reference only.
x402 readiness
A · 91/100
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here A, 94.8/100), which weighs availability, payability and on-chain demand. How the two differ
| Valid payment requirements | 10/10 | Payment requirements carry a payee, a mainnet network and a price. |
| Live 402 challenge | 25/25 | Paid endpoint answers with an HTTP 402 challenge (491 ms). |
| x402 version | n/a | x402 version not observed yet. |
| Signed descriptor | n/a | No x402 standard defines a signed descriptor. |
| Uptime (30 days) | 15/15 | 32/32 probes succeeded over 30 days (100%). |
| Resource declaration | 8/10 | 293 paid resources; 50 sampled lack a description. |
| Verified identity | 5/10 | Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control. |
| Freshness + modern flags | 5/5 | seen in a source within 7 days; declares x402. |
| Security declaration | n/a | Payment is the access control for an x402 resource. |
Applicable criteria total 75 points, scaled to 100.
Responsiveness: Responsive
(491 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_challenge
— We sent a request and got a live HTTP 402 challenge.
Also:
x402_manifest, catalog_listing.
Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.
Compared with peers
Against 10,060 reachable x402 APIs in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 90% of peers
- This listing 91 · peer median 78
- Latency
- Faster than 19% of peers
- This listing 491 ms · peer median 205 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
- Resource declaration −2
— Declare each paid resource with its input and output schema.
Now: 293 paid resources; 50 sampled lack a description.
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
- Site rank (Tranco)
- #931,977 of the top 1M
- laevitas.ch · list of 2026-11-10
Paid endpoints
293 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.
GET
https://apiv2.laevitas.ch/api/v1/options/catalog
GET
https://apiv2.laevitas.ch/api/v1/options/metadata
GET
https://apiv2.laevitas.ch/api/v1/options/ohlcvt
GET
https://apiv2.laevitas.ch/api/v1/options/volume
GET
https://apiv2.laevitas.ch/api/v1/options/trades/summary
GET
https://apiv2.laevitas.ch/api/v1/options/trades
GET
https://apiv2.laevitas.ch/api/v1/options/flow
GET
https://apiv2.laevitas.ch/api/v1/options/open-interest
GET
https://apiv2.laevitas.ch/api/v1/options/level1
GET
https://apiv2.laevitas.ch/api/v1/options/volatility
GET
https://apiv2.laevitas.ch/api/v1/options/ticker-history
GET
https://apiv2.laevitas.ch/api/v1/options/reference-price
GET
https://apiv2.laevitas.ch/api/v1/options/snapshot
GET
https://apiv2.laevitas.ch/api/v1/options/gex/catalog
GET
https://apiv2.laevitas.ch/api/v1/options/gex/latest
GET
https://apiv2.laevitas.ch/api/v1/options/gex/history
GET
https://apiv2.laevitas.ch/api/v1/options/gex/regime-changes
GET
https://apiv2.laevitas.ch/api/v1/options/gex/strikes
GET
https://apiv2.laevitas.ch/api/v1/options/gex/term-structure
GET
https://apiv2.laevitas.ch/api/v1/options/gex/profile
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/catalog
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/metadata
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/ohlcvt
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/level1
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/orderbook
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/orderbook-raw
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/volume
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/trades/summary
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/flow
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/trades
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/open-interest
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/ticker-history
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/carry
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/reference-price
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/snapshot
GET
https://apiv2.laevitas.ch/api/v1/perpetuals/liquidations
GET
https://apiv2.laevitas.ch/api/v1/futures/catalog
GET
https://apiv2.laevitas.ch/api/v1/futures/metadata
GET
https://apiv2.laevitas.ch/api/v1/futures/ohlcvt
GET
https://apiv2.laevitas.ch/api/v1/futures/level1
GET
https://apiv2.laevitas.ch/api/v1/futures/orderbook
GET
https://apiv2.laevitas.ch/api/v1/futures/orderbook-raw
GET
https://apiv2.laevitas.ch/api/v1/futures/volume
GET
https://apiv2.laevitas.ch/api/v1/futures/trades/summary
GET
https://apiv2.laevitas.ch/api/v1/futures/flow
GET
https://apiv2.laevitas.ch/api/v1/futures/trades
GET
https://apiv2.laevitas.ch/api/v1/futures/open-interest
GET
https://apiv2.laevitas.ch/api/v1/futures/ticker-history
GET
https://apiv2.laevitas.ch/api/v1/futures/carry
GET
https://apiv2.laevitas.ch/api/v1/futures/reference-price
How to call
cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://apiv2.laevitas.ch/api/v1/V2/historical/futures/expired_expiries/%7Bmarket%7D/%7Bcurrency%7D # expect HTTP 402 Payment Required (about $0.1/call)/.well-known/x402.json
https://apiv2.laevitas.ch/.well-known/x402
Listed in
Directories this entry was found in.
x402scan since 2026-05-22