API reference
The four public interfaces — REST, the market WebSocket, the market-maker feeds and Ethereum JSON-RPC — and the conventions they share.
| Interface | Address | For |
|---|---|---|
| REST | https://rpc.vordium.com | every read of the committed state and records, and every signed write |
| Market WebSocket | wss://rpc.vordium.com/ws | prices, the book, fills, positions and commits as they happen |
| Market-maker feeds | wss://rpc.vordium.com/feeds | sequenced book, trade, order and fill streams with gap detection |
| JSON-RPC (EVM) | https://rpc.vordium.com/evmrpc | Ethereum tooling: balances, blocks, calls, logs |
The switch at the top of the page changes the addresses to the selected network.
Conventions
- Numbers. USDC amounts carry 6 decimals (
_6dec), sizes 18 (_18dec), order prices 8 (_8dec), oracle reads 6. Large integers are sent as decimal strings. - Writes are POST requests with a JSON body that carries its own signature (Signing). A
write answers
202with"status": "submitted"when it is received; read the state back to see it applied. - Refusals answer
400or403with acode(and for agents areason) and a plain meaning (Errors and refusal codes). Key your program on the code, never on the text. - Busy.
429means too many requests or a full intake; wait forRetry-Afterand send again. - Browsers can call every read: the API sends
Access-Control-Allow-Origin: *.
The network spec
GET /network-spec.json describes the network in one document: its chain id, genesis, endpoints, currency, markets,
bridge, agent rules and EVM status, each with where it comes from. Read its specVersion before reading anything else
from it; a field that reads null or {"available": false} is unknown, never a default.
| Fact | Mainnet | Testnet |
|---|---|---|
| Network spec | https://rpc.vordium.com/network-spec.json | https://testnet.vordex.xyz/network-spec.json |
| Spec version | v28 | v8 |
Network facts last checked against the network 2026-10-22 13:00:37 UTC · mainnet spec v28 · testnet spec v8