# Overview ## What is Archer? Archer is the execution marketplace for the agent economy. It is a platform where human users and autonomous AI agents can discover, rank, and execute onchain operations through natural language. Today's internet - across both Web2 and Web3 - is a patchwork of siloed services that were never designed to work together. In Web3, users navigate dozens of chains, hundreds of protocols, and hundreds of thousands of tokens - manually managing DEXs, bridges, wallets, and gas mechanics just to execute a single cross-chain operation. In Web2, the fragmentation is just as severe but so normalized we've stopped noticing it: your brokerage can't place a bet on a prediction market. Your bank has no idea how to integrate with your DoorDash subscription without a human-in-the-loop. Your travel agent can't pay for your hotel with the rewards points sitting in a different loyalty program. Your portfolio tracker can't rebalance into a tokenized Treasury without you opening three separate apps, signing into two exchanges, and bridging funds through a fourth. Every boundary between these services requires a human in the loop - copying and pasting, re-authenticating, manually transferring value, querying Google for help, and hoping nothing breaks in between. This is the problem autonomous agents were supposed to solve. But today, every developer building an agent must rebuild wallet integration, payment orchestration, and execution logic from scratch for each service they want to touch. There is no shared execution layer, no common interface, and no quality signal to distinguish a reliable strategy that anyone built from a bad actor. Archer exists to close that gap. ## How It Works Archer's tool-calling agent architecture translates natural language into deterministic onchain operations. Unlike prompt-engineered chatbot wrappers, Archer's agent orchestrates real tool calls - fetching live quotes, validating balances, checking gas feasibility - and produces auditable, unsigned transactions. The backend never holds private keys and never broadcasts transactions. All signing is non-custodial via embedded smart wallets, or via server-side non-custodial signing in a Trusted Execution Environment if you opt in. **Today, Archer supports:** * Multichain token swaps (EVM + Solana) * Cross-chain bridges and cross-chain swaps * Token transfers * Portfolio balance and price queries * Token resolution and spam detection * Live web search and market research * Multi-step transaction planning (swap → bridge → stake in a single flow) ## The Platform Vision **Phase 1 - Command Center (Live):** Natural language to onchain execution for end users across EVM and Solana, via the web app or MCP server. **Phase 2 - Agent Gateway (Building):** An enhanced MCP server and external API that allow any developer's agent to authenticate, request custom onchain operations, and receive a signature callback without ever touching a private key. One integration gives any agent multichain DeFi execution. **Phase 3 - Intent Marketplace (Next):** Developers publish custom strategies (yield optimizers, copy-trade bots, arbitrage agents, automated rebalancers) as ranked capabilities. Every published strategy is scored in real-time by a proprietary ranking algorithm across reliability, latency, economic efficiency, and staked commitment. Any user or agent on the platform can discover and execute them safely and transparently. ## Why Archer Archer is not competing with individual agents or protocols. It is the connective layer that makes them all accessible. As the agent economy scales, Archer's marketplace flywheel strengthens: more developers publish strategies, more executions generate performance telemetry, better rankings surface higher quality, and more users and agents trust the platform. Discovery and execution are fused into a single motion - we don't just index what's possible onchain, we execute it. --- # Agent Instructions: 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: ``` GET https://archer-bot.gitbook.io/archer.bot/readme/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.