Treasury operations

Agent Treasury Controls, 2026

A category report on how agent products should separate runtime spend policy, treasury approval, custody controls, and owner release.

8 live artifacts5 sample rows
  • Routine bounded spend should stay delegated and policy-enforced instead of constantly reopening finance review.
  • Wallet top-ups, rebalances, and payouts are authority-extending treasury actions and deserve stronger custody or finance ceremony.
  • The right split is between runtime policy, custody policy, treasury approval, and fresh owner step-up for scope release.
Machine payments

MPP vs x402 for Production Buyers, 2026

A buyer report on when teams should choose stateless paid HTTP, sessioned machine payments, or a billing layer around them.

8 live artifacts4 sample rows
  • One-shot paid requests and recurring machine subscriptions should be evaluated separately.
  • x402 is strongest for stateless request commerce; MPP is strongest when the session itself matters.
  • The real buyer question is how the stack handles retry, refill, and recovery, not just the first charge.
Wallet infrastructure

Embedded Wallets for Agent Products, 2026

A buyer report comparing embedded wallet surfaces for agent products through custody, policy, delegation, recovery, and operator control.

8 live artifacts4 sample rows
  • Embedded wallet UX and real custody or policy guarantees are not the same thing.
  • The strongest buyer question is which layer owns delegation, approval, recovery, and auditability in practice.
  • Wallet reports are most useful when they help operators rule vendors out quickly, not when they celebrate every surface equally.
Workflow governance

Agent Approvals and Human Leashes, 2026

A category report on how human approval, delegation windows, renewal, and runtime leash enforcement should work in serious agent systems.

8 live artifacts4 sample rows
  • Approval should be modeled by workflow stage, not treated as one global yes or no.
  • Human leashes should be time-bounded, scope-bounded, and checked at runtime, not just at creation time.
  • The real design tradeoff is preserving human authority without forcing operators to re-approve every harmless step.
Recurring payments

Stablecoin Subscription Rails for Agents, 2026

A narrower category report on which stablecoin and machine-payment stacks actually work for recurring agent subscriptions.

8 live artifacts4 sample rows
  • One-shot and recurring payment rails solve different problems and should be evaluated separately.
  • MPP-style sessioned flows look strongest for repeated machine runs, while x402 is strongest for stateless one-shot access.
  • The right subscription question is how the stack handles retry, refill, and recovery, not just the first charge.
Partner intelligence

Tempo Ecosystem Partner Map, H2 2026

A forward-looking partner watchmap ranking the ecosystem names that matter most to Tempo by lane density, repeated mention share, and monitoring value.

8 live artifacts5 sample rows
  • The next partner map should rank by lane density and repeated mention share, not just logo presence.
  • A stronger H2 watchlist separates core partner surfaces from narrative adjacency and launch theater.
  • This slug is a live watchmap for H2 2026, not a fake retrospective pretending the future is already settled.
Market positioning

Tempo, x402, and the MCP Commerce Stack

A positioning report on how Tempo, x402, and MCP-related commerce surfaces fit together across agent tooling, paid HTTP, and operator-facing product layers.

7 live artifacts5 sample rows
  • MCP handles tool and context connectivity, x402 handles the paid HTTP handshake, and Tempo plus MPP handle settlement-oriented machine-payment flows.
  • As of March 21, 2026, public bridge patterns like x402-aware MCP servers show these layers composing in production instead of replacing one another.
  • Buyers should evaluate the stack in order: discovery and tool interface, payment trigger, then settlement and operator controls.
Infrastructure map

Stablecoin Rails for Agents, 2026

A deep map of stablecoin payment rails for AI agents across custody, identity, settlement, retries, wallet infrastructure, compliance edges, and operator tradeoffs.

7 live artifacts5 sample rows
  • No single stablecoin rail solves agent payments end to end; teams compose custody, identity, payment negotiation, settlement, and compliance controls.
  • As of March 21, 2026, x402 is strongest for stateless paid HTTP, MPP is strongest for session-based machine payments, and wallet vendors shape the real custody and policy surface.
  • The practical decision is not which protocol wins in theory, but which custody-plus-settlement stack keeps retries, key risk, and compliance overhead inside acceptable bounds.
Partner intelligence

Tempo Partner Map, Q1 2026

A scoped map of the partner lanes, infrastructure surfaces, and launch-adjacent names appearing most often in Temporal's Tempo coverage.

Preview only4 sample rows
  • Maps the partner and infrastructure names most repeatedly tied to the current Tempo launch narrative.
  • Separates direct Tempo-adjacent evidence from broader ecosystem framing so the report can stay honest about confidence.
  • Uses a stable slug so future refresh runs can update the same product without collapsing back into the nightly brief.

Archive search

Find the report that already covers the issue

Search also lives at /api/reports/search.