perp funding next derived
api.usenami.ioMarket dataderived
GET https://api.usenami.io/v1/perp/funding-next
passabsent from every registry#3 by calls of 9 on this host
0.003 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-01 05:50 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / — / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-01 12:06 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.003 USDC
- Networks
- 1
How has the volume on this endpoint moved?
api.usenami.io serves perp funding next, a GET endpoint that TOLL places in market data, listed in neither registry at the last pull.
perp funding next is priced at 0.003 USDC on Base.
Its declared inputs are the query parameters venue, ticker and canonical_id.
perp funding next returns json; the example shows venue, ticker, mark_price, updated_at, canonical_id, current_rate and 2 others.
perp funding next answered the sweep of 2026-10-01 with a valid 402, as at every sweep since 2026-09-11.
perp funding next shares api.usenami.io with 8 other listed endpoints and is tied 3rd by calls with 7 others.
perp funding next takes 5% of the calls counted across api.usenami.io.
In the trailing 30 days: one call, one payer.
perp funding next was last called 42 days before the snapshot.
Closest in price to perp funding next within market data: chain erc20 balance at api.onesource.io and perp funding at agent402.tools.
perp funding next is priced above 13% of comparable listings in market data.
The wallet paid by perp funding next is the payee of 29 endpoints on one host.
Seller tags: funding, perpetual, trading and multi-venue.
perp funding next was missing from the Coinbase registry at the pull of 2026-10-01, confirmed at the pull of 2026-10-01; that is registry presence, not liveness.
The price of perp funding next is declared by 648 other listings in market data too.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-10-01 05:50 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x153872…10475c |
the checks, as of 2026-10-01 10:05 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-01 10:05 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 09:31 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 21:37 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 08:29 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 08:42 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 09:03 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 07:00 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-17 06:52 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 06:48 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 07:05 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:31 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:20 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 10:33 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:50 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-01 12:07 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"venue": {
"type": "string",
"required": true,
"description": "Venue name (e.g. binance, hyperliquid). Required."
},
"ticker": {
"type": "string",
"required": true,
"description": "Base ticker (e.g. BTC, ETH). Required."
},
"canonical_id": {
"type": "string",
"required": false,
"description": "Disambiguates a ticker that names two unrelated assets; a 409 on the ticker alone names the candidates. The response echoes the resolved `canonical_id`, so you always know which asset you were answered about."
}
}
},
"output": {
"type": "json",
"example": {
"venue": "binance",
"ticker": "BTC",
"mark_price": 107234.5,
"updated_at": "2026-05-31T17:03:12Z",
"canonical_id": "btc-crypto",
"current_rate": 0.0001,
"next_funding_time": "2026-05-31T20:00:00Z",
"funding_interval_hours": 8
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "perp funding next on api.usenami.io". https://tollindex.com/e/api-usenami-io-v1-perp-funding-next-f86f90. Accessed [access date].
BibTeX
@misc{toll-e-api-usenami-io-v1-perp-funding-next-f86f90-2026-10-13,
author = {TOLL},
title = {perp funding next on api.usenami.io},
howpublished = {\url{https://tollindex.com/e/api-usenami-io-v1-perp-funding-next-f86f90}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.