Oracles

Use the SEDA proxy when another system must verify Adjacent data before using it on-chain.

Adjacent publishes data to the SEDA oracle network through a SEDA data proxy. The proxy signs each response with a registered keypair. Overlay nodes verify that the payload came from Adjacent before settling it on-chain.

The testnet needs no key and returns delayed data. Mainnet responses require SEDA proof verification and are not generally available.

Endpoints

	Testnet	Mainnet
Host	`oracle.testnet.adjacent.markets`	`oracle.api.adjacent.markets`
Data tier	15-min delayed	Real-time
Access	Ungated	SEDA proof verification
Status	Live	Not generally available

Health

1curl "https://oracle.testnet.adjacent.markets/status/health"

Read index data

The proxy exposes the same index listings and price history as the REST API under the /proxy route group. Testnet needs no API key.

12345# List indices
curl "https://oracle.testnet.adjacent.markets/proxy/indices"

# Index price history (public tier allows interval=1hour|1d)
curl "https://oracle.testnet.adjacent.markets/proxy/indices/red/prices?interval=1hour&per_page=24"

See Indices and Reference rates for the underlying benchmarks, and the API reference for full schemas.