Commerce & Payments · Integration
Alpaca
Add Alpaca to your product for your customers, and give your AI agents governed access to it.
Alpaca is a brokerage API, so no category here is exact; Commerce & Payments is the least-wrong because orders, transfers and account holders are real first-class objects, while invoices and vendors are not. Live and paper trading run on separate hosts, api.alpaca.markets and paper-api.alpaca.markets, sharing the same request shape and both returning 401 without the key and secret headers, which means a misconfigured base URL fails quietly by trading in the wrong environment rather than erroring. Market data lives on its own host and its own entitlements, so a key that reads accounts fine can still be refused for real-time quotes depending on the data plan. Orders are asynchronous: a successful POST returns an accepted order, not a fill, and the terminal state arrives later over the streaming connection or on a subsequent read, so treating the create response as an execution is a common and expensive mistake. Anything that moves money or places an order should stay behind explicit human approval in your product. fastn keeps each customer's key, secret and environment separate and audited, and maintains the connection as endpoints change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Alpaca account so balances and positions appear in your product under their credentials
Show a reconciled view of orders and fills alongside the records your application already holds
Surface a customer's transfer history so finance staff can match cash movements without leaving your app
Keep a paper-trading sandbox connection alongside the live one so customers can test your workflows safely
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to summarise a tenant's current positions and unrealised profit and loss without placing any order
Have an agent prepare an order for human approval and never submit it itself, with every read and draft audited per tenant
Let an agent report which orders from yesterday are still open rather than filled
Example prompt
What are our current open positions and which orders from yesterday have not filled?
Set up Alpaca in 4 steps
- 01Enable the Alpaca connector from your fastn dashboard.
- 02Have each customer authorise their own Alpaca account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Alpaca integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Alpaca integration without building it. Your customers connect their own Alpaca account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Alpaca update is not your on-call problem.
- One integration serves your product and your agents. The same governed Alpaca connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Alpaca, across other categories.
NetSuite
Notion
Box
DocusignAlpaca integration FAQ
How do I add an Alpaca integration to my product?
Enable the Alpaca connector in your fastn dashboard, then let each customer authenticate their own Alpaca account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Alpaca client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Alpaca account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Alpaca account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Alpaca integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to summarise a tenant's current positions and unrealised profit and loss without placing any order
Who maintains the Alpaca integration?
fastn does. When Alpaca changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Alpaca integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Alpaca integration?
A common starting point: let a customer connect their own Alpaca account so balances and positions appear in your product under their credentials. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Alpaca integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Alpaca does not change your per-connector cost. You can start free with 3 connected accounts.
Add Alpaca to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.