Skip to main content
PredictStreet’s integrator API uses a two-layer authentication model:
  1. 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.
  2. 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 — the private key of your associatedWallet signs each order / split / merge.
This split gives you stable long-lived credentials for the HTTP layer while keeping cryptographic finality for writes — a compromised API key cannot drain a vault, because the private key that signs the EIP-712 authorisation never leaves your infrastructure.
Retail user logins live on a separate surface. If you’re building a web/mobile experience where end users sign in with their own wallet, that flow (Sign-In With Ethereum → short-lived JWT) happens on app.predictstreet.io, not on this API. Partner integrations do not need — and should not implement — SIWE.
One key, many wallets. Trading firms with N sub-accounts, copy-trading platforms, and custodial brokers can request a multi_wallet partner kind — one API key fans out across many end-user wallets, with the actor declared on each request via X-User-Wallet. See Partner kinds for the contract.

​
Flow at a glance

​
Base URL

EnvironmentBase URL
Testnethttps://core.api.dev.predictstreet.sde.adifoundation.ai
StagingAvailable on request
MainnetIssued on partner onboarding
Retail user traffic (app.predictstreet.io) 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.