13trust / 100

Funding Spread

by Usenami in Markets & finance

x402 APIFailing, checked 5 h ago

Cross-venue funding-rate spread for one crypto perpetual: the highest- and lowest-paying venues and the gap between them in bps. Where a funding-arb screen starts, across both CEX and DEX perp venues.

GET https://api.usenami.io/v1/funding/spread/:symbol

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
0.0%
Response time
- typical, - slowest 5%
Last check
5 h ago: Expected HTTP 402, got 404
Next check
any minute now

How to call it

GET https://api.usenami.io/v1/funding/spread/:symbol

Each call costs $0.001 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

The listing has no example input.

GET https://api.usenami.io/v1/funding/spread/:symbol

Example response

The provider's example. We can't check it without paying.

{
  "max_rate": 0.0003,
  "min_rate": -0.0001,
  "spread_bps": 4,
  "symbol": "ETH-PERP",
  "venues": [
    {
      "rate": 0.0003,
      "venue": "binance"
    },
    {
      "rate": -0.0001,
      "venue": "okx"
    }
  ]
}

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.001.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.usenami.io/v1/funding/spread/:symbol'

# 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/funding/spread/:symbol' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
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.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.usenami.io%2Fv1%2Ffunding%2Fspread%2F%3Asymbol
const res = await pay("https://api.usenami.io/v1/funding/spread/:symbol");
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.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
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/funding/spread/:symbol")
    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

WhenResultHTTPTimePrice
5 h agoExpected HTTP 402, got 404404700 ms-
9 h agoExpected HTTP 402, got 404404679 ms-
13 h agoExpected HTTP 402, got 404404708 ms-
18 h agoExpected HTTP 402, got 404404589 ms-
22 h agoExpected HTTP 402, got 404404689 ms-
26 h agoExpected HTTP 402, got 404404615 ms-
31 h agoExpected HTTP 402, got 404404634 ms-
35 h agoExpected HTTP 402, got 404404570 ms-
39 h agoExpected HTTP 402, got 404404571 ms-
43 h agoExpected HTTP 402, got 404404180 ms-
47 h agoExpected HTTP 402, got 404404661 ms-
2 days agoExpected HTTP 402, got 404404602 ms-
2 days agoExpected HTTP 402, got 404404594 ms-
3 days agoExpected HTTP 402, got 404404618 ms-
3 days agoExpected HTTP 402, got 404404579 ms-