CRYPTAI ORACLE
FIRST-RUN SETUP
  1. 1Claim install
  2. 2Email delivery
  3. 3Test email
  4. 4Operator account
  5. 5Verify email
  6. 6Exchange keys
  7. 7Market data
  8. 8Notifications
  9. 9System alerts
  10. 10Review
Claim this install
Enter the claim code from your welcome email (for example WG4GG-CKCYX-GPAFJ-DRQFV) to confirm this install is yours. If you installed without an invitation, enter the setup token the installer printed instead.

Until this is done, anyone who finds this address could complete the setup and take ownership of the install. The token is discarded the moment you create your account.
Lost it? The claim code is in your welcome email. The setup token is on the droplet (DigitalOcean → the droplet → Access → Launch Droplet Console): sudo cat /root/cryptai-oracle-bootstrap-secrets.txt
Email delivery
All confirmations (password resets, credential changes, email verification) are delivered via Resend. DigitalOcean blocks outbound SMTP, so this HTTPS API is the only reliable channel on a DO droplet.

Before you paste: sign up at resend.com, verify a sending subdomain (e.g. send.yourdomain.com), and create an API key with sending access on that domain.
Starts with re_, ~36 chars.
Must be on a Resend-verified domain.
Only used for display — the From address above is what matters.
Test email
Send a test message now and confirm it arrives — that way you know the verification email in the next step will land, too.
Usually your own address.
Create operator account
This is the account you sign in with. It also receives every confirmation email for credential changes. Store the password in a password manager — there's no out-of-band reset.
If you ever lose access to the primary email, password resets can be sent here too.
Verify your email
We sent a verification link to your inbox. Click it and this page will advance automatically.
Waiting for you to click the link…
Link expires in 60 minutes. Check spam if you don't see it.
Exchange API keys
Connect the venues you want to trade on. Both are optional and both can be added later under Settings.
Kraken
Create a new key at Kraken → API. Required permissions: Query Funds, Query Orders, Create & Modify Orders. Skip if you only plan to use Coinbase.
Coinbase
Create a CDP key at Coinbase CDP Portal (the newer Advanced Trade API). Paste the private key including -----BEGIN EC PRIVATE KEY----- headers. Skip if you only plan to use Kraken.
From the CDP portal — full path including organizations/…/apiKeys/….
Paste the full PEM block including the BEGIN/END headers. Newlines matter — if you paste a single-line version it will 401.
Both venues are optional. With neither configured the engine still computes signals; it has nowhere to read balances from or place orders.
Collecting market data
The engine cannot produce a signal until every one of its 21 pairs has converged, which needs about 70 days of hourly prices for all seven assets. This runs once, from public market data — no API keys involved. It usually takes under two minutes.
starting…
Notifications
Where the engine tells you about signals, orders and fills. All of this is editable later under Settings.
Telegram
Message @BotFather to create a bot, then message your new bot once so it can reply to you.
Ask @userinfobot for yours.
SMS is off by default. Twilio approval is slow and often refused, so nothing here blocks your install — you can add it any time.
System alerts
Where the engine reports its own faults — a venue refusing orders, a price feed going quiet, a cycle failing. This is separate from the trading notifications in the previous step.
Pre-filled with the cryptAI Oracle support address so faults reach us without you having to notice and report them. Change it to your own address if you would rather handle them yourself.
What this address receives
Sent: the error message, which part of the engine raised it, the time, and which venue was involved. Plus a periodic digest of unresolved faults.
Never sent: API keys or secrets, account balances, position sizes, order or trade history, prices you traded at, portfolio value, or your account credentials. These are stripped from every report before it leaves this machine — not merely omitted by convention.
Turn this off below and nothing is sent at all.
Goes to your own chat about your own account, so it is not redacted the way the developer email is.
Ready to go
Everything below is checked right now, not remembered from earlier steps.
Trading starts switched off. The engine computes signals and shows each venue's real balances and history; no order is placed until you enable a venue, and the header says TRADING OFF until then. To trade, go to Settings → Exchanges and press Enable on the venue — it asks for your password, and refuses if the engine is not warmed up or the trading strategy file is not production grade.
Back up /root/cryptai-oracle-bootstrap-secrets.txt now. It holds your MASTER_KEY, and every stored credential is unrecoverable without it. To read it: DigitalOcean → the droplet → Access → Launch Droplet Console, then cat /root/cryptai-oracle-bootstrap-secrets.txt, and copy it into your password manager.
Your license and trading strategy are installed. Nothing to send and nothing to activate.
This is your install code. Copy it from here, record it in Section I of your installation worksheet and email it to admin@cryptaioracle.com. Include your License ID in the email subject line. Or simply click here to open a pre-formatted email in your email client. This is a public key and safe to send. Your license and trading strategy file will be encrypted to this key. CryptAI Oracle will send you one more activation file after receiving this key. Log in to your dashboard at this address, and upload the activation file on the page Settings → License. Until the activation file is uploaded the engine runs on placeholder parameters and will not place real orders.