Skip to main content
Portfobit is an AI-native workspace for crypto CEX portfolios. It connects supported crypto exchanges, normalizes portfolio data, and lets an AI agent analyze balances, positions, value, risk, activity history, and market data.

​
Before you begin

  • You need a Portfobit account.
  • For a CEX connection, use the smallest provider permission set that fits your intended use. Read access is enough for analysis; trading or internal-transfer permission is needed only if you deliberately enable Portfobit’s protected actions. Always disable withdrawals.
  • If the provider supports it, add Portfobit’s service egress IPs to the provider allowlist before connecting the account.
New accounts include a one-calendar-month Plus trial. Review Plans, Features, and Limits for account capacity, synchronization quotas, and Plus/Pro history capabilities.
Portfobit never supports withdrawals, external-address transfers, cross-exchange transfers, or P2P transfers. Trading and same-CEX internal transfers are protected actions that require an explicit scope, user confirmation, a trading OTP, an idempotency key, provider permission, and server-side risk checks.
1

Connect your AI agent

Follow Plugin or MCP Server Setup for your preferred agent or MCP client. Codex and Claude Code show the plugin installation prompt first; the existing manual Remote MCP setup remains available. Sign in to Portfobit in the browser, review the requested OAuth scopes, and approve only the access the agent needs.
2

Connect your first CEX account

Follow Connect Your First Account and let the connected agent create the account connection. Keep provider permissions minimal and leave withdrawals disabled.
3

Verify the first sync

Wait for the automatic on_create sync to complete, then ask the agent to check the account status and retrieve a portfolio summary. See Sync and Data Freshness if the account is not ready yet.
4

Use Portfobit with AI

Continue with Use Portfobit with AI for practical prompts that analyze your portfolio, inspect activity, and safely prepare protected CEX actions.
You do not need a Developer API key for the recommended OAuth path. Create one only for direct Open API access, automation, service accounts, or an MCP client without OAuth support. See Create a Developer API Key.