Prexora Docs
Whitepaper
Developers / Introduction

For Developers

Prexora exposes a read-only public API so you can build on its signals, outcomes and on-chain commitments. Everything that powers the public dashboard is queryable as JSON — and independently verifiable.

What you can build

Principles

PrincipleWhat it means for you
Read-only & publicThe documented endpoints are public and need no key for read access. No write access is exposed.
VerifiableSignals are ed25519-signed and a daily SHA-256 hash is anchored on Solana — you can confirm authenticity and timing yourself.
Funded vs displayResponses distinguish funded signals (staked, count toward performance) from display-only signals.
The edge stays privateThe API serves signals and outcomes, not the model internals, tuned thresholds or edge formula.

The data model

Three object types you will work with:

ObjectKey fields
Signalcity, market/event slug, side, bracket bounds, strength tier, rationale, funded flag, signature, timestamp.
Outcomelinked signal, resolved bracket, observed value, win/loss, stake, realized P&L, resolution timestamp.
CommitUTC date, canonical SHA-256 hash, Solana memo / transaction reference.

Quick start

Every endpoint returns JSON over HTTPS. Fetch the current track record:

curl https://<host>/export/track-record

Poll the live board (prices move ~every 60s, so polling faster than that is wasteful):

curl https://<host>/export/signals

Verifying a day on-chain

# 1. pull the day's signals + outcomes
curl "https://<host>/export/recent?date=YYYY-MM-DD"
# 2. re-derive the canonical SHA-256 over that payload
# 3. read the committed hash + Solana memo reference
curl "https://<host>/export/onchain-commits?date=YYYY-MM-DD"
# 4. confirm your hash == committed hash == on-chain memo

The memo format on Solana is prexora:commit:YYYY-MM-DD:<sha256-hex>.

i

Base URL, rate limits and CORS are environment-specific — use the host serving the public Prexora app. Treat the live API as the source of truth over any figure printed in these docs.