Venues settle funding on different clocks. Hyperliquid and dYdX charge hourly, ApeX and edgeX every four hours, Paradex and Backpack every eight. Comparing those raw numbers is the fastest way to get funding wrong by a factor of eight.

Each rate is divided by its own settlement interval to get a one-hour rate, then annualised as rate × 24 × 365 × 100. Asset pages show both the venue's own quote and the annualised figure so you can check the arithmetic.

Hyperliquid lists kPEPE, where one contract is 1,000 PEPE. Other venues list PEPE directly, and some use a 1000 prefix. Stored raw, a consensus price would be wrong by three orders of magnitude.

Every ticker is reduced to a base symbol plus a multiplier, and prices are divided by that multiplier. As a check: across all multi-venue assets, the widest disagreement between any two venues on the same asset is well under one percent.

Where a venue publishes open interest in USD, that figure is used directly. Where it publishes a contract count, it is multiplied by that venue's own mark price rather than a consensus price, so the number always reconciles with the venue's own screen.

Site-wide totals add every venue together. Because the same underlying trades in many places, total open interest counts each venue's book separately. It measures activity across the ecosystem rather than the size of a single market.

The spread engine pairs the venue paying most to shorts with the one paying most to longs. The figure is gross: it excludes taker fees on both legs, slippage, borrow on collateral, and the margin you must post to hold two positions.

Thin markets routinely show enormous spreads that cannot be traded, so the engine applies a minimum open interest per leg, adjustable on the page.

Venues are polled independently and a failure is recorded rather than hidden. If a venue's API is unreachable, its profile page stays up and its live figures are marked stale instead of being silently replaced with zero.

Current per-venue health is on the status page.

Several venues let a front-end attach a builder code to an order and take a share of the fee. That attribution is made against the wallet that placed the trade, so an email account could never be credited with the volume it routed.

Sign-in therefore uses Sign in with Ethereum and Sign in with Solana, the EIP-4361 standard. You sign a message proving you control the address, no transaction is involved, and the address becomes the account. What each venue permits and what wikiperps charges is published on the builder codes page, and is currently zero everywhere.

Most venues expose a single endpoint covering every market and are polled every two minutes. A few have no batch endpoint and cost one request per market; those are polled less often to stay within their rate limits, and their timestamps reflect it.