machineODDS AccountACCOUNT · LIVE
Create account.
Add credits.
Start trading.
Create account. Add $mODDS credits. Verify tx hash. Connect venue adapters. Configure agent. Start supervised trading.

No wallet login required. No private keys. No custody. Venue funds stay on venue.
1
Create accountgenerate Account ID + one-time API key
2
Save API keystore securely for SDK, CLI, bot, or agent use
3
Add $mODDS creditssend the EXACT quoted batch amount
4
Choose analyst providermanaged credits or your own provider key
5
Review signalsreview live ranked opportunities
6
Executionsupervised agent settings and risk controls

No wallet login required  ·  No private keys  ·  No custody  ·  Venue funds stay on venue  ·  Supervised execution controls  ·  Providers are interchangeable

Account
Your machineODDS account controls credits, signals, simulations, agent settings, and venue adapter configuration. No wallet login. No private key storage. Venue execution follows account-level supervised risk controls.
Account ID
— not created
Account
API Key
— not generated
Returned once. Store securely.
Restore an existing account on this browser. Paste your Account ID and API key below. These are saved only in this browser.
$mODDS credit balancefetching…
Send the quoted $mODDS amount to the machineODDS receiver wallet, then paste your tx hash and sender wallet to activate credits. No wallet connection required.
IMPORTANT: SEND THE EXACT AMOUNT.
For $mODDS Credit Layer batch activation, send the exact quoted $mODDS amount shown for your selected batch. Do not round up or down. If the amount is different, the system may not recognize the transfer automatically.
Select batch
1 Signal
1 credit
fetching…
10 Signals
10 credits
50 Signals
50 credits
100 Signals
100 credits
How it works
1. Choose batch size above
2. Copy $mODDS amount and receiver wallet
3. Send the EXACT AMOUNT on Base mainnet
4. Paste sender wallet + tx hash
5. Click Verify Credit Transfer
6. Credits activate on confirmation
Account Performance / PnLledger: account-agent trades only
PnL is calculated from exact machineODDS Account agent trades only: account ID, signal, venue order, fill, resolution, and realized PnL. Wallet balances are not used as PnL truth.
Total PnL
$0.00
0 live · 0 resolved
Total Win Rate
0W / 0L
Polymarket
$0.00
0 live · 0 resolved · 0W / 0L · WR —
open exposure $0.00 · fees $0.00
Kalshi
$0.00
0 live · 0 resolved · 0W / 0L · WR —
open exposure $0.00 · fees $0.00
Recent Account-Agent Trades
No account-agent trades yet.
Signalstop 5 live
fetching signals…
Signal Simulation3 credits · informational only
— no signal selected —
Simulation does not change the machineODDS signal score. It does not approve or place trades. Informational only. Cost: 3 credits per simulation (v1).
Agent Setup
Manual
You review each signal and approve trades manually. No automation.
Supervised ✓
Agent selects from signals. You approve before execution. Recommended for v0.
Autonomous
Agent executes within risk limits. Full automation. Requires venue connectors.
Risk limits
Venue Connections
Venue funds stay on venue. machineODDS does not custody trading funds. Provider adapters are interchangeable. Supervised trading before autonomous. Supervised execution controls.
Polymarket
API key status: — not connected
Prediction market · USDC · Polygon
Kalshi
API key status: — not connected
Prediction market · USD · regulated
Bankr route
Adapter: — not configured
Agent wallet adapter · managed execution layer
Direct route
Adapter: — not configured
Direct venue API · operator wallet required
machineODDS Analystprovider: machineODDS managed
Choose analyst provider. machineODDS-managed mode uses our hosted analyst provider stack and will spend machineODDS analyst credits. User-key mode lets power users bring their own Bankr/OpenRouter/Venice/OpenAI/Claude key and pay that provider directly. Signal access and premium market data remain machineODDS-billed.
Commercial mode: machineODDS-managed = machineODDS analyst credits. User API key = customer pays their own provider directly.
Account safety: analyst provider routing is configured at account level, provider routing follows account policy, and venue execution follows supervised account risk controls.
// analyst provider router configured at account level
// free managed uses limited per account
// analyst uses selected account provider route
// no raw provider key returned after save
Activity
Account page opened
now
Account created — pending
Credits verified — pending
Signal viewed — pending
Simulation requested — pending
Agent controls — supervised mode selected
ready
Supervised Order Intents tickets: account-scoped only
Order intents are supervised trade tickets created before any venue adapter submits an order. They do not place trades, do not call venues, and do not write PnL.
Recent Tickets
0
no account loaded
Execution
OFF
supervised intent layer only
Create an account to load supervised order intents.