trade-it

Trade It OpenClaw Skill

Use Trade It in OpenClaw to connect brokerages, inspect accounts and holdings, and place trades on supported brokerage accounts: Robinhood, ETrade, Charles Schwab, Webull, Public, Tastytrade, Coinbase, and Kraken.

This repo contains a publishable OpenClaw skill that teaches agents how to use the Trade It API safely and consistently.

What this is and what users can do with it

This project packages Trade It as an OpenClaw skill. With the right Trade It credentials, agents can help users:

• link brokerage accounts through secure OAuth flows
• inspect linked brokerage accounts, holdings, and trade history
• create stock and options trades
• execute trades on supported brokerages after explicit confirmation when appropriate
• generate hosted Trade It connect or trade URLs for browser handoff

The skill includes:

• a SKILL.md file that tells OpenClaw when and how to use Trade It
• a bundled Python helper for calling the API
• reference docs for endpoints, enums, examples, integration patterns, and security posture

Why this exists

Trade It gives OpenClaw agents a single brokerage integration layer, so teams can support real brokerage actions without building broker-specific flows one by one.

Trust, security, and user control

Trading access is sensitive. This skill is designed to be clear about that.

Key points:

• Trade It encrypts data at rest and in transit.
• Trade It stores revocable access tokens rather than usernames and passwords.
• Trade It users can revoke access directly from their brokerage or on https://tradeit.app.
• Trade It can place trades on a user's behalf, but cannot withdraw, transfer, or custody assets.
• This skill is written to prefer explicit confirmation before execution.
• Some accounts may allow immediate placement on create if the user has enabled that setting.

Read more:

• Trade It site: https://tradeit.app
• Security: https://tradeit.app/security
• Privacy Policy: https://tradeit.app/privacy-policy
• Terms of Service: https://tradeit.app/terms-of-service
• Contact: https://tradeit.app/contact

Important disclaimers

• All investing involves risk, including the possible loss of principal.
• This skill is an integration layer, not investment advice.
• Users remain responsible for reviewing brokerage connections, orders, account choices, and trade details.
• AI outputs can be wrong. Orders and trade flows should be reviewed carefully.
• Third-party brokerages have their own terms, availability, fees, and execution behavior.

How authentication works

This skill always sends:

Authorization: Bearer <TRADEIT_ACCESS_TOKEN>

TRADEIT_ACCESS_TOKEN is required and should be a bearer token value.

Token sources:

• API key token from your Trade It account (direct API access)
• OAuth access token from a partner integration flow

If you use API keys, generate them here:

• https://tradeit.app/account/api-keys

For endpoint-level auth examples, see tradeit-api/references/api-reference.md.

How the skill behaves

The skill is written around two main patterns:

1. API-native trading flow

Gather info and place trade orders entirely in-chat.

2. Hosted browser handoff

A more visual experience. Trade It generates session URLs so you can connect brokerages or review, edit, and place trades in the browser.

Drafts and execution

The default and recommended trading flow is:

1. create a trade
2. inspect returned status
3. if still draft, ask for confirmation
4. execute if confirmed

If users enable immediate placement in Trade It settings, create calls may submit orders without a second execution step.

When enabled, a create_trade or create_options_trade call may place the trade immediately, skipping the separate execution step.

That means this skill does not blindly assume every create call is draft-only. It checks status first.

Canonical happy path

Use this sequence as the default agent behavior:

1. fetch user/account context (get-user, get-accounts)
2. create trade (create-trade or create-options-trade)
3. inspect returned status
4. if status is draft, ask for explicit confirmation before execute-trade
5. if status is already placed, report immediate placement and do not execute again

Repo contents

tradeit-api/
├── SKILL.md
├── scripts/
│   └── tradeit_api.py
└── references/
    ├── api-reference.md
    ├── enums.md
    ├── examples.md
    ├── integration-patterns.md
    └── security.md

References included in the skill

• api-reference.md — JSON-first API request/response shapes
• enums.md — brokerage ids, order types, time-in-force values, statuses, and other constants
• examples.md — concrete integration and conversation examples
• integration-patterns.md — recommended architecture and workflow guidance
• security.md — public Trade It security posture summary with disclaimer language

Installing / using

If you want to publish or distribute the packaged skill, use:

• tradeit-api.skill

If you want to edit the source, use the folder:

• tradeit-api/

Typical OpenClaw usage expects the skill to be installed into a skills directory and supplied with the needed environment variables for the agent run.

Who should use this

This is for:

• OpenClaw users who want brokerage-backed trading flows
• developers building AI trading assistants or chatbot workflows
• products that want a unified brokerage layer instead of brokerage-by-brokerage integrations

Links

• Docs: https://docs.tradeit.app
• FAQ: https://tradeit.app/faq
• Security: https://tradeit.app/security
• Privacy Policy: https://tradeit.app/privacy-policy
• Terms of Service: https://tradeit.app/terms-of-service
• Contact: https://tradeit.app/contact
• Website: https://tradeit.app

License

See LICENSE in this repository.