Paper Trading — Alpaca Data API TOS + Regulatory Exposure

Status: research-only. This document does NOT constitute legal or tax advice. Before acting on anything here, consult a securities attorney (not Adam Schwartz — see Q2 below) and contact Alpaca's partnership/sales team directly for written confirmation on data terms. Last updated: 2026-06-11. Sources as of that date — verify freshness.

Q1 — Alpaca Data API Redistribution

TL;DR

Alpaca's own support article states flatly: "Unfortunately, you cannot redistribute Alpaca API data." This is an unambiguous prohibition on the SaaS display pattern Raxx is considering — where a single Alpaca API key feeds real-time quotes to Raxx end users who are not individually registered with Alpaca. Before treating this as a hard blocker, Kristerpher should get a written answer from Alpaca's sales/partnerships team, because (a) support-article language is not a contract and may be out of date, (b) Alpaca does offer commercial/institutional tiers that may have different terms, and (c) many fintech SaaS operators have negotiated data-redistribution addenda with Alpaca directly. The current publicly-documented default, however, is: redistribution prohibited.

Verbatim source quote

From https://alpaca.markets/support/redistribute-alpaca-api (fetched 2026-06-11):

"Unfortunately, you cannot redistribute Alpaca API data."

No additional conditions, exceptions, or carve-outs appear on that support page. The page does not reference non-professional subscriber certifications, SaaS-specific tiers, or addenda.

What the Market Data FAQ adds

The Market Data FAQ at https://docs.alpaca.markets/us/docs/market-data-faq does not address redistribution, non-professional/professional subscriber distinctions, or SaaS display rules. It focuses on authentication errors, SIP vs IEX data, and bar aggregation. No useful redistribution language was found there.

Plain-English summary of the current documented position

Pricing tier implications (UNKNOWN — confirm with Alpaca)

Alpaca's data pricing page (https://alpaca.markets/data) lists real-time and historical data plans, but the public documentation does not describe a "redistribution-permitted" commercial tier distinct from individual API access. Whether Alpaca offers an OEM/enterprise data license that would permit SaaS display is undocumented in public sources as of this research date.

Specific questions to ask Alpaca support / sales before launch

These are not rhetorical — they need written answers before any paper-trading feature ships live quotes:

1. "Does Alpaca offer a data redistribution license or commercial addendum that would permit a SaaS application (Raxx) to display real-time quotes sourced from the Alpaca Data API to end users who do not have individual Alpaca accounts? If so, what is the pricing and what are the subscriber certification requirements (e.g., non-professional attestation per end user)?"

2. "If redistribution is not permitted under any tier, what is Alpaca's recommended path for a fintech SaaS that wants to use Alpaca for paper trading execution but needs a separate compliant market data feed for display to end users?"

3. "Does the prohibition on redistribution apply equally to delayed (15-min) quotes, or only to real-time/Level 1 data? Is there a delayed-data carve-out for paper trading display?"

Alternative data sources if Alpaca redistribution stays prohibited

These are research pointers — not endorsements — for Kristerpher to evaluate with a data vendor:

• Polygon.io — has an explicit "Starter / Developer / Advanced" tier structure with a SaaS redistribution / white-label tier; redistribution terms are documented publicly at https://polygon.io/terms
• Tradier — offers a brokerage + market data API with SaaS partner terms; used by several paper-trading platforms
• IEX Cloud (now Intrinio) — has business/redistribution plan documentation

None of these have been vetted for current terms in this research. They are starting points for the next research pass.

Q2 — Paper Trading Regulatory Exposure

TL;DR

A platform offering simulated/paper trading with no real money execution does not itself trigger broker-dealer registration under the Securities Exchange Act of 1934 or FINRA membership requirements — those attach to platforms that execute, route, or clear actual securities transactions. However, two adjacent risks exist: (1) if Raxx's tax engine produces or implies tax advice rather than purely mechanical calculations from user-supplied data, it could be read as tax practice; (2) if Raxx's paper-trading feedback loop includes personalized trade recommendations (rather than purely executing the user's own pre-set rules), that could attract Investment Advisers Act scrutiny. The key word in both cases is "personalized" — rule-enforcement on user-defined parameters is structurally different from personalized advice, which is Raxx's stated product thesis. PA state registration mirrors the federal analysis: broker-dealer and IA registration are triggered by the same substantive activity thresholds. No PA-specific paper-trading carve-out was located in this research.

Regulatory exposure summary

What does NOT appear to apply to paper trading with no real-money execution:

• FINRA broker-dealer registration (Exchange Act § 15) — triggered by effecting transactions in securities for the accounts of others; simulated paper trades with no real settlement do not qualify
• SEC investment adviser registration — triggered by providing investment advice "for compensation" to "others"; if Raxx executes user-defined rules without personalization, most securities attorneys read this outside IA Act scope (unsourced — confirm with securities counsel)

What COULD apply depending on product decisions:

• Investment Advisers Act of 1940 — if paper-trading analytics, performance scoring, or AI-assisted commentary in Raxx's "Shape" sentiment layer is characterized as personalized investment advice, even for no direct charge, the "compensation" prong can be met through indirect business benefit (unsourced — confirm with securities counsel)
• State IA registration (PA) — Pennsylvania securities law (70 P.S. § 1-301 et seq., the Pennsylvania Securities Act of 1972) has IA registration requirements that parallel federal thresholds; the PA Securities Commission is the relevant body (unsourced — confirm with PA securities counsel)
• Tax practice / Circular 230 — the tax engine must disclaim clearly that it is a mechanical calculator, not tax advice; if the engine provides guidance on tax optimization strategies, it could be read as unauthorized tax practice (unsourced — confirm with CPA/tax attorney)

How paper-trading competitors position themselves (competitive landscape — not legal guidance):

• TradingView's PaperTrading and thinkorswim's paperMoney disclaim prominently that paper trading is for "educational and practice purposes" and explicitly not investment advice; these disclaimers are structural, appearing in TOS and at the point of use
• These platforms avoid the IA Act primarily because they provide tools, not personalized recommendations; the user's own inputs and configurations drive behavior

Questions for Kristerpher's attorney

Note: Adam Schwartz handles IP. These questions require a securities attorney — ideally one with fintech SaaS experience. This is a separate engagement from IP counsel.

1. "Does Raxx's paper-trading feature (simulated execution of user-defined rules, no real money movement, no personalized trade recommendations from Raxx) trigger any federal broker-dealer or investment adviser registration obligation? Does adding a tax-impact calculator to the paper-trading output change that analysis?"

2. "Does Pennsylvania require state-level investment adviser or broker-dealer registration for a SaaS that offers paper trading and performance analytics, even with no real-money execution? What disclosures are required at the PA level before we launch to PA residents?"

3. "What TOS / in-product disclaimer language is sufficient to maintain the 'educational tool' framing for paper trading, and at what point does AI-generated commentary on simulated results (e.g., Raxx's Shape sentiment layer) cross into regulated investment advice territory?"

Recommended Posture for v1

Data: Do not ship live-quote display to Raxx end users sourced from Alpaca's Data API until Alpaca's sales/partnerships team provides written confirmation that redistribution is permitted under a commercial addendum. For v1 paper trading, evaluate using delayed data (15-min, which is often redistribution-exempt) or a Polygon.io / Tradier commercial redistribution tier while the Alpaca question is resolved.

Regulatory: Paper trading with no real-money execution and no personalized recommendations is widely treated as outside broker-dealer and IA Act scope — but "widely treated" is not a legal opinion. Have a securities attorney review the product spec before launch, focusing specifically on whether Shape-layer commentary and the tax engine create an IA nexus.

Timing / Deadlines

No hard regulatory deadlines identified. However: if Raxx launches paper trading with live Alpaca-sourced quotes before resolving the redistribution question, that is a contract violation exposure (Alpaca TOS), not a regulatory violation per se — but it could result in API key revocation. Prioritize getting Alpaca's written answer before any public beta of the paper-trading feature.

Questions for Attorney (securities-specific)

See Q2 section above. Recommend engaging a securities/fintech attorney separate from Adam Schwartz (IP). Three questions itemized above.

Questions for Alpaca Sales/Partnerships

Three questions itemized in Q1 section above. These should be asked in writing (email, not support chat) so the response is documented.

Questions for CPA

None identified from this research. The tax engine disclaimer question is for a tax attorney, not a CPA, because it touches on unauthorized practice of law/tax rather than accounting methodology.

Sources

https://alpaca.markets/support/redistribute-alpaca-api
https://docs.alpaca.markets/us/docs/market-data-faq
https://alpaca.markets/data
https://www.innreg.com/blog/fintech-regulation-guide-for-startups
https://www.sec.gov/files/2025-exam-priorities.pdf

Primary source attempted and returned 404:

https://alpaca.markets/legal/market-data-agreement
https://docs.alpaca.markets/docs/market-data-api

These should be re-checked directly on Alpaca's current site — URL structures may have changed.