> For the complete documentation index, see [llms.txt](https://archer-bot.gitbook.io/archer.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archer-bot.gitbook.io/archer.bot/readme/web-app.md).

# Web App

The Archer web app at [app.archerprotocol.com](https://app.archerprotocol.com) is the primary surface for the platform. It's a chat-first interface where every Web3 operation (swap, bridge, send, balance check, price lookup, token research) happens through natural language in a single conversation.

## What the Web App Does

* **Conversational execution.** Type what you want; Archer parses, validates, and prepares the transaction. You see a Confirm/Cancel modal with the full plan (route, slippage, gas, fees, expected output) before anything is signed.
* **Multichain by default.** Eight chains supported today (Ethereum, Arbitrum, Base, Polygon, Optimism, Avalanche, BSC, Solana). Archer automatically resolves the right chain from your prompt or your balances.
* **Persistent threads.** Every conversation is saved. Pick up follow-ups, ask "what if I swapped 200 instead?", or revisit a past trade with full context.
* **Portfolio dashboard.** Aggregated balances across all your wallets and chains, with USD values, per-chain breakdowns, and per-wallet attribution.
* **Wallet management.** Embedded EVM and Solana wallets are provisioned automatically on signup via Privy. Connect external wallets (MetaMask, Phantom, Coinbase Wallet, etc.) for portfolio visibility and fund consolidation.
* **Settings.** Risk tolerance, default slippage, gas multiplier, chain preferences, server-side signing toggle.

## Getting Started

1. Go to [app.archerprotocol.com](https://app.archerprotocol.com)
2. Sign in with email, Google, Apple, or wallet
3. Embedded EVM + Solana wallets are created automatically
4. Fund your account ([Fund Your Account](/archer.bot/getting-started/fund-your-account.md))
5. Start prompting

## What Makes the Web App Different

Most Web3 apps put the chain in your face. They make you pick the wallet, figure out the gas funding yourself, network, pick the DEX, pick the bridge, or pick the route. Archer inverts that. You describe the *outcome* and Archer figures out the path. Behind every prompt:

1. **Semantic understanding.** We classify your intent and extract the right parameters.
2. **Tool calls.** The agent fetches a live quote, checks your balance, simulates gas, validates the destination, and runs spam checks against tokens involved.
3. **Plan.** A single human-readable plan is presented for your approval.
4. **Sign.** You approve in your browser (or via server-side signing in a TEE if you've opted in).
5. **Execute.** The transaction is broadcast and confirmed; results land back in the thread.

No private keys ever leave your wallet. The backend ***never*** holds custody.

## Browser Support

The web app is a Progressive Web App (PWA) that runs in any modern browser:

* **Desktop:** Chrome, Safari, Firefox, Edge, Brave, Arc
* **Mobile:** Chrome (Android), Safari (iOS), Firefox, Brave
* **Installable:** Add to home screen on iOS/Android for a native-app feel - see [Mobile App](/archer.bot/readme/mobile-app.md)

## Next

* [Create an Account](/archer.bot/getting-started/create-an-account.md)
* [Manage Your Wallet](/archer.bot/getting-started/manage-your-wallet.md)
* [Swap Tokens](/archer.bot/intents/swap-tokens.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://archer-bot.gitbook.io/archer.bot/readme/web-app.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.