> 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/for-builders/developer-portal.md).

# Developer Portal

The Developer Portal at [app.archerprotocol.com/developer](https://app.archerprotocol.com/developer) is your control center for connecting external tools to Archer Protocol. Create API keys, monitor usage, manage transaction approvals, and track compute unit billing.

## API Keys

API keys authenticate your MCP client or external application with Archer's backend.

### Creating a Key

1. Navigate to the Developer Portal in the Archer webapp
2. Click **Create API Key**
3. Configure:
   * **Name** - a label for your reference (e.g., "Claude Code - local dev")
   * **Scopes** - permissions for this key (read, quote, swap, bridge, send)
   * **Spend Limit** - optional USD cap for transaction operations
   * **Expiry** - optional expiration date
4. Copy the raw key immediately - it is shown only once

The portal displays a **connection snippet** with ready-to-paste config for Claude Code, Cursor, and other clients.

### Key Format

API keys follow the format `arch_xxxx...` where `arch_` is the prefix. The portal shows the prefix for identification but never displays the full key after creation.

### Scopes

| Scope    | Allows                                       |
| -------- | -------------------------------------------- |
| `read`   | Token lookups, price checks, balance queries |
| `quote`  | Swap and bridge quotes (no execution)        |
| `swap`   | Prepare swap transactions                    |
| `bridge` | Prepare bridge transactions                  |
| `send`   | Prepare send/transfer transactions           |

### Revoking a Key

Click **Revoke** on any active key. This is immediate and permanent - the key stops working instantly.

## Transaction Approvals

When an MCP client prepares a transaction (swap, bridge, or send), a **Pending Approval** appears in the Developer Portal.

### Approval Lifecycle

1. **PENDING** - Transaction prepared, waiting for your review
2. **APPROVED** - You signed the transaction; it's been submitted on-chain
3. **REJECTED** - You rejected the transaction
4. **EXPIRED** - Transaction expired before you acted (typically 60-90 seconds for swap quotes)

### Reviewing a Transaction

Each pending approval shows:

* **Tool name** - which operation (swap, bridge, send)
* **Human summary** - plain-English description of what will happen
* **Chain** - which blockchain
* **Wallet address** - which of your wallets will sign
* **Transaction details** - the unsigned transaction data
* **Expiry** - how long before the quote expires

Click **Approve** to sign with your Privy embedded wallet, or **Reject** to cancel.

## Usage Tracking

The Developer Portal tracks all API operations:

* **Total calls** and success rate
* **Calls by tool** - which tools are used most
* **Daily timeline** - usage over time
* **Recent calls** - last operations with latency and error details
* **Per-key metrics** - usage broken down by API key

## Compute Units (CU) Billing

Every operation consumes Compute Units. Your account has a free monthly CU allowance based on your tier:

| Tier         |  Price | Monthly CU |    CU Rate   | TVR Fee |
| ------------ | :----: | :--------: | :----------: | :-----: |
| FREE         |  Free  |    2,500   |  $0.0002/CU  |  0.20%  |
| VIBE BUILDER | $19/mo |   150,000  | $0.000127/CU |  0.15%  |
| PRO          | $79/mo |  1,000,000 | $0.000079/CU |  0.10%  |
| ENTERPRISE   | Custom |   Custom   |  Negotiated  |  Custom |

CU costs include:

* **Infrastructure CU** - base cost per tool call (see [Tools Reference](/archer.bot/for-builders/overview/tools-reference.md#compute-unit-costs))
* **AI CU** - LLM inference costs (varies by model tier: economy, standard, premium)
* **TVR Fee** - percentage of transaction value routed on-chain (swap/bridge/send)

View your current period's usage, remaining balance, and billing history in the Developer Portal.


---

# 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/for-builders/developer-portal.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.