BYOB Broker Research — Post-Launch Broker Integration Targets

Status: research-only. This document does NOT constitute legal or tax advice. Before filing or acting, consult a securities attorney licensed in relevant jurisdictions (see securities-attorney-engagement-2026-05-13/ATTORNEY-SHORTLIST.md for pre-vetted contacts) AND a compliance attorney with FINRA/SEC broker-dealer registration experience. Last updated: 2026-05-20 UTC. Sources as of that date — verify freshness before acting. Per feedback_human_to_human_drive: this document should also land in Google Drive for the eventual securities-counsel meeting. Copy to Drive before attorney engagement call.

TL;DR

Raxx ships Alpaca-default only at v1. The post-launch BYOB epic (#495, deferred 2026-05-20 UTC) targets power-users who have existing brokerage relationships. Three brokers — Tradier, tastytrade, and Alpaca (as an explicit BYOB target for users who bring their own Alpaca account) — form the strongest Tier A: all three have public REST APIs, paper trading sandboxes, full equities + options coverage, and FINRA/SIPC membership. The critical unresolved question for any BYOB feature: whether Raxx, by submitting orders to a user-chosen broker on the user's behalf, triggers broker-dealer registration under Exchange Act Section 15(a). A securities attorney must answer this before any BYOB architecture ships to production. The SnapTrade aggregator path is the most compliance-protective architecture because the aggregator relationship with the broker is pre-established — Raxx would be a SnapTrade API consumer, not a broker-facing integration.

1. Candidate Broker Inventory

1.1 Tradier Brokerage

Sources: - https://docs.tradier.com/docs/getting-started - https://docs.tradier.com/docs/trading - https://tradier.com/businesses/fintechs - https://brokercheck.finra.org/firm/104982

1.2 tastytrade

Sources: - https://developer.tastytrade.com/api-overview/ - https://developer.tastytrade.com/sandbox/ - https://tastytrade.com/api/ - https://support.tastytrade.com/support/s/solutions/articles/43000700385

1.3 Alpaca (explicit BYOB target — distinct from v1 default)

Sources: - https://alpaca.markets/broker - https://alpaca.markets/oauth - https://alpaca.markets/blog/alpaca-secures-occ-and-ficc-memberships-to-power-multi-asset-self-clearing-for-partners/

1.4 Interactive Brokers (IBKR)

Sources: - https://www.interactivebrokers.com/campus/ibkr-api-page/oauth-1-0a-extended/ - https://www.interactivebrokers.com/campus/ibkr-api-page/web-api-trading/ - https://www.interactivebrokers.com/campus/ibkr-api-page/getting-started/ - https://interactivebrokers.github.io/tws-api/introduction.html

1.5 Charles Schwab (Trader API)

Sources: - https://developer.schwab.com/ - https://developer.schwab.com/user-guides/apis-and-apps/test-in-sandbox - https://medium.com/@carstensavage/the-unofficial-guide-to-charles-schwabs-trader-apis-14c1f5bc1d57

1.6 Webull

Sources: - https://developer.webull.com/apis/docs/ - https://www.webull.com/open-api

1.7 TradeStation

Sources: - https://developer.tradestation.com/trading-api/ - https://api.tradestation.com/docs/ - https://www.tradestation.com/stocks-etfs-pricing-disclosures/

1.8 Robinhood

Sources: - https://robinhood.com/us/en/support/articles/third-party-connections/ - https://robinhood.com/us/en/support/articles/crypto-api/

1.9 E*TRADE (Morgan Stanley)

Sources: - https://developer.etrade.com/getting-started - https://us.etrade.com/l/f/agreement-library/api-developer-licensing-agreement - https://developer.morganstanley.com/

1.10 Fidelity Investments

Sources: - https://snaptrade.com/brokerage-integrations/fidelity-api - https://clearingcustody.fidelity.com/app/item/RD_9883092/integration-xchange.html

1.11 Moomoo / Futu

Sources: - https://openapi.moomoo.com/moomoo-api-doc/en/ - https://www.moomoo.com/us/support/topic3_436

2. Aggregator Pathways

2.1 SnapTrade

Overview. SnapTrade is a fintech API aggregator that connects to 30+ brokerages via a single normalized API. It handles brokerage auth (OAuth per broker, stored credentials per broker), normalized data models, and provides Raxx with a unified order interface regardless of the user's broker.

Supported US Brokerages (as of 2026-05-20, partial — verify against full list): Alpaca, Robinhood, E*TRADE, Schwab, Interactive Brokers, TradeStation, Webull, Fidelity, Moomoo, Coinbase, Kraken, and 20+ others. Full list: https://snaptrade.com/brokerage-integrations

Capabilities: - Read access: account balances, holdings, transactions, positions — supported across all brokers - Trade (order routing): supported for most major US brokers; not every broker supports every order type (multi-leg options, extended hours are institution-specific) - Options: single-leg and multi-leg supported for brokers that expose it - Crypto: supported for crypto-capable brokers - Paper trading: NOT exposed via SnapTrade — SnapTrade connects to live accounts; paper trading would need to be implemented broker-side and surfaced directly (or via direct integration)

Pricing: - Free: $0, 1 connected user, 5 brokerage connections, real-time data, trading included - Pay-as-you-go (real-time): $2/user/month, unlimited users, trading included - Pay-as-you-go (daily sync): $1/user/month, read-only (no trade), $0.05/account manual sync - Custom/volume: contact sales

Regulatory exposure for Raxx: SnapTrade operates as the authorized connection intermediary. The brokerage retains the regulatory relationship with the end customer. Raxx, as a SnapTrade API consumer, is one step further removed from the brokerage relationship. This is the most compliance-protective architecture for BYOB — the aggregator holds the broker-facing agreements, not Raxx. However: SnapTrade's ability to route orders to user-chosen brokers means Raxx's role shifts to "app that generates order instructions sent through SnapTrade to user's broker." Whether that constitutes "taking or routing orders" under Exchange Act Section 15(a) is the same question that applies to direct integration — it is not resolved by using an aggregator. Securities attorney required.

Integration effort: Low-Medium — single normalized API, documented SDK, Pay-as-you-go pricing scales with user base, no upfront cost for development

Sources: - https://snaptrade.com/pricing - https://snaptrade.com/brokerage-integrations - https://docs.snaptrade.com/docs/trading-with-snaptrade - https://docs.snaptrade.com/docs/integrations

2.2 Plaid Investments

Verdict: Read-only. Not a BYOB candidate.

Plaid's Investments product provides read-only access to portfolio holdings, transactions, and balances via /investments/holdings/get and /investments/transactions/get. It does NOT support order routing or trade execution. Maximum lookback: 24 months of transaction history. No real-time data.

Plaid is appropriate for: portfolio aggregation / analytics display. It is not appropriate for any component of the BYOB trading flow.

Sources: - https://plaid.com/products/investments/ - https://plaid.com/docs/api/products/investments/

2.3 Other Aggregator Candidates

Apex Fintech Solutions (Apex Clearing): Apex operates as a clearing firm and provides white-label brokerage infrastructure. Tradier clears through Apex. Not a direct BYOB aggregator — it is a B2B clearing layer. Raxx would not interface with Apex directly; it is plumbing behind brokers.

DriveWealth: API-first brokerage infrastructure provider (B2B, not aggregator). Powers embedded brokerage for apps (Revolut, MoneyLion, etc.). Not a BYOB path — DriveWealth is an introducing broker infrastructure play, not an account-aggregation play. Would require Raxx to register as introducing broker or enter a formal BD agreement.

Yodlee (Envestnet): Investment data aggregation — read-only, similar to Plaid. Not an order-routing solution.

3. Tiered Rollout Recommendation

Tier A — First Post-Launch BYOB Targets

Criterion: Public or partner REST API + paper trading sandbox + US equities + options + FINRA/SIPC member + integration effort Low or Low-Medium + no Compliance gate blocking development start.

Tier A total estimated cost: 4–6 engineer-weeks of implementation + testing. No per-broker API licensing fees (all three are free-to-account-holder models). Attorney time for BYOB regulatory opinion is the largest cost item — estimate $3,000–$8,000 for a formal opinion from shortlisted firms (see ATTORNEY-SHORTLIST.md).

Tier B — Next 6 Months Post-BYOB Launch

Criterion: Strong brand / user base but require aggregator integration OR moderate auth complexity OR gated compliance approval.

Tier C — Deferred Indefinitely

4. Regulatory Considerations

Every item in this section is a research summary, NOT legal advice. All regulatory questions must be reviewed by a securities attorney before any BYOB feature ships to production. The shortlisted attorneys at ATTORNEY-SHORTLIST.md have been pre-vetted for IA/BD registration analysis. BYOB introduces exchange-act broker-dealer questions that go beyond Investment Advisers Act analysis — confirm each firm's scope covers Exchange Act Section 15(a) BD registration.

4.1 Does Raxx Need to Register as a Broker-Dealer?

The core question: Exchange Act Section 15(a) requires broker-dealer registration for any person who is "in the business of effecting transactions in securities for the account of others." The key phrase is "effecting transactions." A technology platform that generates order instructions and submits them to a user-chosen broker on the user's behalf is in disputed territory.

SEC guidance (crypto context, April 2026): The SEC Staff issued a statement listing conditions under which "Covered User Interface Providers" can operate without BD registration. Key conditions include:

1. User-configurable parameters with educational materials
2. No solicitation of specific transactions
3. Transparent venue/route display with objective filtering
4. No discretionary control over market information or transactions
5. Fixed-charge fee only (flat or per-transaction percentage) — no payment for order flow
6. No order routing by the platform (orders routed by the user or broker, not the platform)
7. No holding of customer funds or securities

Critical finding for Raxx BYOB: Condition 9 explicitly prohibits "taking or routing orders." Raxx's BYOB model — where Raxx submits orders to the user's broker on the user's behalf — would likely constitute "routing orders" under this framework, which means the SEC Staff guidance would NOT provide a safe harbor. This guidance was issued in the context of crypto user interfaces but signals the SEC's general posture.

Unsourced (confirm with attorney): The SEC Staff statement is described as an "interim step" expiring five years from April 13, 2026, and has "no legal force or effect" — meaning it is not binding precedent. However, it is strong directional signal.

Research finding on SEC 2025 enforcement: The SEC dropped most fintech enforcement actions based on unregistered BD activity without accompanying fraud allegations in 2025. This suggests a more permissive environment, but it does not eliminate registration risk.

Sources: - https://www.wilmerhale.com/en/insights/client-alerts/20260417-sec-staff-issues-broker-dealer-registration-guidance-for-certain-user-interfaces - https://practiceguides.chambers.com/practice-guides/fintech-2025/usa/trends-and-developments

4.2 Introducing Broker Registration

If Raxx routes orders to a user-chosen broker as an intermediary, it may fit the "introducing broker" profile: an entity that takes and transmits customer orders to a clearing broker but does not carry customer accounts or hold customer funds. Introducing brokers must register with FINRA and the SEC as broker-dealers.

Key factors that push toward "introducing broker" status: - Raxx submits orders programmatically to the broker on behalf of users - Raxx generates the specific order parameters (price, quantity, order type) - Raxx earns revenue in connection with trading activity (subscription fees are fine; per-trade fees or payment for order flow are not)

Key factors that push away from "introducing broker" status: - User explicitly authorizes each order (no discretion by Raxx) - Raxx does not hold customer funds or securities - Orders are submitted to user's own account at a broker the user chose - Raxx earns only flat subscription fees unrelated to order volume

The balance of these factors must be assessed by a securities attorney, not a researcher.

Sources: - https://www.finra.org/rules-guidance/guidance/reports/2026-finra-annual-regulatory-oversight-report/best-execution - https://www.sec.gov/rules-regulations/staff-guidance/trading-markets-frequently-asked-questions/faq-rule-606-regulation

4.3 RIA vs. BD Analysis

Earlier research (see securities-attorney-engagement-2026-05-13/) focused on whether Raxx triggers Investment Advisers Act registration as a Registered Investment Adviser. BYOB introduces a second, distinct registration question: Exchange Act broker-dealer registration.

These are separate analyses. A platform can be exempt from RIA registration but still trigger BD registration — or vice versa. The engagement with any shortlisted attorney must scope both analyses explicitly.

4.4 Best Execution Obligations

Best execution (FINRA Rule 5310) applies to broker-dealers that receive and handle customer orders. A firm cannot transfer its duty of best execution to another party.

If Raxx is not a registered BD: Best execution obligations do not directly apply to Raxx. They apply to the broker (Alpaca, Tradier, tastytrade, etc.) who receives and executes the order.

If Raxx triggers BD registration: Raxx would then bear best-execution obligations for every order it routes, including the obligation to evaluate whether the chosen broker provides best execution and to document that analysis.

Disclosure obligations under Reg NMS Rule 606: Broker-dealers must publish quarterly reports on order routing. If Raxx becomes a BD, it would need to publish these reports. This is an operational cost item (compliance + reporting infrastructure).

Sources: - https://www.finra.org/rules-guidance/guidance/reports/2026-finra-annual-regulatory-oversight-report/best-execution - https://www.federalregister.gov/documents/2023/01/27/2022-27644/regulation-best-execution

4.5 State BD Registration Triggers

Research finding: State BD registration is generally triggered by the same business activities that trigger federal registration — "effecting transactions" in securities. Most states require BD registration if the firm transacts in securities within the state, with thresholds varying.

Pennsylvania (Raxx's home state / MooseQuest LLC jurisdiction): PA securities law (PA Securities Act of 1972) generally requires BD registration for firms effecting securities transactions with PA residents. PA Department of Banking and Securities (DoBS) is the regulator.

Unsourced (confirm with attorney): Whether PA DoBS registration is required depends on the same "effecting transactions" analysis as the federal question. A determination that Raxx is not a BD at the federal level would typically (but not always) mean state registration is also not required. Attorney must confirm.

Key jurisdiction note: If BYOB targets users in all 50 states, the state BD registration analysis covers all 50 states, not just PA.

Sources: - Unsourced for PA-specific analysis — confirm with PA securities attorney

4.6 Crosby vs. Securities Counsel Scope

Matthew Crosby (IP/trademark, engaged) is NOT securities counsel. His engagement covers trademark and IP — not Exchange Act or Investment Advisers Act questions.

The prior securities attorney research (securities-attorney-engagement-2026-05-13/) identified Stark & Stark (Antonakakis), Lex Nova Law, and Parker MacIntyre as top contacts for IA Act analysis. BYOB regulatory questions should be scoped explicitly in the engagement letter for any of these attorneys, with confirmation that Exchange Act Section 15(a) BD registration analysis is in scope.

Note from reference_attorneys.md: John Covert (patent, pending reply) is also not the right resource for securities regulation.

5. Open Questions — For Securities Attorney Engagement

1. Does submitting orders to a user-chosen broker, where the user authorized Raxx to act on their behalf, constitute "effecting transactions in securities for the account of others" under Exchange Act Section 15(a)?
2. Does using a SnapTrade aggregator as the order-routing intermediary change the BD registration analysis for Raxx?
3. If Raxx is determined to be an introducing broker: what is the estimated cost and timeline for FINRA membership and BD registration for a pre-revenue seed-stage company?
4. What subscription-fee model (flat monthly, per-user, percentage-of-AUM-equivalent) is least likely to be characterized as "transaction-based compensation" that triggers BD status?
5. Do best-execution obligations attach to Raxx if it directs orders to a user-specified broker rather than exercising discretion over broker selection?
6. Does the BYOB feature require Rule 606 order routing reports?
7. Is PA DoBS state BD registration triggered by the BYOB feature? What about other key states (CA, NY, TX, FL)?
8. Does the "technology vendor" framing of the April 2026 SEC Staff statement apply to Raxx's BYOB architecture, or does the "no order routing" condition disqualify Raxx from that safe harbor?
9. Does the tastytrade partner program or Tradier third-party marketing disclosure create any agency relationship that affects Raxx's regulatory posture?
10. Are there any existing no-action letters or SEC staff guidance applicable to "automated trading platforms that route orders to user-chosen brokers"?

6. Open Questions — For Product / Architecture

1. Will Raxx store per-user broker credentials (API keys) or use OAuth tokens? The auth model affects both security architecture and regulatory analysis.
2. Does the BYOB architecture route orders programmatically without per-order user confirmation, or does the user confirm each order before it is submitted? (Affects "discretion" analysis in BD registration.)
3. What is the target launch window for BYOB Tier A? Attorney engagement must begin at minimum 60–90 days before intended ship date for opinion letter work.
4. Will BYOB support paper trading via the connected broker's paper environment, or only live accounts? (Critical for pre-launch user testing and marketing.)
5. Is there a minimum user base at which SnapTrade's $2/user/month pricing becomes material? (At 500 users: $1,000/month; at 5,000 users: $10,000/month — plan into unit economics.)

7. Cost Summary

Tier A Direct Integration

SnapTrade Aggregator (Tier B3) — Per-User Monthly Cost

SnapTrade pricing is per connected user/month ($2 with real-time data + trading). At scale, custom pricing is available. Confirm current pricing at https://snaptrade.com/pricing before any financial projection.

8. Timing Considerations

Sources

All URLs referenced in this document:

https://docs.tradier.com/docs/getting-started
https://docs.tradier.com/docs/trading
https://tradier.com/businesses/fintechs
https://brokercheck.finra.org/firm/104982
https://developer.tastytrade.com/api-overview/
https://developer.tastytrade.com/sandbox/
https://tastytrade.com/api/
https://support.tastytrade.com/support/s/solutions/articles/43000700385
https://alpaca.markets/broker
https://alpaca.markets/oauth
https://alpaca.markets/blog/alpaca-secures-occ-and-ficc-memberships-to-power-multi-asset-self-clearing-for-partners/
https://www.interactivebrokers.com/campus/ibkr-api-page/oauth-1-0a-extended/
https://www.interactivebrokers.com/campus/ibkr-api-page/web-api-trading/
https://www.interactivebrokers.com/campus/ibkr-api-page/getting-started/
https://interactivebrokers.github.io/tws-api/introduction.html
https://developer.schwab.com/
https://developer.schwab.com/user-guides/apis-and-apps/test-in-sandbox
https://medium.com/@carstensavage/the-unofficial-guide-to-charles-schwabs-trader-apis-14c1f5bc1d57
https://developer.webull.com/apis/docs/
https://www.webull.com/open-api
https://developer.tradestation.com/trading-api/
https://api.tradestation.com/docs/
https://www.tradestation.com/stocks-etfs-pricing-disclosures/
https://robinhood.com/us/en/support/articles/third-party-connections/
https://robinhood.com/us/en/support/articles/crypto-api/
https://developer.etrade.com/getting-started
https://us.etrade.com/l/f/agreement-library/api-developer-licensing-agreement
https://developer.morganstanley.com/
https://openapi.moomoo.com/moomoo-api-doc/en/
https://www.moomoo.com/us/support/topic3_436
https://snaptrade.com/pricing
https://snaptrade.com/brokerage-integrations
https://docs.snaptrade.com/docs/trading-with-snaptrade
https://docs.snaptrade.com/docs/integrations
https://plaid.com/products/investments/
https://plaid.com/docs/api/products/investments/
https://www.wilmerhale.com/en/insights/client-alerts/20260417-sec-staff-issues-broker-dealer-registration-guidance-for-certain-user-interfaces
https://www.finra.org/rules-guidance/guidance/reports/2026-finra-annual-regulatory-oversight-report/best-execution
https://www.federalregister.gov/documents/2023/01/27/2022-27644/regulation-best-execution
https://www.sec.gov/rules-regulations/staff-guidance/trading-markets-frequently-asked-questions/faq-rule-606-regulation
https://practiceguides.chambers.com/practice-guides/fintech-2025/usa/trends-and-developments