Claude · Published 2026-09-24

Patrick Collison on Claude Code at Stripe

Open on YouTube ↗

Summary

Overview

  • Speaker: Patrick Collison
  • Channel: Claude
  • Main topic: The adoption, impact, and scaling of AI tools and Claude Code at Stripe
  • Purpose: To share insights on how Stripe integrates AI and Claude Code into its engineering workflow, the balance between speed and reliability, and the broader economic impacts of AI on entrepreneurship. Stripe CEO Patrick Collison discusses how Stripe built custom multi-modal weather stations and how they approach software development reliability, security, and velocity using AI tools like Claude Code. They explore how AI accelerates engineering, impacts business creation statistics, shifts organizational paradigms from human-to-human to agent economies, and changes the nature of software engineering productivity.

Topic Map

Reliability, Speed, and AI Integration at Stripe

  • Explanation: Stripe operates with 5.5 nines of reliability for core APIs while simultaneously attempting rapid feature development and continuous deployment.
  • Key claims:
    • Reliability and security are paramount for financial services APIs.
    • Continuous deployment and rapid feature evolution require investment in rigorous end-to-end development and QA processes.
    • Dev boxes, instrumentation, observability, and incremental rollouts enable speed without sacrificing reliability.
  • Examples:
    • Stripe engineers merging hundreds of pull requests per hour with AI assistance while maintaining high reliability standards.
  • Terminology:
    • dev boxes
    • instrumentation
    • observability
    • pull requests
    • incremental rollout
  • Why it matters: Demonstrates that high reliability and extreme velocity are not mutually exclusive when paired with proper AI guardrails and quality assurance infrastructure.

AI-Assisted Engineering and Code Quality

  • Explanation: Evaluating the impact of AI coding assistants on software development velocity, pull request quality, and engineering team productivity.
  • Key claims:
    • Quality per pull request has increased over the last 18 months despite a slight uptick in incident rate per unit time.
    • Total reliability and security metrics remain essentially unchanged.
    • AI agents enable small teams to compete against much larger teams by orchestrating complex plans across multiple codebases.
  • Examples:
    • An engineer merging over 600 pull requests in one hour using AI assistance with only one reversion.
    • Stripe building 'Stripe Projects' inspired by Claude Code to couple substance with logging, hosting, and database services.
  • Terminology:
    • Claude Code
    • pull requests
    • codebase
    • agent
    • prompt injection protection
  • Why it matters: Proves that AI coding tools can radically accelerate software development velocity while preserving code quality and security.

Macroeconomic Impact of AI on Business Creation

  • Explanation: Analyzing Stripe data, US Census Bureau statistics, and UK business formation to understand how AI influences entrepreneurship and new firm creation.
  • Key claims:
    • The acceleration of new business creation on Stripe is on a relative basis much larger than any prior historical acceleration.
    • New business registrations and Stripe sign-ups are showing a significant upward trend in the UK and US.
    • Average revenue per new business and the number of businesses reaching key revenue thresholds are both improving.
  • Examples:
    • UK official company statistics showing a surge in entrepreneurship compared to historical trends.
    • Stripe data indicating roughly a quarter of all US Delaware corporations are incorporated with Stripe.
  • Terminology:
    • time series
    • business formation
    • entrepreneurship
    • revenue threshold
    • macroeconomics
  • Why it matters: Highlights the broader economic proof points that AI is driving a major boom in entrepreneurship and business success.

The Agent Economy and Future Workflows

  • Explanation: Exploring how AI agents acting as counterparties will change transactions, business models, and software architecture.
  • Key claims:
    • In the future, most transactions will be between agents on both sides.
    • Stripe is rethinking how agents will sign up for Stripe, use APIs, make payments, and interact with infrastructure.
    • Agent-to-agent transactions will create a massive vortex of agent-to-agent payments.
  • Examples:
    • Agents orchestrating 10 different dev boxes to execute complex multi-day software engineering plans autonomously.
  • Terminology:
    • agent economy
    • counterparties
    • MCP
    • CLI
    • agent-to-agent payments
  • Why it matters: Anticipates the next paradigm shift in commerce where AI agents become primary economic actors.

Key Points

Reliability and Speed Coexistence

  • Explanation: Stripe balances 5.5 nines of reliability with continuous deployment by investing heavily in automated testing, dev boxes, and incremental rollouts.
  • Evidence: Stripe operates core APIs with extreme reliability while shipping products and features rapidly.
  • Practical implication: Engineering organizations must invest in rigorous dev-box instrumentation and QA pipelines to safely leverage AI speed.

Code Quality and Pull Request Velocity

  • Explanation: AI coding tools significantly increase pull request velocity and code quality without degrading overall system reliability.
  • Evidence: Engineers merging hundreds of PRs per hour with AI assistance with negligible reversion rates.
  • Practical implication: Teams can increase feature output multi-fold by embedding AI into developer workflows.

Macroeconomic Acceleration

  • Explanation: AI is lowering the barriers to building software and starting businesses, leading to a measurable surge in global entrepreneurship.
  • Evidence: Stripe sign-up data and US/UK business formation statistics showing unprecedented growth rates.
  • Practical implication: Founders and operators should expect increased market dynamism and faster competitive cycles.

Frameworks, Models & Processes

Continuous Feature Evolution Development Process

  • How it works: Combines fast AI-driven code generation with rigorous developer box instrumentation, automated test suites, and progressive rollout strategies.
  • Components:
    • Dev boxes
    • Instrumentation and observability
    • Incremental rollout strategies
    • Automated test suite execution
  • When to use: When scaling software development velocity in high-reliability environments.

Examples & Case Studies

An engineer at Stripe had over 600 pull requests merged over the course of an hour, all written with AI, with only one reverted.

  • Illustrates: The extreme acceleration possible in software engineering velocity using AI tools.
  • Lesson: AI can handle massive code generation volume while maintaining high success rates when guarded by strong test suites.

Stripe launched 'Stripe Projects' inspired by Claude Code to couple codebases with logging, hosting, and database services.

  • Illustrates: How AI tools inspire new internal product paradigms and developer workflows.
  • Lesson: Integrating AI agents into product architecture unlocks new ways for developers to build and manage services.

Actionable Takeaways

  • Immediate:
    • Integrate AI coding tools like Claude Code into developer workflows to accelerate pull request velocity.
    • Invest in robust QA and test suites to maintain reliability when shipping AI-generated code.
  • Strategic:
    • Prepare infrastructure for the upcoming agent economy where AI agents transact with each other.
    • Recognize that AI enables smaller teams to tackle ambitious problems and compete with much larger organizations.
  • Questions to investigate:
    • How will agent-to-agent payment flows and API interactions change financial infrastructure?
    • What is the distribution of productivity gains across different types of software projects?

Claims Worth Verifying

  • Stripe operates with 5.5 nines of reliability for its core APIs. (statistical)
  • Roughly a quarter of all Delaware corporations are incorporated with Stripe. (statistical)

Notable Quotes

"Stripe operates with five and a half nines of reliability." (at 0:35) "Every codebase is now the prompt for another codebase." (at 16:46)

Compressed Summary

  • Stripe maintains 5.5 nines of reliability while accelerating development with AI.
  • Claude Code enables engineers to merge hundreds of AI-written pull requests per hour.
  • Macroeconomic data shows a historic surge in entrepreneurship and new business creation.
  • Future commerce will feature AI agents as primary counterparties transacting via APIs and automated payments.
  • Keywords: claude, stripe, ai, reliability, startups
  • Core insight: AI coding tools dramatically accelerate software engineering velocity and entrepreneurship while maintaining high system reliability.

Core insights

6
Empirical Resulthigh noveltymoderate evidence

Stripe decouples deployment velocity from reliability through infrastructure rather than process discipline: dev boxes, instrumentation, observability, and incremental rollouts let engineers merge hundreds of PRs/hour while core APIs hold 5.5 nines of reliability. The observable signature is that AI-driven velocity raises per-PR quality and only slightly raises incident rate per unit time, while aggregate reliability/security metrics stay flat.

Why it matters

It reframes AI coding adoption as an infrastructure investment problem: the guardrail stack (isolated environments, observability, progressive rollout, test suites) is what bounds the blast radius of machine-generated code, not human review bandwidth.

Generalization

Teams that add agentic code generation without equivalent investment in isolation, observability, and progressive rollout should expect aggregate reliability erosion, not the flat metrics Stripe reports.

Stripe operates with 5.5 nines of reliability for core APIs while simultaneously attempting rapid feature development and continuous deployment.
Open source video
Quality per pull request has increased over the last 18 months despite a slight uptick in incident rate per unit time.
Open source video
Total reliability and security metrics remain essentially unchanged.
Open source video
Dev boxes, instrumentation, observability, and incremental rollouts enable speed without sacrificing reliability.
Open source video
Mental Modelmedium noveltymoderate evidence

The per-PR quality metric improving while aggregate reliability stays flat implies the real constraint has moved downstream of code generation: verification, merge/rollback automation, and staged rollout become the throughput bottleneck and the primary control surface.

Why it matters

Optimizing generation speed yields diminishing returns once verification infrastructure is saturated; engineering effort should shift to test synthesis, rollback tooling, and rollout gating.

Generalization

For any agentic pipeline, identify the first stage that cannot keep pace with the generative stage; that stage defines system throughput and is where reliability engineering budget belongs.

Quality per pull request has increased over the last 18 months despite a slight uptick in incident rate per unit time.
Open source video
AI can handle massive code generation volume while maintaining high success rates when guarded by strong test suites.
Open source video
Architecturehigh noveltyweak evidence

Agents are being used as long-horizon orchestrators of parallel isolated execution environments, not single-session assistants: the cited pattern is one agent orchestrating ~10 dev boxes to execute a complex multi-day software engineering plan autonomously.

Why it matters

This implies agent runtimes need primitives for provisioning, scheduling, and consolidating work across many ephemeral environments, plus durability across multi-day horizons — a different architecture than single-loop tool-calling agents.

Generalization

Long-horizon agentic systems require an environment-orchestration layer (provisioning, state hydration, result reconciliation) analogous to a distributed scheduler, not just context management.

Agents orchestrating 10 different dev boxes to execute complex multi-day software engineering plans autonomously.
Open source video
Predictionmedium noveltyweak evidence

The predicted shift to agent-to-agent transactions forces a rethink of onboarding, API auth, and payment primitives, because the counterparty is no longer assumed to be a human operator. Prompt injection protection appears alongside core engineering terminology, signaling that security boundaries between agents and infrastructure are treated as a first-class design concern.

Why it matters

If both sides of a transaction can be agents, identity, authorization, rate/privilege scoping, and payment authorization must be designed for non-human principals from the start rather than retrofitted onto human-oriented signup flows.

Generalization

APIs and payment rails built around human account lifecycle will need agent-native identity and delegated-authority primitives before agent-mediated commerce scales.

In the future, most transactions will be between agents on both sides.
Open source video
Stripe is rethinking how agents will sign up for Stripe, use APIs, make payments, and interact with infrastructure.
Open source video
Agent-to-agent transactions will create a massive vortex of agent-to-agent payments.
Open source video
Predictionmedium noveltyweak evidence

Small teams can now compete with much larger teams when AI agents orchestrate complex plans across multiple codebases, suggesting the unit of leverage shifts from headcount to the agent's ability to coordinate changes spanning repositories.

Why it matters

Cross-codebase orchestration — not single-repo code completion — is the capability that changes team-size economics, which points design effort at dependency awareness and multi-repo consistency rather than raw token throughput.

Generalization

The defensible agent capability is coordinated multi-artifact change management; single-artifact generation is commoditized.

AI agents enable small teams to compete against much larger teams by orchestrating complex plans across multiple codebases.
Open source video
Architecturemedium noveltyweak evidence

Claude Code's design patterns propagated into an internal product (Stripe Projects), coupling codebases directly to logging, hosting, and database services — i.e., the agent interface becomes a control plane over infrastructure provisioning.

Why it matters

It shows agent tooling influencing product surface design, where the coding agent is a thin layer over service provisioning rather than a pure text-editing assistant.

Generalization

Expect coding-agent interaction patterns to generalize into infrastructure control planes, collapsing 'write code' and 'provision the runtime the code needs' into one interface.

Stripe building 'Stripe Projects' inspired by Claude Code to couple substance with logging, hosting, and database services.
Open source video

Deep dives

4

Verification as the post-generation throughput bottleneck

Research question

Once agentic code generation stops being the limiting stage, which downstream stage (test synthesis, review/merge automation, rollback tooling, staged rollout gating) saturates first, and what instrumentation exposes that saturation point before aggregate reliability degrades?

Why

Determines where reliability engineering budget should go. If Stripe's flat aggregate reliability alongside rising per-PR quality is a verification-infrastructure result, then teams adding agents without equivalent verification investment will see throughput gains capped and reliability erode rather than stay flat.

Quality per pull request has increased over the last 18 months despite a slight uptick in incident rate per unit time.
Open source video
Total reliability and security metrics remain essentially unchanged.
Open source video
Continuous deployment and rapid feature evolution require investment in rigorous end-to-end development and QA processes.
Open source video
Source video

Runtime primitives for long-horizon, multi-environment agent plans

Research question

What provisioning, state-hydration, reconciliation, and partial-failure-recovery primitives does an agent runtime need to durably drive ~10 parallel isolated dev boxes across a multi-day plan, and how do those differ from single-loop tool-calling agent context management?

Why

Shifts agent architecture from context management to distributed scheduling over ephemeral environments. Without reconciliation and durable plan state, long-horizon autonomy degrades silently on partial failure; with it, cross-repo work becomes schedulable rather than serialized.

Dev boxes, instrumentation, observability, and incremental rollouts enable speed without sacrificing reliability.
Open source video
AI agents enable small teams to compete against much larger teams by orchestrating complex plans across multiple codebases.
Open source video
Source video

Agent-native identity, delegated authority, and payment authorization

Research question

What identity, scoping, and delegated-authority scheme lets an agent act as a transaction counterparty on a payment rail at scale without inheriting human account-lifecycle assumptions or widening prompt-injection blast radius?

Why

If the counterparty is no longer assumed to be a human operator, signup, API auth, privilege scoping, and payment authorization must be designed for non-human principals from the start; retrofitting delegated authority onto human-oriented flows is a security-boundary problem, not a UX problem.

Stripe is rethinking how agents will sign up for Stripe, use APIs, make payments, and interact with infrastructure.
Open source video
prompt injection protection
Open source video
Source video

Causal decomposition of AI-attributed throughput gains

Research question

How much of reported PR-throughput gains (e.g., 600 PRs merged in one hour with one reversion) is attributable to the AI tool versus pre-existing test suites, dev-box isolation, rollout gating, and observability, and how does reversion rate move when each guardrail layer is removed?

Why

Without isolating causal contributions, the 600-PR result is not transferable: teams may over-attribute results to the model and under-invest in the guardrail stack that actually bounds blast radius, producing a failure mode of silent degradation when guards are weak.

An engineer merging over 600 pull requests in one hour using AI assistance with only one reversion.
Open source video
Stripe engineers merging hundreds of pull requests per hour with AI assistance while maintaining high reliability standards.
Open source video
Source video

Article ideas

3

Flat Reliability With Rising PR Quality Is a Guardrail Result, Not a Model Result

Stripe's combination of rising per-PR quality, hundreds of merged PRs per hour, and essentially unchanged aggregate reliability and security is explained by infrastructure (dev boxes, instrumentation, observability, incremental rollout, test suites) rather than by model capability; teams that adopt agentic generation without the equivalent guardrail stack should expect reliability erosion, because the same claim about the model is not what the metrics actually support.

Angle

Separate what the reported metrics do and do not prove, then map each metric to the infrastructure layer that produces it.

Source video

The Bottleneck Moved: Reliability Engineering Budget Should Follow Verification, Not Review

Once generation throughput exceeds what verification can absorb, per-change quality improvements no longer convert into reliability headroom, and review bandwidth stops being the binding constraint; the productive investments become test synthesis, merge/rollback automation, and rollout gating, plus the instrumentation needed to detect when that saturation point is reached.

Angle

Reframe the velocity/reliability trade-off as a queueing problem where the slowest stage sets system throughput.

Source video

Agent Counterparties Break Payment Primitive Assumptions Before They Break Volume

Designing for agent-to-agent transactions is not a volume-scaling problem to defer until demand arrives: identity, delegated authority, privilege scoping, and payment authorization for non-human principals are prerequisites that cannot be retrofitted onto human-oriented signup and API flows, and prompt-injection defense belongs in the same security-boundary design conversation.

Angle

Argue that agent-native identity is a gating prerequisite, not a follow-on feature, and enumerate the flow assumptions that break.

Source video

Project ideas

4

Saturation Probe

beyond-evals

For an agentic code pipeline, there exists a measurable generation rate beyond which added generation throughput yields no net merged-change throughput because verification/rollback stages saturate, and that saturation point is predictable from verification-stage queue depth and test-suite latency before aggregate reliability metrics move.

Proof of concept

Instrument a synthetic pipeline with a controllable generation rate, a real test suite and merge/rollback gate, and a staged-rollout simulator; sweep generation rate upward and record merged-change throughput, reversion rate, and verification queue depth until net throughput plateaus or falls.

Measurement

Generation rate at which net merged-change throughput stops increasing; ratio of verification queue depth to generation rate at plateau; reversion rate and simulated incident rate per unit time at and past saturation.

Source video

Fleet Reconciler

movement-lab

A reconciliation-based scheduler (declared plan state + periodic convergence across ephemeral environments) recovers correctly from partial failures of individual dev boxes in a multi-day agent plan, whereas a single-loop sequential agent does not, and the difference is measurable in plan completion rate and duplicated/orphaned work.

Proof of concept

Build a minimal planner that emits a multi-step, multi-repository plan, a set of N ephemeral isolated environments, and a reconciler that hydrates state, detects lost environments, replays or reassigns their steps, and consolidates results; inject environment failures at random points.

Measurement

Plan completion rate and duplicate/orphaned work under injected failures versus a sequential single-loop baseline; recovery time after partial failure; durable state correctness after restart.

Source video

Attribution Splitter

new

The high-throughput, low-reversion outcome attributed to AI coding assistance is dominated by guardrail layers rather than the model: removing test suites, rollout gating, or isolation degrades reversion rate substantially more than swapping the generation model with a weaker one.

Proof of concept

Run a controlled matrix on a fixed repository: {strong model, weak model} x {full guardrails, no test suite, no progressive rollout, no isolation} on identical task sets; record throughput, reversion rate, and escaped-defect rate per cell.

Measurement

Per-cell reversion rate and escaped-defect rate; marginal effect size of each removed guardrail compared to the marginal effect of the model swap on throughput and reversion.

Source video

Agent Principal Kit

gatehouse

A delegated-authority identity scheme with per-action privilege scoping and explicit injection-boundary enforcement lets an agent complete provision-and-pay workflows without holding standing human-equivalent credentials, and it contains prompt-injection-driven unauthorized actions that a shared long-lived API key does not.

Proof of concept

Prototype non-human principals with scoped, time-bounded delegated grants over a provisioning API and a payment authorization API; run a red-team suite of prompt-injection payloads embedded in tool outputs and measure unauthorized action attempts that succeed.

Measurement

Count of unauthorized actions succeeding under scoped delegated grants versus a shared API key baseline; grant lifetime and scope breadth versus task completion rate.

Source video

Architectural implications

4

AI-assisted development at high velocity coexists with 5.5 nines of reliability only when isolation, observability, and progressive rollout are layered beneath it.

Before

Velocity and reliability treated as a direct trade-off, mediated by human review and release cadence.

After

Velocity scaled by infrastructure: ephemeral dev boxes, instrumentation, automated test suites, incremental rollout as the reliability boundary.

Consequence

Reliability engineering budget migrates from review gates toward environment and rollout tooling.

Source video

Agents orchestrate many parallel dev boxes over multi-day plans.

Before

Agents modeled as a single session with a bounded context and tool loop.

After

Agents modeled as schedulers over fleets of isolated environments with durable multi-day state.

Consequence

Need for result reconciliation, environment lifecycle management, and durable plan state as first-class runtime primitives.

Source video

Stripe rethinks signup, API usage, and payments for agents as counterparties.

Before

Account, auth, and payment flows assume a human principal.

After

Agent-native identity, delegated authority, and machine-to-machine payment authorization.

Consequence

API and payment schemas must be redesigned for non-human principals, and prompt injection protection becomes a boundary concern.

Source video

Claude Code patterns inspired an internal product (Stripe Projects) coupling code to logging, hosting, and database services.

Before

Coding assistant operates on text/code artifacts only.

After

Coding agent acts as a control plane for provisioning supporting services.

Consequence

Blurs boundary between authoring code and provisioning its runtime dependencies.

Source video

Tradeoffs and failure modes

3

AI-assisted merge velocity vs. per-unit-time incident rate

Benefit

Engineers can merge hundreds of PRs per hour with quality per PR rising over 18 months.

Cost or risk

Slight uptick in incident rate per unit time even as aggregate reliability and security metrics remain unchanged — higher volume means more absolute exposure events even at better per-change quality.

Quality per pull request has increased over the last 18 months despite a slight uptick in incident rate per unit time.
Open source video
Source video

Mass generation volume vs. verification burden

Benefit

An engineer merged over 600 PRs in an hour with AI assistance.

Cost or risk

Only one reversion — but the credibility of that outcome depends entirely on strong test suites and rollback infrastructure, so the failure mode is silent degradation when those guards are weak.

An engineer merging over 600 pull requests in one hour using AI assistance with only one reversion.
Open source video
Source video

Agent autonomy vs. security boundary

Benefit

Agents can autonomously execute multi-day, multi-environment engineering plans.

Cost or risk

Autonomous agents interacting with APIs and infrastructure create prompt-injection and delegated-authority exposure that must be explicitly defended.

prompt injection protection
Open source video
Source video

Open questions

5

What is the actual composition of the 'incident rate per unit time' uptick — clustered in specific subsystems, or uniformly distributed?

Why unresolved

The summary reports the uptick qualitatively without breakdown by service or change type.

Research direction

Segment incident data by subsystem, change class, and whether AI-generated vs. human-generated to locate where velocity outpaces guardrails.

Source video

How much of the 600-PR/hour result is attributable to the AI tool versus the pre-existing test, rollout, and observability infrastructure?

Why unresolved

The summary presents the result but does not isolate causal contributions.

Research direction

Run controlled comparisons of PR throughput and reversion rate with and without each guardrail layer.

Source video

What primitives does an agent runtime need to durably coordinate 10 parallel dev boxes across multi-day plans?

Why unresolved

The summary only states the orchestration happened, without describing state, reconciliation, or failure handling.

Research direction

Prototype a scheduler/reconciler abstraction for long-horizon multi-environment agent plans and measure recovery after partial failures.

Source video

What does agent-native identity, authorization, and payment look like when both transaction counterparties are agents?

Why unresolved

The summary frames this as a future direction Stripe is 'rethinking' without specifying mechanisms.

Research direction

Specify delegated-authority and machine-identity schemes usable at payment-rail scale.

Source video

Do the business-formation statistics reflect durable new firm creation or a spike of low-durability registrations?

Why unresolved

The summary reports upward trends in registrations and revenue thresholds but no cohort durability analysis.

Research direction

Cohort-track new businesses over time to distinguish durable formation from transient registration activity.

Source video

Key claims

8
factualVerification needed

Stripe runs core APIs at 5.5 nines of reliability while pursuing continuous deployment and rapid feature development.

Evidence

Stripe operates with 5.5 nines of reliability for core APIs while simultaneously attempting rapid feature development and continuous deployment.

Question

Is the 5.5-nines figure measured over a consistent window and does it apply to all core APIs or a subset?

Source video
causalVerification needed

Quality per pull request has risen over 18 months despite a slight increase in incident rate per unit time.

Evidence

Quality per pull request has increased over the last 18 months despite a slight uptick in incident rate per unit time.

Question

What metric operationalizes 'quality per pull request' and is the incident-rate uptick attributable to AI-generated changes?

Source video
factualVerification needed

An engineer at Stripe merged over 600 pull requests in one hour using AI assistance with only one reversion.

Evidence

An engineer merging over 600 pull requests in one hour using AI assistance with only one reversion.

Question

What was the content of those PRs (substantive vs. mechanical) and what definition of 'reversion' was applied?

Source video
causalVerification needed

AI agents let small teams compete with much larger teams by orchestrating complex plans across multiple codebases.

Evidence

AI agents enable small teams to compete against much larger teams by orchestrating complex plans across multiple codebases.

Question

Is this supported by measured output comparisons or anecdotal observation?

Source video
predictionVerification needed

Most future transactions will be between agents on both sides.

Evidence

In the future, most transactions will be between agents on both sides.

Question

What evidence or leading indicators support 'most transactions' versus a growing minority?

Source video
comparativeVerification needed

New business creation acceleration on Stripe is larger on a relative basis than any prior historical acceleration.

Evidence

The acceleration of new business creation on Stripe is on a relative basis much larger than any prior historical acceleration.

Question

Which historical baselines were used for the relative comparison and over what time windows?

Source video
factualVerification needed

Roughly a quarter of all US Delaware corporations are incorporated with Stripe.

Evidence

Stripe data indicating roughly a quarter of all US Delaware corporations are incorporated with Stripe.

Question

Does this include dormant entities or only actively transacting incorporations?

Source video
predictionVerification needed

Agent-to-agent transactions will create a massive vortex of agent-to-agent payments.

Evidence

Agent-to-agent transactions will create a massive vortex of agent-to-agent payments.

Question

What volume or growth signals currently indicate agent-originated payment activity?

Source video

Connections

5