Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Node.js library for Alpaca Trade API.
| Date | Stars |
|---|---|
| 2026-07-24 | 598 |
| 2026-07-25 | 598 |
| 2026-07-28 | 598 |
| 2026-07-30 | 598 |
| 2026-08-06 | 598 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
35.0
growth rate 0.00%/day
# @alpacahq/alpaca-trade-api A single Node.js TypeScript SDK for the Alpaca **Trading API** and **Market Data API**. Both APIs live under their own namespace (`trading` / `marketData`) in one package, fronted by a unified `Alpaca` client with typed errors, resilience (retry / timeout / rate limiting), pagination helpers, ergonomic order builders, and real-time streaming. > **Upgrading from 3.x?** See the [Migration guide](./MIGRATION.md) — it maps > every endpoint old → new, explains the ergonomic layer, and ships a > [codemod](./codemods/alpaca-v3-to-v4.js) that automates most of the work. > Both files are included in the published npm package. ## Requirements - **Node.js** >= 20 (developed against v24) — the REST transport uses the platform-global `fetch`, `Headers`, `URL`, and `AbortController`. (Node 18 reached end-of-life in April 2025; the package declares `engines.node >=20`.) - Strict Node TypeScript projects may omit DOM libs; the REST declarations are portable and do not require `"dom"` in the consumer `tsconfig`. ## Runtime compatibility | Runtime | REST | Streaming | Notes | | --- | :---: | :---: | --- | | **Node.js** >= 20 | ✅ | ✅ | Primary target. | | **Bun** | ✅ | ✅ | Node-compatible (`ws` runs). | | **Deno** | ✅ | ❌ | Root auto-resolves to the REST build via the `deno` export condition. | | **Cloudflare Workers** / `workerd` | ✅ | ❌ | Root auto-resolves to the REST build (`workerd` / `worker`). | | **Vercel Edge** | ✅ | ❌ | Root auto-resolves to the REST build (`edge-light`). | | **Browser** | ✅ | ❌ | Resolves to the REST build (`browser`). Not recommended — see caveat. | Legend: ✅ supported · ❌ not supported. - **Streaming is Node/Bun only.** The WebSocket clients use Node-compatible streaming modules, which don't run on edge or in the browser. On those targets the package's [export conditions](#edge--browser-runtimes) transparently resolve the root import to the streaming-free [REST build](#rest-only-entrypoint), so REST works and the stream factories (`stockStream`, `stream`, ...) plus `submitAndWait` throw if called. For real-time streaming, run on Node or Bun. - **Browser: technically works, but discouraged.** Calling Alpaca directly from a browser ships your `APCA_API_SECRET_KEY` to the client. Prefer a server or proxy (see [`examples/marketdata-backend.ts`](./examples/marketdata-backend.ts)) rather than embedding credentials in front-end code. The same matrix plus the edge-resolution mechanics, module formats, and the REST-only entrypoint are consolidated on the docs site: **[Runtime & module compatibility](./docs/docs/runtime-compatibility.md)**. ## Install ```bash npm install @alpacahq/alpaca-trade-api ``` Migrating from `3.x`? Follow the [Migration guide](./MIGRATION.md). ## Documentation This README is the canonical, self-contained reference. There is also a [Docusaurus](https://docusaurus.io) documentation site — curated guides, a generated API reference, runtime compatibility, and the runnable examples — hosted at **<https://alpacahq.github.io/alpaca-trade-api-js/>** and deployed from [`docs/`](./docs) on every push to `master`. You can also read the whole thing **locally** in two commands: ```bash npm --prefix docs install # first time only npm --prefix docs start # dev server → http://localhost:3000/alpaca-trade-api-js/ ``` Prefer the exact production build? Run `npm --prefix docs run build` (which regenerates the API reference, examples, and migration page first), then `npm --prefix docs run serve`. The guides are hand-written under [`docs/docs/`](./docs/docs); the API reference and examples pages are generated at build time from the SDK's capability maps and `examples/`; the site migration page is derived from the canonical [`MIGRATION.md`](./MIGRATION.md). ## Install the agent skill Building on this SDK with an AI coding agent? This repo ships an [Agent Skill](https://agentskills.io) that teaches agents the SDK's mental model, idioms, and where t
Excerpt of 99,739 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:de267ce67d1fe954, topic:trading
