- Session auth — API key. Your server holds an issued key and
sends it as
X-Api-Key: ps_live_<keyId>_<secret>on every request. See API keys. - Per-operation auth — EIP-712. Every operation that moves
funds (placing orders, vault split / merge) additionally
requires an EIP-712 signature over the operation’s typed data.
An API key alone is never sufficient to move money. Each order,
split and merge is signed with the private key of the acting
wallet: your
associatedWalletforsingle_walletpartners, or the wallet named inX-User-Walletformulti_walletpartners. In the signed Order struct that wallet is thesigner, its vault is themaker, andsignatureTypeis1.
Retail user logins live on a separate surface. End users sign in
on the web app (
app.dev.predictstreet.sde.adifoundation.ai on testnet,
adipredictstreet.com on mainnet), which issues its own short-lived
session token. Partner integrations do not use or implement that
login; they authenticate with API keys only.Flow at a glance
Base URL
Retail user traffic (the web app —
app.dev.predictstreet.sde.adifoundation.ai
on testnet, adipredictstreet.com on mainnet) is a separate surface
and isn’t documented here.
Where to next
API keys
Format, scope taxonomy, endpoint coverage, rotation procedure.
Rate limits
Per-partner, per-wallet, per-IP buckets.
EIP-712 signing
How the per-operation order signature works.
Quickstart
First order end-to-end with an API key.