{"artifact":{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/json","byteLength":29566,"description":"Structured partner rows, source mappings, and monitoring metrics for downstream agents.","format":"json","label":"Full machine-readable JSON","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"91264ba2df299ee17853e8436ee6b2851bba218c9d3c35e22cf640f98b5c55c1","status":"live"},"document":{"artifacts":[{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/markdown","byteLength":13150,"description":"Human-readable dossier with lane-by-lane partner framing, rankings, and appendix.","format":"markdown","label":"Full markdown report","mimeType":"text/markdown; charset=utf-8","priceUsdc":0,"sha256":"25bd5d02a5ad2cab8d5d1c9246e95185ea2256395242eb6f7f5d4ae9707a796c","status":"live"},{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/json","byteLength":null,"description":"Structured partner rows, source mappings, and monitoring metrics for downstream agents.","format":"json","label":"Full machine-readable JSON","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":null,"status":"live"},{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/charts","byteLength":3097,"description":"Structured chart payload backing the inline report visuals and machine-readable consumers.","format":"charts","label":"Chart data artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"36750ac3d40636f3d59c1cdb5cc27ecc313ad615f4562cf840629158e0e6bdf4","status":"live"},{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/definition","byteLength":2745,"description":"Saved report definition artifact.","format":"definition","label":"Definition artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"0f8b785430f0322cf0cea3ab44742c0fce209ffe6b076f732b677039df2949e0","status":"live"},{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/evidence","byteLength":7028,"description":"Structured evidence ledger tying claims and chart provenance back to cited sources.","format":"evidence","label":"Evidence artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"d11f67ef6dddb302342697d6a9e9a5f502d804e0adb3a58a17ac4c090a84ffd9","status":"live"},{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/methodology","byteLength":1143,"description":"Structured methodology notes, dataset summary, and report timing metadata.","format":"methodology","label":"Methodology artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"dfa7b4e58e7d90f29db6db4879122bbb8116349d500df0ea73ca3f249dade398","status":"live"},{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/sources","byteLength":3217,"description":"Structured source ledger with source kinds, labels, notes, and URLs.","format":"sources","label":"Sources artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"d449fe7fc7dd090194dc23561a790d0651f6ab5513923f404c2a94ba9dc704f2","status":"live"},{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/bundle","byteLength":null,"description":"Single purchase target returning the markdown report, JSON artifact, and manifest together.","format":"bundle","label":"Combined report bundle","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":null,"status":"live"}],"charts":[{"caption":"The strongest public density is not in one generic partner bucket. It clusters around service discovery, wallet control, payment reach, and enterprise workload demand.","chartType":"bar","points":[{"label":"Wallet control and custody","note":"Privy, Turnkey, Crossmint, and Fireblocks provide the signer, policy, or custody surfaces operators actually have to inspect.","values":[4]},{"label":"Payment protocol and checkout","note":"Stripe, Visa, Lightspark, and Crossmint shape how Tempo reaches cards, Lightning, and merchant distribution.","values":[4]},{"label":"Service discovery and data","note":"Tempo's public launch names Alchemy, Dune Analytics, Merit Systems, and Parallel Web Systems, while Allium adds a Tempo-specific data recipe surface.","values":[5]},{"label":"Enterprise workloads and distribution","note":"Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and similar names are strongest as demand and credibility signals.","values":[9]}],"series":["tracked names"],"title":"Where the documented Tempo partner density is actually accumulating","unit":"tracked names"},{"caption":"Core watch names are not just mentioned once. They recur either on both sides of the ecosystem boundary or across multiple partner-owned public surfaces.","chartType":"bar","points":[{"label":"Stripe","note":"Tempo names Stripe directly in the MPP launch, and Stripe publishes the machine-payments support matrix.","values":[1,1]},{"label":"Privy","note":"Privy has both an MPP integration recipe and a Tempo-specific integration post.","values":[0,2]},{"label":"Crossmint","note":"Crossmint has both AI-agent docs and a protocol comparison that treats MPP as a live route.","values":[0,2]},{"label":"Alchemy","note":"Tempo names Alchemy in the launch directory, and Alchemy publishes an MPP versus x402 buyer explainer.","values":[1,1]},{"label":"Turnkey","note":"Turnkey is strong on wallet-control docs but still thinner on Tempo-specific public evidence.","values":[0,1]},{"label":"Allium","note":"Allium exposes Tempo recipes, making it more than generic analytics adjacency.","values":[0,1]}],"series":["Tempo-owned evidence","partner-owned evidence"],"title":"Which names already have multi-surface public evidence","unit":"evidence surfaces"}],"chartsArtifact":{"byteLength":3097,"fileName":"charts.json","format":"charts","mimeType":"application/json; charset=utf-8","sha256":"36750ac3d40636f3d59c1cdb5cc27ecc313ad615f4562cf840629158e0e6bdf4"},"definition":{"audience":null,"authoredAt":"1970-01-01T00:00:00.000Z","authoredByUserId":null,"chartPlan":[],"dateAnchor":"March 22, 2026","datasetWindow":"H2 2026 watchlist","deepResearchPrompts":[{"id":"partner_watchmap_memo","purpose":"Produce a citation-heavy H2 2026 partner watchmap for Tempo.","model":"sonar-deep-research","maxTokens":7000,"prompt":"As of March 22, 2026, produce a citation-heavy partner watchmap for Tempo focused on H2 2026 monitoring. Rank ecosystem names by lane density, repeated mention share, and operational relevance across wallet control, payments, funding, compliance, and distribution. Distinguish direct Tempo-adjacent evidence from broader ecosystem adjacency, and end with a clear split between core watchlist names, secondary names, and narrative-adjacent names."}],"deepResearchPromptCount":1,"evidenceRequirements":[],"freshnessExpectation":null,"generatedAt":"1970-01-01T00:00:00.000Z","notes":[],"officialDomainHints":["tempo.xyz","docs.stripe.com","bridge.xyz","privy.io","turnkey.com","crossmint.com","fireblocks.com","circle.com"],"reportPromptGuidance":["Treat this as a forward-looking H2 2026 watchmap, not a retrospective pretending the future is already settled.","Rank partners by lane density, repeated mention share, and monitoring value rather than logo count alone.","Separate direct Tempo evidence from broader adjacency so the confidence model stays honest.","Keep the analysis operational by focusing on wallet control, payment flow, funding, compliance, and distribution lanes.","End with a clear watchlist split across core, secondary, and narrative-adjacent names."],"searchQueries":[{"id":"tempo_partner_surfaces","purpose":"Collect Tempo-adjacent partner and launch-surface evidence.","query":"Tempo ecosystem partners launch wallet payments stablecoin identity 2026","maxResults":10,"maxTokens":2200},{"id":"wallet_identity_lane_density","purpose":"Track wallet and identity partners with repeated relevance.","query":"Tempo partner wallet identity embedded wallets Privy Turnkey Crossmint 2026","maxResults":10,"maxTokens":2200},{"id":"payments_treasury_lane_density","purpose":"Track payment, treasury, and stablecoin infrastructure lanes.","query":"Tempo payments treasury stablecoin partners Bridge Stripe Circle 2026","maxResults":10,"maxTokens":2200},{"id":"distribution_and_adjacency","purpose":"Separate core monitoring targets from broader ecosystem adjacency.","query":"Tempo ecosystem distribution partners adjacency launch watchlist 2026","maxResults":10,"maxTokens":2200}],"sectionPlan":[],"slug":"tempo-ecosystem-partner-map-h2-2026","title":"Tempo Ecosystem Partner Map, H2 2026","topic":"tempo ecosystem partner map h2","versionId":"seed_tempo-ecosystem-partner-map-h2-2026"},"definitionArtifact":{"byteLength":2745,"fileName":"definition.json","format":"definition","mimeType":"application/json; charset=utf-8","sha256":"0f8b785430f0322cf0cea3ab44742c0fce209ffe6b076f732b677039df2949e0"},"dataset":{"sampleRows":[{"partner":"Stripe","lane":"payment protocol and merchant distribution","status":"core","confidence":"high","whyItMatters":"MPP is co-authored with Stripe, and Stripe's own machine-payments matrix is the clearest merchant-side distribution surface in the current public set."},{"partner":"Privy","lane":"wallet control and machine payments","status":"core","confidence":"high","whyItMatters":"Privy publishes both an MPP integration recipe and a Tempo-specific integration blog, making it one of the clearest wallet-policy watch names."},{"partner":"Alchemy","lane":"service discovery and developer infrastructure","status":"core","confidence":"medium","whyItMatters":"Alchemy appears in Tempo's launch-time payments directory and publishes one of the clearest MPP-versus-x402 buyer explainers."},{"partner":"Allium","lane":"data and verification","status":"secondary","confidence":"medium","whyItMatters":"Tempo-specific recipes give Allium a more concrete monitoring role than a generic analytics logo would imply."},{"partner":"Anthropic","lane":"enterprise workload demand","status":"adjacent","confidence":"medium","whyItMatters":"Important as workload validation and demand-side signal, but still not the place where operators should expect Tempo integration details to break first."}],"summary":{"trackedPartners":21,"partnerLanes":4,"sampleRows":5,"searchQueries":4,"window":"H2 2026 watchlist"}},"evidence":{"chartProvenance":[{"chartTitle":"Where the documented Tempo partner density is actually accumulating","sourceLabels":["Tempo Mainnet launch","Tempo docs","MPP services directory","Turnkey embedded wallet guide","Crossmint AI agents introduction","Fireblocks overview"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://docs.tempo.xyz","https://mpp.dev/services","https://docs.turnkey.com/production-checklist/embedded-wallet","https://docs.crossmint.com/solutions/ai-agents/introduction","https://developers.fireblocks.com/docs/overview"],"whyUseful":"Shows which lanes deserve real H2 monitoring instead of flattening every partner into one undifferentiated ecosystem list."},{"chartTitle":"Which names already have multi-surface public evidence","sourceLabels":["Tempo Mainnet launch","Stripe machine payments","Privy MPP integration recipe","Privy on Tempo MPP","Crossmint AI agents introduction","Crossmint protocols compared","Alchemy x402 vs MPP","Allium Tempo recipes"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://docs.stripe.com/payments/machine","https://docs.privy.io/recipes/agent-integrations/mpp","https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol","https://docs.crossmint.com/solutions/ai-agents/introduction","https://www.crossmint.com/learn/agentic-payments-protocols-compared","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols","https://github.com/Allium-Science/allium-recipes/tree/main/tempo"],"whyUseful":"Separates core watch names from weaker adjacency by showing which partners recur across direct Tempo evidence and partner-owned public surfaces."}],"claims":[{"chartTitles":["Where the documented Tempo partner density is actually accumulating"],"confidence":"high","id":"lane-density-clusters","kind":"chart","section":"Lane density","sourceLabels":["Tempo Mainnet launch","Tempo docs","MPP services directory","Turnkey embedded wallet guide","Crossmint AI agents introduction","Fireblocks overview"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://docs.tempo.xyz","https://mpp.dev/services","https://docs.turnkey.com/production-checklist/embedded-wallet","https://docs.crossmint.com/solutions/ai-agents/introduction","https://developers.fireblocks.com/docs/overview"],"statement":"The strongest publicly documented Tempo partner density now clusters around service discovery and data, wallet control, payment distribution, and enterprise workload demand rather than one generic ecosystem bucket."},{"chartTitles":["Which names already have multi-surface public evidence"],"confidence":"high","id":"stripe-core-watch","kind":"finding","section":"Core watchlist","sourceLabels":["Tempo Mainnet launch","Stripe machine payments"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://docs.stripe.com/payments/machine"],"statement":"Stripe belongs on the core watchlist because it sits in both Tempo's MPP launch story and Stripe's own machine-payments distribution surface."},{"chartTitles":["Which names already have multi-surface public evidence"],"confidence":"high","id":"wallet-control-core","kind":"comparison","section":"Core watchlist","sourceLabels":["Privy MPP integration recipe","Privy on Tempo MPP","Turnkey embedded wallet guide","Crossmint AI agents introduction","Crossmint protocols compared"],"sourceUrls":["https://docs.privy.io/recipes/agent-integrations/mpp","https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol","https://docs.turnkey.com/production-checklist/embedded-wallet","https://docs.crossmint.com/solutions/ai-agents/introduction","https://www.crossmint.com/learn/agentic-payments-protocols-compared"],"statement":"Privy, Turnkey, and Crossmint deserve sustained monitoring because wallet-control and delegated-spend surfaces are as important as settlement infrastructure in the Tempo stack."},{"chartTitles":["Which names already have multi-surface public evidence"],"confidence":"medium","id":"alchemy-allium-data-lane","kind":"comparison","section":"Secondary watchlist","sourceLabels":["Tempo Mainnet launch","Alchemy x402 vs MPP","Allium Tempo recipes"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols","https://github.com/Allium-Science/allium-recipes/tree/main/tempo"],"statement":"Alchemy and Allium matter because service-discovery and analytics lanes are becoming a real part of the Tempo ecosystem surface, not just an afterthought around the chain."},{"chartTitles":[],"confidence":"high","id":"design-partners-not-core-integrations","kind":"finding","section":"Narrative-adjacent names","sourceLabels":["Tempo Mainnet launch"],"sourceUrls":["https://tempo.xyz/blog/mainnet"],"statement":"Large design-partner names such as Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, and Standard Chartered validate demand, but they should not all be treated as first-order integration depth until more public implementation detail appears."},{"chartTitles":[],"confidence":"medium","id":"fireblocks-secondary-governance","kind":"finding","section":"Secondary watchlist","sourceLabels":["Fireblocks overview"],"sourceUrls":["https://developers.fireblocks.com/docs/overview"],"statement":"Fireblocks is a strong secondary watch name because custody and governance become materially more relevant if Tempo grows into treasury-heavy enterprise payment deployments."}],"generatedAt":"2026-03-23T00:00:00.000Z","slug":"tempo-ecosystem-partner-map-h2-2026","summary":{"chartBackedClaimCount":3,"claimCount":6,"ecosystemSourceCount":4,"officialSourceCount":8,"totalSourceCount":12},"title":"Tempo Ecosystem Partner Map, H2 2026"},"evidenceArtifact":{"byteLength":7028,"fileName":"evidence.json","format":"evidence","mimeType":"application/json; charset=utf-8","sha256":"d11f67ef6dddb302342697d6a9e9a5f502d804e0adb3a58a17ac4c090a84ffd9"},"findings":["The strongest public Tempo partner density now sits in service discovery and data lanes, wallet control surfaces, and payment distribution rather than one generic launch bucket.","Stripe, Privy, Turnkey, Crossmint, Alchemy, and Visa deserve the core watchlist because they shape either direct payment reach or the wallet and control model around Tempo.","Secondary names like Fireblocks, Allium, Dune, Merit Systems, Parallel Web Systems, and Lightspark matter operationally, but the public evidence base is still thinner than the core group.","Large design-partner names validate demand, but they should not all be treated as first-order integration risk until they expose clearer public build or deployment surfaces."],"markdownArtifact":{"apiPath":"/api/reports/tempo-ecosystem-partner-map-h2-2026/markdown","byteLength":13150,"description":"Human-readable dossier with lane-by-lane partner framing, rankings, and appendix.","format":"markdown","label":"Full markdown report","mimeType":"text/markdown; charset=utf-8","priceUsdc":0,"sha256":"25bd5d02a5ad2cab8d5d1c9246e95185ea2256395242eb6f7f5d4ae9707a796c","status":"live"},"markdownAvailable":true,"methodologyArtifact":{"byteLength":1143,"fileName":"methodology.json","format":"methodology","mimeType":"application/json; charset=utf-8","sha256":"dfa7b4e58e7d90f29db6db4879122bbb8116349d500df0ea73ca3f249dade398"},"methodology":["Anchored the report in Tempo's March 18, 2026 mainnet launch, Tempo docs, the MPP services directory, and partner-owned wallet and payment documentation published through March 23, 2026.","Ranked names by lane density and evidence breadth rather than logo count, with direct Tempo evidence weighted above generic ecosystem adjacency.","Separated core watch names from secondary and narrative-adjacent names so design-partner demand signals do not get confused with integration depth.","Preferred operator monitoring value over launch theater: the key question is which names define wallet control, payment reach, data visibility, or enterprise workload demand."],"outline":[{"id":"tempo-ecosystem-partner-map-h2-2026","level":1,"text":"Tempo Ecosystem Partner Map, H2 2026"},{"id":"a-useful-partner-map-starts-with-lane-density","level":2,"text":"A Useful Partner Map Starts With Lane Density"},{"id":"core-watchlist-the-names-that-define-the-stack-shape","level":2,"text":"Core Watchlist: The Names That Define The Stack Shape"},{"id":"stripe","level":3,"text":"Stripe"},{"id":"privy","level":3,"text":"Privy"},{"id":"turnkey","level":3,"text":"Turnkey"},{"id":"crossmint","level":3,"text":"Crossmint"},{"id":"alchemy","level":3,"text":"Alchemy"},{"id":"visa","level":3,"text":"Visa"},{"id":"secondary-watchlist-strong-single-lane-names","level":2,"text":"Secondary Watchlist: Strong Single-Lane Names"},{"id":"fireblocks","level":3,"text":"Fireblocks"},{"id":"allium","level":3,"text":"Allium"},{"id":"dune-analytics-merit-systems-and-parallel-web-systems","level":3,"text":"Dune Analytics, Merit Systems, and Parallel Web Systems"},{"id":"lightspark","level":3,"text":"Lightspark"},{"id":"narrative-adjacent-names-still-matter-but-they-are-not-core","level":2,"text":"Narrative-Adjacent Names Still Matter, But They Are Not Core"},{"id":"recommendations-by-buyer-type","level":2,"text":"Recommendations By Buyer Type"},{"id":"if-you-are-evaluating-tempo-as-a-builder","level":3,"text":"If you are evaluating Tempo as a builder"},{"id":"if-you-are-a-service-or-data-seller","level":3,"text":"If you are a service or data seller"},{"id":"if-you-are-using-the-partner-map-as-a-credibility-check","level":3,"text":"If you are using the partner map as a credibility check"},{"id":"bottom-line","level":2,"text":"Bottom Line"}],"previewMarkdown":"# Tempo Ecosystem Partner Map, H2 2026\n\n## Scope\n\n- A forward-looking partner watchmap for the next Tempo cycle\n- Built to rank partners by lane density, repeated mention share, and monitoring value\n- Intended to separate core partner surfaces from narrative adjacency\n\n## What the preview shows\n\n- The next Tempo partner map should rank by lane density and repeated mention share, not just list names.\n- A stronger H2 watchlist separates partners that matter to wallet control, payment flow, funding, compliance, and distribution from names that are mainly narrative adjacency.\n- This slug is a live watchmap for H2 2026, not a fake retrospective pretending the future is already settled.\n\n## Why this slug exists\n\nThe Q1 partner map proved the category shape. This follow-up should be the durable watch surface: the place where core, secondary, and narrative-adjacent names are tracked with clearer scoring and a better artifact package.\n","report":{"category":"Partner intelligence","datasetSummary":{"trackedPartners":21,"partnerLanes":4,"sampleRows":5,"searchQueries":4,"window":"H2 2026 watchlist"},"featureKey":"deep_reports_tempo_ecosystem_partner_map_h2_2026","findings":["The strongest public Tempo partner density now sits in service discovery and data lanes, wallet control surfaces, and payment distribution rather than one generic launch bucket.","Stripe, Privy, Turnkey, Crossmint, Alchemy, and Visa deserve the core watchlist because they shape either direct payment reach or the wallet and control model around Tempo.","Secondary names like Fireblocks, Allium, Dune, Merit Systems, Parallel Web Systems, and Lightspark matter operationally, but the public evidence base is still thinner than the core group.","Large design-partner names validate demand, but they should not all be treated as first-order integration risk until they expose clearer public build or deployment surfaces."],"methodology":["Anchored the report in Tempo's March 18, 2026 mainnet launch, Tempo docs, the MPP services directory, and partner-owned wallet and payment documentation published through March 23, 2026.","Ranked names by lane density and evidence breadth rather than logo count, with direct Tempo evidence weighted above generic ecosystem adjacency.","Separated core watch names from secondary and narrative-adjacent names so design-partner demand signals do not get confused with integration depth.","Preferred operator monitoring value over launch theater: the key question is which names define wallet control, payment reach, data visibility, or enterprise workload demand."],"previewBullets":["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."],"publishedAt":"2026-03-23T00:00:00.000Z","sampleRows":[{"partner":"Stripe","lane":"payment protocol and merchant distribution","status":"core","confidence":"high","whyItMatters":"MPP is co-authored with Stripe, and Stripe's own machine-payments matrix is the clearest merchant-side distribution surface in the current public set."},{"partner":"Privy","lane":"wallet control and machine payments","status":"core","confidence":"high","whyItMatters":"Privy publishes both an MPP integration recipe and a Tempo-specific integration blog, making it one of the clearest wallet-policy watch names."},{"partner":"Alchemy","lane":"service discovery and developer infrastructure","status":"core","confidence":"medium","whyItMatters":"Alchemy appears in Tempo's launch-time payments directory and publishes one of the clearest MPP-versus-x402 buyer explainers."},{"partner":"Allium","lane":"data and verification","status":"secondary","confidence":"medium","whyItMatters":"Tempo-specific recipes give Allium a more concrete monitoring role than a generic analytics logo would imply."},{"partner":"Anthropic","lane":"enterprise workload demand","status":"adjacent","confidence":"medium","whyItMatters":"Important as workload validation and demand-side signal, but still not the place where operators should expect Tempo integration details to break first."}],"slug":"tempo-ecosystem-partner-map-h2-2026","sources":[{"kind":"official","label":"Tempo Mainnet launch","note":"March 18, 2026 launch post naming MPP extensions, payments-directory services, and enterprise design partners.","url":"https://tempo.xyz/blog/mainnet"},{"kind":"official","label":"Tempo docs","note":"Official developer docs for wallets, payments, and machine-payment flows on Tempo.","url":"https://docs.tempo.xyz"},{"kind":"official","label":"MPP services directory","note":"Public MPP discovery surface showing how Tempo expects agents to find paid services.","url":"https://mpp.dev/services"},{"kind":"official","label":"Stripe machine payments","note":"Support matrix covering MPP on Tempo and x402 on other rails, useful for partner-distribution scoring.","url":"https://docs.stripe.com/payments/machine"},{"kind":"official","label":"Privy MPP integration recipe","note":"Partner-owned documentation for building agent payment flows on Tempo with Privy wallets.","url":"https://docs.privy.io/recipes/agent-integrations/mpp"},{"kind":"official","label":"Turnkey embedded wallet guide","note":"Operational wallet-control guide covering app-controlled, delegated, and shared-custody models.","url":"https://docs.turnkey.com/production-checklist/embedded-wallet"},{"kind":"official","label":"Crossmint AI agents introduction","note":"Crossmint's product surface for agent wallets and payment orchestration.","url":"https://docs.crossmint.com/solutions/ai-agents/introduction"},{"kind":"official","label":"Fireblocks overview","note":"Institutional custody and governance surface useful for treasury-heavy Tempo deployments.","url":"https://developers.fireblocks.com/docs/overview"},{"kind":"ecosystem","label":"Privy on Tempo MPP","note":"Tempo-specific partner blog explaining how Privy wallets fit MPP sessions and bounded machine spend.","url":"https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol"},{"kind":"ecosystem","label":"Crossmint protocols compared","note":"Crossmint comparison framing MPP, x402, and multi-rail agent commerce from a unified wallet perspective.","url":"https://www.crossmint.com/learn/agentic-payments-protocols-compared"},{"kind":"ecosystem","label":"Alchemy x402 vs MPP","note":"Buyer-oriented comparison useful for understanding why Alchemy belongs in the watchlist.","url":"https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"},{"kind":"ecosystem","label":"Allium Tempo recipes","note":"Tempo-specific analytics recipes that make Allium a concrete data and verification watch name.","url":"https://github.com/Allium-Science/allium-recipes/tree/main/tempo"}],"subtitle":"Built as a monitoring surface for wallet control, payment distribution, data lanes, and enterprise demand instead of a stretched launch collage.","summary":"A forward-looking partner watchmap ranking the ecosystem names that matter most to Tempo by lane density, repeated mention share, and monitoring value.","tags":["tempo","ecosystem","partners","watchlist","distribution"],"title":"Tempo Ecosystem Partner Map, H2 2026","updatedAt":"2026-03-23T00:00:00.000Z"},"sourcesArtifact":null,"sources":[{"kind":"official","label":"Tempo Mainnet launch","note":"March 18, 2026 launch post naming MPP extensions, payments-directory services, and enterprise design partners.","url":"https://tempo.xyz/blog/mainnet"},{"kind":"official","label":"Tempo docs","note":"Official developer docs for wallets, payments, and machine-payment flows on Tempo.","url":"https://docs.tempo.xyz"},{"kind":"official","label":"MPP services directory","note":"Public MPP discovery surface showing how Tempo expects agents to find paid services.","url":"https://mpp.dev/services"},{"kind":"official","label":"Stripe machine payments","note":"Support matrix covering MPP on Tempo and x402 on other rails, useful for partner-distribution scoring.","url":"https://docs.stripe.com/payments/machine"},{"kind":"official","label":"Privy MPP integration recipe","note":"Partner-owned documentation for building agent payment flows on Tempo with Privy wallets.","url":"https://docs.privy.io/recipes/agent-integrations/mpp"},{"kind":"official","label":"Turnkey embedded wallet guide","note":"Operational wallet-control guide covering app-controlled, delegated, and shared-custody models.","url":"https://docs.turnkey.com/production-checklist/embedded-wallet"},{"kind":"official","label":"Crossmint AI agents introduction","note":"Crossmint's product surface for agent wallets and payment orchestration.","url":"https://docs.crossmint.com/solutions/ai-agents/introduction"},{"kind":"official","label":"Fireblocks overview","note":"Institutional custody and governance surface useful for treasury-heavy Tempo deployments.","url":"https://developers.fireblocks.com/docs/overview"},{"kind":"ecosystem","label":"Privy on Tempo MPP","note":"Tempo-specific partner blog explaining how Privy wallets fit MPP sessions and bounded machine spend.","url":"https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol"},{"kind":"ecosystem","label":"Crossmint protocols compared","note":"Crossmint comparison framing MPP, x402, and multi-rail agent commerce from a unified wallet perspective.","url":"https://www.crossmint.com/learn/agentic-payments-protocols-compared"},{"kind":"ecosystem","label":"Alchemy x402 vs MPP","note":"Buyer-oriented comparison useful for understanding why Alchemy belongs in the watchlist.","url":"https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"},{"kind":"ecosystem","label":"Allium Tempo recipes","note":"Tempo-specific analytics recipes that make Allium a concrete data and verification watch name.","url":"https://github.com/Allium-Science/allium-recipes/tree/main/tempo"}]},"generatedAt":"2026-05-04T00:13:26.162Z","kind":"deep_report_json","operatorAccess":null,"payer":null}