> 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/reference/roles.md).

# Roles

Archer serves three distinct participants. Each benefits from the others' activity on the platform.

## Users

Users interact with Archer through natural language — via the web interface, MCP server, API, or voice — to execute internet operations without needing to understand the underlying chain mechanics, gas requirements, or protocol interfaces.

**What users do:**

* Type or speak intents like *"swap half my ETH to USDC on the cheapest chain"* or *"bridge 500 USDC from Base to Solana"*
* Review human-readable transaction plans with costs, routes, and safety checks
* Approve transactions via their non-custodial embedded wallet (one-click signing), or enable server-side signing for automatic execution
* Access developer-published strategies from the marketplace (Phase 3)

## Developers / "Vibe Builders"

Developers build, publish, and monetize execution strategies on Archer's marketplace. These can range from simple automation flows to sophisticated multi-step agent workflows.

**What developers do:**

* Build custom strategies and skills using Archer's SDK and tool registry
* Publish them as ranked capabilities on the marketplace
* Earn fees when users or agents execute their strategies
* Stake tokens on published strategies as a quality signal and user-insurance mechanism
* Improve their ranking by optimizing for reliability, latency, and economic efficiency — higher-ranked strategies attract more traffic

See [Marketplace Intents](/archer.bot/intents/marketplace-intents.md) for the marketplace roadmap.

## Agents

Autonomous AI agents are a first-class user type on Archer. Any external agent — whether built with Claude Code, Cursor, a custom framework, or any MCP-compatible client — can access Archer's full execution infrastructure programmatically.

**What agents do:**

* Authenticate via Archer's developer portal
* Call Archer's MCP server or REST API to request onchain operations
* Receive signature callbacks from non-custodial wallets without ever touching a private key
* Discover and execute marketplace strategies on behalf of their end users
* Generate execution telemetry that feeds the platform's ranking algorithm

See the [Quickstart](/archer.bot/for-builders/quickstart.md) and [MCP Server](/archer.bot/for-builders/overview.md) for agent integration.


---

# 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/reference/roles.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.