Key details

  1. Announcement dated November 5, 2026.
  2. Queries API and Reports API accessible through Stripe MCP or direct API calls.
  3. Queries free through January 31, 2027; usage-based pricing starts February 1.
  4. Reports API remains free.
  5. Restricted key permissions: data_queries_read and data_reports_read.
  6. QueryRun jobs are asynchronous; successful results can be downloaded or paged inline.
  7. Result retention is 90 days; signed file URLs last five minutes.
  8. Live QueryRun creation limit 10 per second, with 100 concurrent jobs; sandbox limits lower.

What builders should take away

  1. Trial the read-only APIs with a restricted key and a small reconciliation report.
  2. Inspect SQL and compare computed MRR/churn against existing finance definitions before trusting agent output.
  3. Handle asynchronous success/failure and webhook verification; avoid treating HTTP 200 as a finished query.
  4. Export results that must survive the 90-day retention window.
  5. Set query usage monitoring and check actual pricing before February 1, 2027.

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.

Timeline

2026-11-05

Agent-readable analytics announced

Stripe announces Queries and Reports APIs plus MCP access for all users.
2027-01-31

Last day of free query period

Stripe's published free Queries API period ends.
2027-02-01

Query usage billing begins

Queries API switches to usage-based pricing; Reports API stays free.

What to watch next

  • Stripe's published query-credit rates and any account-specific billing controls.
  • API version and access changes as integrations mature.
  • Independent production measurements of agent-generated analytics accuracy and costs.

Still unclear

  • No independently executed merchant-account test was performed.
  • The official announcement does not establish a universal dollar price per query after January 31.
  • Generated financial analyses depend on model quality, SQL and account-specific data.

Sources

Direct reading behind this dossier.

3 sources
Queries API
Stripe Docs primary

Current query job semantics, permissions, pricing date, caching, limits and retention.

Reports v2 API
Stripe Docs primary

Current reports semantics, read permission, report templates and job lifecycle.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment