Daily preview

March 20, 2026

Published from run_cycle_v0 in live mode.

Executive summary

TEMPO SIGNAL Daily Brief

Tempo's mainnet launch is the dominant official anchor for the current research set. The highest-signal page confirms that Tempo mainnet went live on 2026-03-18 alongside the Machine Payments Protocol, a payments directory with more than 100 services, and a partner narrative centered on real payment workloads rather than general-purpose chain activity.

The strongest product signal is that Tempo is framing itself around four concrete enterprise payment lanes: global payouts, cross-border remittances, embedded finance, and tokenized deposits. The strongest agentic-commerce signal is that MPP sessions aggregate many small machine payments into a single settlement flow, which makes pay-per-use APIs and multi-service agent workflows economically viable.

Distilled signals

Key takeaways from this issue

Signal 01

Mainnet + MPP launch

Tempo mainnet and MPP launched together on 2026-03-18, positioning MPP as the native machine-payments layer on top of Tempo settlement.

Signal 02

Directory depth

the payments directory launched with 100+ services, which is a stronger ecosystem bootstrap signal than a docs-only release.

Signal 03

Design partner density

official launch materials name Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa.

Signal 04

Payment workload focus

Tempo is emphasizing global payouts, remittances, embedded finance, and tokenized deposits as the main real-world workload categories.

Signal 05

Key primitives

official docs and launch content repeatedly point to smart accounts, memos, payment lanes, stablecoin-native fee design, and MPP sessions as the differentiating stack.

Research notes

How this was assembled

  • Query quality was materially better after narrowing to official domains only: `tempo.xyz`, `docs.tempo.xyz`, and `mpp.dev`.
  • Result quality is now high on relevance but still imperfect on uniqueness. The same official pages appeared in slash and non-slash variants, and blog index pages still showed up.
  • A watchlist-driven ecosystem query also stayed on official domains, but it still over-indexed on generic Tempo surfaces instead of partner-specific pages.
  • The best next refinement is to drill into one partner or one partner bucket at a time, rather than querying six ecosystem names in one shot.
  • The best current source anchors are:
  • `https://tempo.xyz/blog/mainnet`
  • `https://docs.tempo.xyz`
  • `https://mpp.dev/services`

Next build step

What the system should improve next

Implement canonical URL dedupe plus page-type scoring so TEMPO SIGNAL promotes leaf docs and launch posts over duplicated index pages before report synthesis.