What changed
On November 5, 2026, Stripe announced agent-accessible analytics via its MCP server and new Queries and Reports APIs for all Stripe users. Queries accept SQL as asynchronous QueryRun jobs and return inline results or CSV downloads; Reports runs Stripe-defined financial templates. Queries are free through January 31, 2027, with usage-based billing starting February 1. Reports remain free. Stripe's examples cover reconciliation, MRR, churn and subscription analytics.
Why it matters
Small SaaS operators can analyse their own Stripe payment and subscription data without building a separate export-and-query pipeline, and can let an agent assemble explainable revenue reports. But automation should use restricted read permissions, inspect SQL and financial calculations, manage asynchronous job status and avoid surprise query charges after the introductory period.
Two different data interfaces, not an unrestricted payment agent
The Queries API executes submitted SQL over Stripe analytical tables, while Reports exposes predefined report templates and parameters. Stripe's MCP can help an agent discover tables and formulate queries. This is read-only financial analysis, not permission to issue refunds or alter subscriptions. Restricted API keys require data_queries_read or data_reports_read, respectively.
The free period ends on January 31
Stripe says Queries API execution is free through January 31, 2027, and usage-based credit pricing begins February 1. Reports API remains free. The announcement does not publish a fixed per-query dollar cost, so builders should confirm account-specific credits and terms before scheduling high-volume analyses.
Async jobs, caching and result lifetimes matter
A Queries API POST creates a QueryRun that may be running, succeeded or failed. Clients can poll or listen for signed webhooks; identical queries may return cached runs. Results expire after 90 days and file download URLs after five minutes. Query creation and concurrency have separate live/sandbox limits, and files are capped at 5GB. Reports follow a similar asynchronous lifecycle.
Verify AI-produced financial answers
Stripe describes over 300 modelled tables and encourages inspecting generated SQL. A prompt such as 'why did MRR fall?' can be useful for investigation, but a plausible narrative is not audited accounting. Verify filters, timezone, currency conversion, refunds, disputes, subscription status and definitions against the actual underlying data.
Availability and evidence limits
Stripe's November 5 announcement says the APIs are available to all users, and its current API documentation provides concrete request/response and permission details. We did not execute queries on a live merchant account or independently measure latency, costs or model accuracy. The API examples currently use a 2026-10-28.preview version header, which integrators should verify against their account and current API documentation.