Technical Analyst
tradermonty/claude-trading-skills
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta…
Install Alpaca Broker Funding Transfers
$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alpacahq/alpaca-skills alpaca-broker-funding-transfers --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/broker-api/funding-transfers .claude/skills/alpaca-broker-funding-transfers && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "alpaca-broker-funding-transfers" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/funding-transfers into .claude/skills/alpaca-broker-funding-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-funding-transfers", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/funding-transfersType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alpacahq/alpaca-skills alpaca-broker-funding-transfers --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/broker-api/funding-transfers .agents/skills/alpaca-broker-funding-transfers && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "alpaca-broker-funding-transfers" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/funding-transfers into .agents/skills/alpaca-broker-funding-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-funding-transfers", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alpacahq/alpaca-skills alpaca-broker-funding-transfers --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/broker-api/funding-transfers .cursor/skills/alpaca-broker-funding-transfers && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "alpaca-broker-funding-transfers" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/funding-transfers into .cursor/skills/alpaca-broker-funding-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-funding-transfers", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alpacahq/alpaca-skills.git --path skills/broker-api/funding-transfers--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alpacahq/alpaca-skills alpaca-broker-funding-transfers --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/broker-api/funding-transfers .gemini/skills/alpaca-broker-funding-transfers && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "alpaca-broker-funding-transfers" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/funding-transfers into .gemini/skills/alpaca-broker-funding-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-funding-transfers", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alpacahq/alpaca-skills alpaca-broker-funding-transfersInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/broker-api/funding-transfers .github/skills/alpaca-broker-funding-transfers && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "alpaca-broker-funding-transfers" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/funding-transfers into .github/skills/alpaca-broker-funding-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-funding-transfers", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alpacahq/alpaca-skills alpaca-broker-funding-transfers --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpacahq/alpaca-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/broker-api/funding-transfers .opencode/skills/alpaca-broker-funding-transfers && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "alpaca-broker-funding-transfers" agent skill from https://github.com/alpacahq/alpaca-skills/tree/main/skills/broker-api/funding-transfers into .opencode/skills/alpaca-broker-funding-transfers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "alpaca-broker-funding-transfers", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
alpaca-broker-funding-transfers- GitHub stars
- 154
- Token cost
- ~2.4k tokens
- SKILL.md length
- 899 words
- Files
- 2
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta…
- Works in 8 steps: The funding model → Endpoints → Create-transfer request (POST… → …
- Building deposit/withdrawal flows
- SKILL.md covers Reference, 1. The funding model, 2. Endpoints and 3. Create-transfer request…, plus 5 more sections
- Reaches docs.alpaca.markets
What it does
Alpaca Broker Funding Transfers is an agent skill from alpacahq/alpaca-skills. Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta funding wallet (international/instant), transfer status lifecycles, and fees. Use when building deposit/withdrawal flows or connecting external bank accounts on Alpaca in any language. For moving cash/shares BETWEEN accounts inside your own omnibus, use journals instead.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It sits in Business, Finance & HR. The repository describes itself as: Agent skills for Alpaca's Trading API and Broker API: drop-in SKILL.md files for AI coding assistants. The licence is Apache-2.0.
When your agent uses it
- Building deposit/withdrawal flows
- Connecting external bank accounts on Alpaca in any language
Example prompts
- “/alpaca-broker-funding-transfers”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 39111ab. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.alpaca.markets
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Alpaca Broker Funding Transfers loads about 2.4k tokens when it runs. Until then it costs about 124 tokens; SKILL.md has 899 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from alpacahq/alpaca-skills at commit 39111ab, republished under its Apache-2.0 licence (© alpacahq). 899 words, ~2,354 tokens.
Download SKILL.mdSave it as
.claude/skills/alpaca-broker-funding-transfers/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- alpaca-broker-funding-transfers
- description
- Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta funding wallet (international/instant), transfer status lifecycles, and fees. Use when building deposit/withdrawal flows or connecting external bank accounts on Alpaca in any language. For moving cash/shares BETWEEN accounts inside your own omnibus, use journals instead.
Alpaca Broker API — Funding & Transfers
Getting cash into and out of end-user accounts. There are three rails, and the model splits cleanly into bank links (persistent) and transfers (the actual money movement).
Read
alpaca-broker-integrationfirst. Broker API + HTTP Basic auth. For moving cash between accounts in your omnibus (vs. to/from the outside world), seealpaca-broker-journals— that's a different mechanism.
Reference
- Guide:
https://docs.alpaca.markets/docs/funding-accounts - API ref:
https://docs.alpaca.markets/reference/createtransferforaccount - Live schema:
alpaca-docsMCP →get-endpointtitle"Broker API"path/v1/accounts/{account_id}/transfers
1. The funding model
External bank ──(relationship: a persistent link)──┐
├──> Transfer (the money movement) ──> Account cash
ACH relationship (rail A: ACH, US domestic) │
Bank relationship (rail B: wire, domestic + intl) │
Funding wallet (rail C: v1beta, multi-currency) ┘- A relationship links an external bank. It moves no money and has its own status; for wires it must be
APPROVEDbefore a transfer can progress. - A transfer references a relationship by ID and moves the money. One relationship backs many transfers.
| Rail | transfer_type | Directions | Relationship | Notes |
|---|---|---|---|---|
| ACH | ach | INCOMING + OUTGOING | ACH relationship (relationship_id) | US domestic; set up via Plaid processor_token (recommended) |
| Wire | wire | OUTGOING only | Bank relationship (bank_id) | Domestic + international (SWIFT). Incoming wires are pushed by the sending bank and booked automatically |
| Funding wallet | (separate /v1beta API) | incoming / outgoing (lowercase) | Funding-wallet recipient bank | Multi-currency, swift_wire/local_rails |
2. Endpoints
| Method | Path | Purpose |
|---|---|---|
| POST/GET/DELETE | /v1/accounts/{id}/ach_relationships[/{rel_id}] | Manage ACH bank links |
| POST/GET/DELETE | /v1/accounts/{id}/recipient_banks[/{bank_id}] | Manage wire recipient banks |
| POST | /v1/accounts/{id}/transfers | Create transfer (ACH deposit/withdraw, or wire withdraw) |
| GET | /v1/accounts/{id}/transfers | List transfers |
| DELETE | /v1/accounts/{id}/transfers/{transfer_id} | Request cancel |
| POST/GET | /v1beta/accounts/{id}/funding_wallet | Create / get funding wallet |
| POST/GET/DELETE | /v1beta/accounts/{id}/funding_wallet/recipient_bank | Funding-wallet recipient bank |
| POST | /v1beta/accounts/{id}/funding_wallet/withdrawal | Funding-wallet withdrawal |
| GET | /v1beta/accounts/{id}/funding_wallet/transfers[/{transfer_id}] | List / get wallet transfers |
| GET | /v2/events/funding/status | SSE — unified funding status stream (see §6) |
The current wire-bank endpoint is
/recipient_banks(schemaBank/CreateBankRequest). The older/banksname is a legacy alias.
3. Create-transfer request (POST /v1/accounts/{id}/transfers)
Required for all: transfer_type, amount (decimal string, > 0), direction.
// ACH deposit
{ "transfer_type": "ach", "relationship_id": "<uuid>", "amount": "100.00", "direction": "INCOMING" }
// Wire withdrawal
{ "transfer_type": "wire", "bank_id": "<uuid>", "amount": "500.00", "direction": "OUTGOING",
"fee_payment_method": "user", "additional_information": "..." }relationship_idrequired iffach;bank_idrequired iffwire(and must be the other one's empty).fee_payment_method(wire):user(fee deducted fromamount; warn the user in UI) orinvoice(firm billed monthly). Only outgoing wire fees auto-process.additional_informationis wire-only — sending it on a non-wire request returns422.- The
Transferresponse addsid,status,fee,requested_amount(original ask),reason, timestamps.
4. Wire recipient bank (POST /v1/accounts/{id}/recipient_banks)
Required: name, bank_code, bank_code_type, account_number.
bank_code_type:ABA(9-digit routing, domestic) orBIC(SWIFT, international).- When
BIC:country,city,state_province,postal_code,street_addressbecome required. extra_fieldscarries intermediary/correspondent BICs (intermediary_bank1_bic…). Omitting them on international wires can cause auto-selection, delays, or extra fees — gather them up front for cross-border.- A new bank starts
QUEUED; it must reachAPPROVEDbefore a wire transfer against it progresses.
5. Transfer status state machines
Classic transfers (TransferStatus):
QUEUED → APPROVAL_PENDING → PENDING → SENT_TO_CLEARING → (APPROVED) → COMPLETE, with REJECTED / CANCELED / RETURNED as failure exits.
| Terminal | Meaning |
|---|---|
COMPLETE | Settled |
REJECTED | Rejected |
CANCELED | Client-initiated cancel |
RETURNED | Bank issued an ACH return |
(The SSE Transfer entity also reports EXPIRED, which is effectively terminal.)
Funding-wallet transfers (FundingWalletTransferStatus): PENDING, EXECUTED, COMPLETE, CANCELED, FAILED (last three terminal). Note lowercase incoming/outgoing directions here — different casing from classic transfers.
Show full SKILL.md (434 more words)Show less
6. Events vs polling — the key reliability lesson
Classic transfers HAVE an SSE stream: GET /v2/events/funding/status. It is unified across four entity_type values — Transfer, BankRelationship, WireBank, FundingWallet — and is replayable via since/until (timestamps) or since_id/until_id (ULIDs). Use it instead of polling for classic ACH/wire status.
Funding-wallet per-transfer status appears NOT to be pushed — only wallet-level status (active/pending) is in the stream. Individual wallet transfer status (PENDING→EXECUTED→COMPLETE) must be polled via GET /v1beta/.../funding_wallet/transfers/{id}.
Lesson (hard-won): rails differ in event coverage. Decide per rail whether you consume SSE or poll, and build a status-reconciliation poller for anything not covered by events (and as a safety net even for those that are — SSE can drop). Map each Alpaca status to your own internal status with an explicit lookup table, and only poll transfers still in a non-terminal state. See alpaca-broker-reconciliation-idempotency.
Legacy caveat: the older
us/sse-events"Transfer Events" payload uses an integerevent_idand lowercase statuses; the modern/v2/events/funding/statususes ULIDs. Migrate to v2.
7. Documented gotchas
- Wire fees (since 2022-06-01): outgoing domestic + international wires are charged. Reflect
requested_amountvsamount+feein your UI. - Incoming wires need an FFC (For Further Credit) instruction to auto-book; otherwise they're handled manually.
- Travel Rule: Alpaca requires transmitter/originator info on all incoming deposits regardless of amount (below the usual FinCEN $3,000 threshold). Pass it at settlement creation; retained ≥5 years.
- ACH uses Plaid: pass the bank via
processor_token. There's aninstantflag on the relationship. Account types limited toCHECKING/SAVINGS. timing: immediateis deprecated and silently ignored (sunset 2026-08-26) — stop sending it.- Permission errors:
403if the account'sdepositable_status/withdrawable_statusisn't allowed;422for incoming-wire attempts, missing/mismatched relationship vs bank IDs, or amounts under the (undocumented) minimums. - Sandbox wire behavior: simulated end-to-end but asynchronous and auto-completes on weekdays only — weekend submissions don't progress until Monday. (ACH in sandbox settles instantly.)
8. The omnibus / sweep-account pattern (architecture lesson)
Many production brokers don't fund each user account by a separate external transfer. Instead:
- Users pay you through your payment processor (or you receive a bulk wire into a firm/sweep account held at Alpaca).
- You then journal cash from the firm account to the user's account instantly (
JNLC) — no external ACH/wire per user. Seealpaca-broker-journals. - Withdrawals reverse it: journal from user → firm account, then send one external transfer out.
This decouples your funding UX from Alpaca's transfer rails and enables "instant" deposits. It requires Alpaca review (and possibly a local money-transmitter license) — confirm with counsel. The classic transfer endpoints in this skill then handle only the firm-account-to-outside-world leg.
Related skills: internal cash movement → alpaca-broker-journals; missed-status recovery → alpaca-broker-reconciliation-idempotency; money formatting → alpaca-broker-money-precision; live status → alpaca-broker-sse-events.
© alpacahq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/broker-api/funding-transfers of alpacahq/alpaca-skills.
- SKILL.md
- reference.md
Open the folder on GitHubat commit 39111ab
Compare with similar skills
Alpaca Broker Funding Transfers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Alpaca Broker Funding Transfers this skillalpacahq/alpaca-skills | 154 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Technical Analysttradermonty/claude-trading-skills | 3k | 4 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Theme Detectortradermonty/claude-trading-skills | 3k | 2 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Creating Financial ModelsChen-zexi/open-ptc-agent | 729 | 3 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Stock APIzhangxiangliang/stock-api | 2k | — | ~507 | Automated safety check: Pass | MIT | |
| Itr Walakaranb192/itr-wala | 871 | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Theme Detector
tradermonty/claude-trading-skills
Detect and analyze trending market themes across sectors. An agent skill from tradermonty/claude-trading-skills.
Creating Financial Models
Chen-zexi/open-ptc-agent
This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions
Stock API
zhangxiangliang/stock-api
Fetch real-time stock quotes, K-line (candlestick) history, and search symbols for China A-shares, Hong Kong, and US markets.
Itr Wala
karanb192/itr-wala
File Indian income tax returns (ITR) for FY 2025-26 / AY 2026-27.
Tushare Data
zillionare/zillionare
面向中文自然语言的 Tushare 数据研究技能。用于把“看看这只股票最近怎么样”“帮我查财报趋势”“最近哪个板块最强”“北向资金在买什么”“给我导出一份行情数据”这类请求，转成可执行的数据获取、清洗、对比、筛选、导出与简要分析流程。适用于 A 股、指数、ETF/基金、财务、估值、资金流、公告新闻、板块概念与宏观数据等研究场景。
More from alpacahq/alpaca-skills
All 14 skills in this repoAlpaca Broker Account Onboarding
alpacahq/alpaca-skills
Open and manage brokerage accounts via the Alpaca Broker API — account creation, KYC/CIP, identity & disclosures, agreements, document upload (incl.
Alpaca Broker Integration
alpacahq/alpaca-skills
Entry point for integrating with the Alpaca Broker API (plus Market Data and Trading APIs) in any programming language.
Alpaca Broker Journals
alpacahq/alpaca-skills
Move cash (JNLC) and securities (JNLS) BETWEEN accounts inside your own Alpaca omnibus via the Broker API — single, batch, and reverse-batch journals, the Idempotency-Key header, journal status…
Alpaca Broker Money Precision
alpacahq/alpaca-skills
Handle money and numeric precision correctly with the Alpaca API — numbers-as-strings on the wire, decimals vs floats, rounding/truncation before sending amounts, fractional-share precision, and…
Alpaca Broker Rate Limits Resilience
alpacahq/alpaca-skills
Make Alpaca API clients resilient — rate-limit header handling, HTTP 429 backoff, exponential retry, bounded concurrency/worker pools, pagination loops, batch sizing, and timeouts.
Alpaca Broker Reconciliation Idempotency
alpacahq/alpaca-skills
Keep local state correct against the Alpaca Broker API — idempotency keys, ID-keyed upserts, event snapshotting and dedup, polling rails that have no events, nightly reconciliation/heal jobs, status…
Related
Categories
Questions about Alpaca Broker Funding Transfers
What does Alpaca Broker Funding Transfers do?
Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta…. Alpaca Broker Funding Transfers is an agent skill from alpacahq/alpaca-skills. Move money between an Alpaca brokerage account and the EXTERNAL banking world via the Broker API — ACH relationships, wire recipient banks, classic transfers (deposits/withdrawals), the v1beta funding wallet (international/instant), transfer status lifecycles, and fees.
When should I use Alpaca Broker Funding Transfers?
Alpaca Broker Funding Transfers fits situations like: building deposit/withdrawal flows; connecting external bank accounts on Alpaca in any language.
How do I install Alpaca Broker Funding Transfers in Claude Code?
Run `npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a claude-code`. Or copy the skill folder (skills/broker-api/funding-transfers in alpacahq/alpaca-skills) into .claude/skills/alpaca-broker-funding-transfers in your project. Claude Code loads it when a task matches its description.
How do I install Alpaca Broker Funding Transfers in Codex?
Run `npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a codex`. Or copy the skill folder (skills/broker-api/funding-transfers in alpacahq/alpaca-skills) into .agents/skills/alpaca-broker-funding-transfers in your project. Codex loads it when a task matches its description.
Can I use Alpaca Broker Funding Transfers in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alpacahq/alpaca-skills --skill alpaca-broker-funding-transfers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/alpaca-broker-funding-transfers, .gemini/skills/alpaca-broker-funding-transfers, .github/skills/alpaca-broker-funding-transfers and .opencode/skills/alpaca-broker-funding-transfers in your project.
What does Alpaca Broker Funding Transfers need to run?
SKILL.md names no scripts, command-line tools or credentials: Alpaca Broker Funding Transfers is instructions for the agent only.
Does Alpaca Broker Funding Transfers access the network?
SKILL.md names 1 domain. In commands or code: docs.alpaca.markets; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Alpaca Broker Funding Transfers safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Alpaca Broker Funding Transfers use?
Alpaca Broker Funding Transfers is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Alpaca Broker Funding Transfers use?
About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Alpaca Broker Funding Transfers?
Skills that share tags, products or a category with Alpaca Broker Funding Transfers: Technical Analyst (tradermonty/claude-trading-skills, 3k stars), Theme Detector (tradermonty/claude-trading-skills, 3k stars), Creating Financial Models (Chen-zexi/open-ptc-agent, 729 stars) and Stock API (zhangxiangliang/stock-api, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Alpaca Broker Funding Transfers?
alpacahq (a GitHub organization) maintains it in alpacahq/alpaca-skills, which has 154 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 8, 2026.
Source: alpacahq/alpaca-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.