How to get your Stripe data ready for agentic AI
Sync Stripe charges, invoices, subscriptions, and payouts with Airbyte, then let AI agents read and search billing data through the Airbyte MCP.

Airbyte syncs Stripe billing and payments data into your warehouse with a read-only restricted key, and the Airbyte context layer lets agents read and search Stripe records directly through the Airbyte MCP.
Stripe holds the money side of the business: who paid, what they were charged, which subscriptions renewed, and which invoices are overdue. Finance, support, and revenue teams all want agents that can answer questions about that data. Those questions rarely stay inside Stripe, though. "Which enterprise accounts have a failed payment and an open support ticket" needs billing data next to CRM and support data.
That is why agents should work against a centralized, governed copy. A warehouse copy of Stripe lets agents run aggregate queries without paging through the API, keeps history beyond Stripe's 30-day event window, and puts billing records next to everything else. Airbyte also lets agents read live Stripe records when a question needs the current state.
Why Stripe data matters for agentic AI
Stripe data is precise, financial, and changes often. A few properties make it valuable and tricky for agents:
- It is the record of revenue. Charges, invoices, refunds, and payouts are the source of truth for billing questions.
- Objects change after creation. Invoices get paid, disputes open, subscriptions cancel. An agent working from stale data gives wrong answers.
- Amounts use the smallest currency unit. The Charges stream's amount column is in the smallest unit, such as cents, so agents need that context to report figures correctly.
- The API has limits. Stripe enforces request rate limits and keeps the Events API for 30 days, which shapes how data must be synced.
What agents can do with Stripe data
- Billing support. Look up a customer's invoices, charges, and subscriptions to answer "why was I charged twice" without a person searching the dashboard.
- Collections and churn signals. Find past-due invoices, failed payment intents, or canceled subscriptions and summarize them for account owners.
- Revenue reporting. Aggregate charges, refunds, and balance transactions by period, product, or plan from the warehouse copy.
- Dispute review. List open disputes with related charges and customers so a reviewer starts with context.
- Payout reconciliation. Match payouts to the balance transactions that make them up.
How Airbyte gets Stripe data ready
Authentication
Airbyte recommends creating a restricted key specifically for Airbyte with Read permissions only. You also provide your Stripe Account ID, which begins with acct_. Using a read-only key means the sync cannot change anything in Stripe.
Streams
The connector supports nearly 50 streams, all incremental except Usage Records. They include:
- Customers and payments: Customers, Charges, Payment Intents, Payment Methods, Refunds, Disputes, Early Fraud Warnings, Reviews
- Billing: Invoices, Invoice Items, Invoice Line Items, Subscriptions, Subscription Items, Subscription Schedule, Plans, Prices, Products, Coupons, Promotion Codes, Credit Notes
- Money movement: Balance Transactions, Payouts, Payout Balance Transactions, Transfers, Transfer Reversals, Top Ups
- Checkout: Checkout Sessions and their line items
- Connect and Issuing: Accounts, Persons, Bank Accounts, External Accounts, Application Fees, Authorizations, Cardholders, Cards, Transactions
- Events, Files, and File Links
Stripe's JSON types match Airbyte's, so no type conversion is applied.
How incremental sync works
Stripe's API doesn't let you ask for objects updated since a given time, so the connector uses the Events API for incremental syncs of most streams and adds an artificial updated cursor. Some streams, such as Balance Transactions, Events, and Files, sync by creation date instead.
The Events API matters for planning:
- Stripe only guarantees access to the last 30 days of events. Sync at least once every 30 days to keep Events-based streams current.
- Cursor age validation can be turned on per stream. If a stream's cursor is older than 30 days, the connector falls back to a full refresh for that stream instead of missing changes. Airbyte recommends it for high-volume streams like Charges, Invoices, Invoice Items, Invoice Line Items, Payment Intents, and Payouts.
- If you use Full Refresh Overwrite on the Events stream, events older than 30 days are removed from the destination and replaced with the latest 30 days.
Settings that shape the sync
- Replication Start Date: data from this date on is replicated.
- Lookback Window: rereads the last N days to catch post-transaction changes. The default of 0 doesn't reread.
- Data Request Window: the span covered by each API request, 365 days by default. Smaller windows mean less to resync if a sync is interrupted.
- Concurrent threads and max API calls per second: tune these to stay under Stripe's limits.
Deletes
For a limited set of streams, including Customers, Invoices, Invoice Items, Subscriptions, Products, Prices, Plans, Coupons, Persons, and several bank account and card streams, records are marked with an is_deleted flag when the delete event happens in Stripe. Agents should filter on it.
Rate limits
The connector retries and backs off on HTTP 429 responses. Stripe allows 25 requests per second for sandbox keys and 100 for live keys. If other systems share the same account's limits, lower the thread count or set a stricter calls-per-second value.
How agents reach Stripe data
Stripe is an agent connector in Airbyte Cloud, so it works with both parts of the context layer:
- Agent access (direct reads). Agents can list and get customers, invoices, charges, subscriptions, refunds, products, payment intents, disputes, payouts, balance transactions, and the current balance. Stripe's own search is available for customers, invoices, charges, subscriptions, products, and payment intents. Direct reads use credentials stored in Airbyte, are read-only, and count toward Stripe's rate limits.
- Search. When a connection syncs Stripe to an agent-connector destination, Airbyte can index selected streams such as customers, invoices, charges, subscriptions, and refunds, so agents can search synced records.
Agents connect through the hosted Airbyte MCP at https://mcp.airbyte.com/mcp. Direct reads and searches are free up to 100,000 combined per organization per month.
Because direct reads use the connector's stored key rather than each user's permissions, an Airbyte user could see Stripe records through an agent that they could not see in Stripe themselves. Decide who can use the connector with that in mind.
What this unlocks
- Billing answers from a complete, current copy of Stripe objects.
- History beyond Stripe's 30-day event window, kept in your warehouse.
- Deleted customers, invoices, and subscriptions flagged instead of silently missing.
- Live lookups for "what is the status right now" questions.
- Billing joined with CRM, support, and product data.
Getting started
- Create a read-only restricted key in Stripe.
- Create a Stripe source in Airbyte with your Account ID and key.
- Pick streams, enable cursor age validation for high-volume ones, and set a lookback window if amounts change after creation.
- Sync to BigQuery or Snowflake, then connect your agent to the Airbyte MCP.
Try Airbyte free or talk to sales about billing data for agents.
Frequently asked questions
What Stripe key should I use with Airbyte?
Create a new restricted key for Airbyte and grant it Read permissions only. You enter it with your Stripe Account ID, which starts with acct_.
Why does the 30-day Events API limit matter?
Incremental syncs of many Stripe streams use the Events API, and Stripe only guarantees access to the last 30 days of events. Sync at least every 30 days, and consider enabling cursor age validation so stale streams fall back to a full refresh instead of missing changes.
Does Airbyte capture deleted Stripe records?
For a limited set of streams, including Customers, Invoices, Invoice Items, Subscriptions, Products, Prices, Plans, and Coupons, records are marked with an is_deleted flag when the delete event happens in Stripe.
How does Airbyte handle Stripe rate limits?
The connector retries and backs off on HTTP 429 responses. You can lower the number of concurrent threads or set a maximum number of API calls per second if other systems share the same Stripe limits.
Can an agent create refunds or invoices through the Airbyte context layer?
No. Direct reads and searches through the context layer are read-only. Agents can list, get, and search Stripe records, but cannot create or change them through these tools.
Integrate with 700+ apps using Airbyte
Move data from 700+ sources into warehouses, lakes, and beyond. Set up pipelines in minutes with pre-built connectors and the Connector Builder.
