# Agentic Trading
> Source: https://useagentos.dev/docs/core/features/agentic-trading

AgentOS treats trading as a first-class capability. Market research, portfolio
analysis, and order execution reach the agent through partner-authorized
connections and skills that ship with the product, so you do not have to wire up
an unofficial API or paste credentials into a chat window.

Three mechanisms provide it:

- **MCP connections** — a featured Robinhood Trading preset in the Web UI, and
  any other MCP server you choose to add.
- **Bundled skills** — trading, research, and liquidity skills installed with
  AgentOS and loaded only when a task needs them.
- **Partner skills** — Bankr and Capminal skills you install in one click from
  the Community hub.

Both run behind the same approval and sandbox layers as every other tool.

> Agentic trading involves significant risk. Review a connection's access and
> action permissions before authorizing it, and read
> [Approvals and Permissions](https://useagentos.dev/docs/core/approvals-and-permissions) before
> letting any automation place orders.

## Robinhood Trading MCP

The Web UI ships a featured preset for Robinhood Agentic Trading.

| Setting | Value |
| --- | --- |
| Endpoint | `https://agent.robinhood.com/mcp/trading` |
| Transport | Streamable HTTP |
| Authorization | Provider-hosted OAuth flow |

Open **Settings › MCP**, select the Robinhood Trading preset, and save
it. Saving opens the provider authorization flow and loads the server's tools
without a gateway restart.

For scripted deployments, declare the same server in TOML:

```toml
[mcp]
enabled = true
connect_timeout_seconds = 10

[[mcp.servers]]
name = "robinhood-trading"
transport = "streamable_http"
url = "https://agent.robinhood.com/mcp/trading"
oauth = true
tool_timeout_seconds = 30
```

See [Configuration](https://useagentos.dev/docs/core/configuration) for the full MCP configuration
reference and [Web UI](https://useagentos.dev/docs/core/web-ui) for the connection UI.

### Account scope

Robinhood's own documentation defines the product scope; the live authenticated
MCP schemas are authoritative for tool names, parameters, supported order types,
and available asset classes.

- The connected agent can **read** all Robinhood accounts, including account
  numbers, positions, balances, transaction and order history, watchlists, and
  scans.
- Trade **placement** is restricted to the dedicated Robinhood Agentic account,
  even though read access is broader.

### How the agent is expected to behave

The bundled `robinhood-agentic-trading` skill encodes the operating rules:

1. Confirm the connected server is the intended Robinhood Trading endpoint.
2. Complete the provider-hosted authentication flow. Never ask for OAuth codes,
   access tokens, account numbers, or credentials in chat.
3. Discover the current tools and read their complete input schemas before
   planning calls. Never invent a tool name, parameter, enum value, order type,
   or asset class.
4. Re-discover tools after reconnecting, or when a schema error indicates that
   capabilities changed.
5. If the connection, authentication, or a required tool is unavailable, stop
   and explain the gap rather than substituting an unofficial API.

## Bundled trading and research skills

These install with AgentOS and load on demand. Skills marked
`risk: high` declare `signing` capability. The ones that sign with a hot-wallet
key of their own (`senior-unilp-manager`, `poolsdotfun-token-launcher`,
`gmgn-swap`, `gmgn-cooking`) never see that key in the agent's shell; AgentOS
passes it to a single direct run of the skill's entry point, and asks you to
approve any run that moves funds — see [Safety model](#safety-model).

| Skill | What it does |
| --- | --- |
| `robinhood-agentic-trading` | Account and portfolio analysis, market research, order preview, placement, cancellation, rebalancing, and bounded automation over the Trading MCP. |
| `robinhood-rwa-addresses` | Resolves a company name or ticker to its Robinhood tokenized-asset token on Robinhood Chain (`4663`) — symbol, contract address, chain id, decimals. Public data source, no key. |
| `gmgn-swap` | Buy and sell tokens on Solana, BSC, Base, and Ethereum: single swap, multi-wallet batch, limit orders, stop loss, take profit, and trailing variants. |
| `gmgn-market` | Price charts (K-line, OHLCV), trending rankings by volume, new launchpad listings, and hot-search rankings. |
| `gmgn-token` | Per-token research: price, market cap, liquidity, holders, top Smart Money and KOL positions, security audit, and social links. |
| `gmgn-portfolio` | Wallet analysis: holdings, realized and unrealized P&L, win rate, history, and developer-wallet token history. |
| `gmgn-track` | Real-time buy and sell activity from Smart Money wallets, KOL wallets, and wallets you follow. |
| `gmgn-holder-analysis` | Holder-structure analysis: chip distribution, entry cost, whale and dev behavior, and risk wallets. |
| `gmgn-wallet-analysis` | Copy-trade dossier on one wallet: four pass/fail gates (authenticity, currency, reachability, survivability), what it holds and buys now, copy window, and a size cap. |
| `gmgn-wallet-score` | Wallet scoring across three angles: track record, copy-tradeability (with a latency/slippage/gas backtest), and developer reputation for token-launcher wallets. |
| `gmgn-cooking` | Token creation and launchpad launches, and launchpad creation statistics. |
| `senior-unilp-manager` | Uniswap V4 liquidity on Base (`8453`) and Robinhood Chain (`4663`): inspect pools and positions, then mint, increase, decrease, collect fees, or burn. |

The GMGN skills require a `gmgn-cli` install plus `GMGN_API_KEY` and
`GMGN_PRIVATE_KEY`. The signing key authorizes orders — treat it as a
credential. See [Skills](https://useagentos.dev/docs/core/features/skills) for how skill requirements and secrets
are declared and surfaced.

## Partner trading skills from the Community hub

These do not ship in the wheel. They are published by partners on the
allowlist below and install in one click from **Skills > Community** (or with
`agentos skills install <name>`). Because their publisher id arrives from the
catalog row rather than from the skill text, they keep their brand on the card
while a look-alike dropped on disk does not — see
[Safety model](#safety-model).

| Skill | Publisher | What it does |
| --- | --- | --- |
| `bankr` | Bankr | Natural-language crypto trading, tokenized stocks and ETFs (spot or leveraged), portfolio balances with P&L, transfers, token deploys, and automated trading across Base, Ethereum, Polygon, Solana, Unichain, Arbitrum, BNB Chain, and Robinhood Chain. Also fronts the Bankr LLM gateway. |
| `aero-stock-lp` | Bankr | Range-LP Coinbase tokenized equities (NVDA, AAPL, GOOGL, META) and AERO/USDC on Aerodrome Slipstream (Base): open, recenter, and exit concentrated-liquidity positions, check pool status, NAV, and yields, and get a portfolio pass with P&L and projected APR. Routes each position to the higher-yielding side — staked for AERO emissions vs unstaked for trading fees — at entry and on every manage pass. Writes go through the Bankr arbitrary-transaction flow. |
| `capminal` | Capminal | Cap Wallet operations: deploy tokens via Clanker, Liquid, or Virtuals, claim rewards, manage limit, stop-loss, TWAP, and DCA orders, bridge between Base and Robinhood Chain, and discover x402 APIs. |

Each publisher carries further skills in the same catalog; browse the Community
tab to see the current list.

`bankr` needs the `@bankr/cli` install and a Bankr login; `aero-stock-lp` runs
on top of that same Bankr wallet, funded with USDC on Base; `capminal` needs
`CAP_API_KEY`. All three authorize spending — treat them as credentials and read
[Skills](https://useagentos.dev/docs/core/features/skills) for how requirements are surfaced before an install.

## Local by default

AgentOS runs on your own machine. For trading, that changes three things.

**Credentials stay on the device.** MCP authorization tokens are written to a
`0700` directory on POSIX systems; Windows uses the current user's
state-directory ACL. The GMGN request-signing key (`GMGN_PRIVATE_KEY`) and the
Uniswap LP signing key (`UNIV4_LP_PRIVATE_KEY`) are local environment values.
Nothing is escrowed with a hosted service, and the agent never asks you to paste
a credential into chat.

**The routing decision never leaves the machine.** The Pilot Router classifies
each turn on-device, so a strategy prompt is not shipped to a third party merely
to decide which model should handle it. Only the turn that actually runs reaches
your chosen model provider. See
[Pilot Router](https://useagentos.dev/docs/core/features/pilot-router) for the classifier and its
alternatives.

**Always-on work runs on hardware you already have.** Scheduled and recurring
trading tasks execute through the local gateway rather than a rented agent
cloud — see [Scheduling](https://useagentos.dev/docs/core/scheduling). Combined with router-driven
model selection, running an agent continuously stays inexpensive.

What still leaves the machine is exactly what has to: the broker or exchange API
calls themselves, and the model turns you route to a remote provider.

## Safety model

Trading skills are held to a stricter standard than ordinary tools.

- **Operator approval for every skill write that moves funds.** The skill
  hot-wallet keys — `UNIV4_LP_PRIVATE_KEY`, `POOLSFUN_PRIVATE_KEY`,
  `GMGN_PRIVATE_KEY` — are held back from every process the agent can drive
  (its shell, `execute_code`, cron scripts, MCP servers, coding agents). AgentOS
  hands one only to a direct invocation of that skill's own entry point, runs
  its packaged copy itself without a shell, and for a `--broadcast`, a ratchet
  `arm --confirm`, or a GMGN `swap` / `multi-swap` / `order strategy create|cancel`
  / `cooking create` first asks you to approve that exact command. `/elevated`,
  `bypass` and auto-approve do not answer that prompt. The unattended
  `ratchet.py tick --broadcast` gets the key without asking, but fires only
  mandates whose `arm` you approved, with the bounds you approved, and always
  pays the signing wallet itself. Keep these keys in **Settings > Skills**: a
  key in a file the agent's shell can read (`~/.config/gmgn/.env`) is outside
  this custody.
- **Explicit confirmation.** Skills tagged `[FINANCIAL EXECUTION]` do not act on
  an inferred intent; they show the user the specific action first. That is the
  model's instruction; the approval above is what enforces it.
- **Dry run by default.** `senior-unilp-manager` splits reads from writes. Its
  read script cannot sign at all, and a write is a dry run unless it is given
  both `--broadcast` and the plan hash printed by that same dry run. The plan
  hash binds the broadcast to the plan that was shown; it is not an approval —
  the agent can read it back — which is why the broadcast also waits for yours.
- **Pinned GMGN CLI.** The `gmgn-*` skills install `gmgn-cli@1.7.1`, and AgentOS
  refuses to hand `GMGN_PRIVATE_KEY` to any other installed version. That CLI has
  no confirmation prompt of its own; the approval above is the gate.
- **Schema truth.** The agent plans against the live authenticated schemas of
  the connected server, not remembered API shapes.
- **Publisher verification.** A skill cannot mint its own brand. Only bundled
  skills that ship inside the wheel may name a publisher, and the displayed
  name, URL, and logo always come from an internal allowlist — currently
  Robinhood, Bankr, and Capminal. Every other skill takes its brand from the
  catalog row that installed it, so a look-alike dropped on disk renders as an
  ordinary unbranded skill.
- **Standard approvals.** Everything above sits on top of the normal permission
  and sandbox layers described in
  [Approvals and Permissions](https://useagentos.dev/docs/core/approvals-and-permissions) and
  [Tools, Approvals, and Sandbox](https://useagentos.dev/docs/core/tools-and-sandbox).

## Related

- [Web UI](https://useagentos.dev/docs/core/web-ui) - connecting and authorizing MCP servers.
- [Configuration](https://useagentos.dev/docs/core/configuration) - MCP and skill configuration.
- [Skills](https://useagentos.dev/docs/core/features/skills) - skill discovery, install, and authoring.
- [Approvals and Permissions](https://useagentos.dev/docs/core/approvals-and-permissions) -
  permission tiers and approval prompts.
