Perp Basis
by Usenami in Markets & finance
Per-venue basis for one crypto perpetual — mark versus index price, basis_bps = (mark−index)/index×10000, and contango/backwardation structure, across tracked CEX and DEX venues. Every venue has an index except Crypto.com, Variational and dYdX; dYdX publishes one oracle price, which is its mark. `venues_without_index` names the ones missing. Each venue also carries liquidity_state (live/dead/unknown), and a market with no trading is flagged unreliable however clean its basis looks.
https://api.usenami.io/v1/perp/basis- Price
- $0.005
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 576 ms
- 667 ms slowest 5%
- Last check
- Passed
- 4 h ago, next any minute now
Reliability
How to call it
GET https://api.usenami.io/v1/perp/basis
Each call costs $0.005 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
Built from the input schema. Replace the values with your own.
GET https://api.usenami.io/v1/perp/basis?ticker=exampleParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
canonical_id | string | No | Disambiguates a ticker that names two unrelated assets; a 409 on the ticker alone names the candidates. |
ticker | string | Yes | Base ticker (e.g. BTC, ETH). Required. |
Example response
The provider's example. We can't check it without paying.
{
"items": [
{
"asset_class": "crypto",
"basis_bps": -2.31,
"basis_reliable": true,
"index_price": 60292.9,
"liquidity_state": "live",
"mark_price": 60278.9,
"structure": "backwardation",
"updated_at": "2026-06-27T21:00:00Z",
"venue": "paradex"
}
],
"methodology": "basis_bps = (mark_price − index_price)/index_price × 10000; structure = basis sign (contango/backwardation/flat/unknown)",
"ticker": "BTC",
"venues_count": 18,
"venues_without_index": [
"Crypto.com",
"Variational",
"dYdX"
]
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.005.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.usenami.io/v1/perp/basis?ticker=example'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.usenami.io/v1/perp/basis?ticker=example' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.usenami.io%2Fv1%2Fperp%2Fbasis
const res = await pay("https://api.usenami.io/v1/perp/basis?ticker=example");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.usenami.io/v1/perp/basis?ticker=example")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Passed | 402 | 648 ms | $0.005 |
| 8 h ago | Passed | 402 | 667 ms | $0.005 |
| 12 h ago | Passed | 402 | 592 ms | $0.005 |
| 16 h ago | Passed | 402 | 565 ms | $0.005 |
| 20 h ago | Passed | 402 | 553 ms | $0.005 |
Show 10 older checks
| 24 h ago | Passed | 402 | 208 ms | $0.005 |
| 27 h ago | Passed | 402 | 197 ms | $0.005 |
| 31 h ago | Passed | 402 | 546 ms | $0.005 |
| 35 h ago | Passed | 402 | 576 ms | $0.005 |
| 38 h ago | Passed | 402 | 734 ms | $0.005 |
| 42 h ago | Passed | 402 | 568 ms | $0.005 |
| 46 h ago | Passed | 402 | 614 ms | $0.005 |
| 2 days ago | Passed | 402 | 579 ms | $0.005 |
| 2 days ago | Passed | 402 | 594 ms | $0.005 |
| 2 days ago | Passed | 402 | 542 ms | $0.005 |