Platforms
Core ships on four platforms. They share accounts, key management, and the approval pipeline, but expose different integration surfaces — which one your users run determines how your software reaches them.
Core Web — core.app
The wallet as a website: portfolio, trading, staking, DeFi, and the settings that govern the MCP agent policy. No integration API of its own — see Core Web dapp connections for what that means in practice.
Core Extension
The browser extension, and the main dapp target. Injects the EIP-1193 provider, announces via EIP-6963, supports hardware wallets and WalletConnect sessions. Chrome and Chromium-based browsers.
Core Mobile — iOS and Android
Full wallet on the phone. Connects to dapps exclusively through WalletConnect; there is no injected provider in mobile browsers.
The MCP server
Not a user-facing platform, but a fourth surface: the Core MCP Server lets AI agents operate a wallet under a signed policy, authenticated with the user's core.app identity.
Choosing what to build against
| You are building… | Integrate with |
|---|---|
| A web dapp | EIP-6963 detection + WalletConnect, or a library that does both |
| A desktop or non-browser app | WalletConnect |
| An AI agent | The MCP server |
| X/P-Chain tooling | The avalanche_* methods |