Choosing between spot and a perp?
Choosing between spot and a perp? This is the data that choice needs. Aggregate OI-weighted perpetual funding, open interest and basis for a coin across venues (CoinGecko, no key): who pays whom (longs crowded vs shorts crowded), the carry you earn or bleed holding the perp, and contango vs backwardation. Verdict neutral / elevated / extreme. Pass symbol=BTC. Funding annualised as an estimate (8h intervals assumed). A market-structure signal, not a price call. Not financial advice.
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://402.com.tr/api/x402/perp-funding
| Category | Market data |
|---|---|
| Provider host | 402.com.tr |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 1 from 1 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-10-10 | no x402 terms | 429 | 331 ms |
Example input (from the provider)
{
"method": "GET",
"pathParams": {},
"queryParams": {
"symbol": "BTC"
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"pathParams": {
"type": "object"
},
"queryParams": {
"properties": {
"symbol": {
"description": "Coin symbol (BTC, ETH, SOL\u2026)",
"type": "string"
}
},
"required": [
"symbol"
],
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}