From e7abc707aa70e91d81f92c9170bcacf2d82cdf23 Mon Sep 17 00:00:00 2001
From: juan leal <114959779+juandolealt@users.noreply.github.com>
Date: Thu, 16 Jul 2026 18:54:27 -0400
Subject: [PATCH] docs: complete Graphite organization profile

---
 profile/README.md | 48 +++++++++++++++++++++++++++++++++++++++--------
 1 file changed, 40 insertions(+), 8 deletions(-)

diff --git a/profile/README.md b/profile/README.md
index 6cb5e3f..08ef80d 100644
--- a/profile/README.md
+++ b/profile/README.md
@@ -13,16 +13,48 @@
 <br>
 <br>
 
-[Tempo](https://tempo.xyz/) is a payments-first Layer 1 blockchain incubated by Stripe and Paradigm, purpose-built for stablecoin payments at scale. Built with the [Reth SDK](https://github.com/paradigmxyz/reth), its architecture focuses on high throughput, low cost, and features that financial institutions, payment service providers, and fintech platforms expect from modern payment infrastructure.
+## What is Tempo?
+
+Tempo is a payments-first blockchain incubated by Stripe and Paradigm, purpose-built for stablecoins and real-world payments at scale.
+
+Tempo is EVM-compatible and built on Reth, the Ethereum execution client also maintained by the Tempo team. Smart contracts deploy with familiar tooling: Solidity, Foundry, Hardhat. The network is live on mainnet after a public testnet phase, with sub-second finality, gas fees payable in stablecoins, and an independent, diverse validator set as part of Tempo's roadmap toward permissionless validation.
+
+Tempo also powers the Machine Payments Protocol (MPP), an open standard for machine-to-machine payments co-authored by Stripe and Tempo. MPP runs on Tempo's settlement layer, letting AI agents pay for resources — APIs, data, compute — inline with a request, with no API keys or billing accounts required.
+
+## What makes Tempo different?
 
-What makes Tempo different?
 - **TempoTransaction:** Tempo includes a new EIP-2718 transaction type (0x76), providing features like passkey authentication, call batching, scheduled and parallel transactions, and fee sponsorship built natively into the protocol.
-- **TIP-20 token standard:** Enshrined stablecoin token standard optimized for payments and reconciliation.  
-- **Payment lanes:** Tempo ensures that payment transactions always have available blockspace, even during periods of high network congestion from DeFi activity. 
-- **Built with the Reth SDK:** High-performance, modular EVM execution layer under the hood powered by [Reth](https://github.com/paradigmxyz/reth).  
-- **Simplex consensus:** Optimized for low-latency, low-overhead finality under normal conditions.  
-- Fully [EVM-compatible](https://tempo.xyz/developers/docs/quickstart/evm-compatibility).
+- **TIP-20 token standard:** Enshrined stablecoin token standard optimized for payments and reconciliation.
+- **Predictable, low fees:** Gas is paid directly in USD-stablecoins via a built-in fee AMM, with TIP‑20 transfers targeting sub-millidollar costs.
+- **Payment lanes:** Tempo ensures that payment transactions always have available blockspace, even during periods of high network congestion from DeFi activity.
+- **Built with the Reth SDK:** High-performance, modular EVM execution layer under the hood powered by Reth.
+- **Simplex consensus:** Optimized for low-latency, low-overhead finality under normal conditions.
+- **Fully EVM-compatible.**
+
+## What is MPP?
+
+The Machine Payments Protocol (MPP) is an open standard for machine-to-machine payments, co-developed by Tempo and Stripe (with payment-method specs contributed by partners including Visa). It extends HTTP with a native 402 Payment Required flow, so any client — an AI agent, an app, or a person — can pay for a resource in the same request that asks for it, without API keys or checkout flows.
 
-To learn more, read the [Tempo documentation](https://tempo.xyz/developers/).
+MPP is payment-method agnostic — it supports Tempo, Stripe, and other rails through the same protocol — which is why it lives alongside Tempo's core repos rather than being Tempo-exclusive. Primary use cases include agentic payments (an AI agent paying per API call), usage-based billing, and machine-to-machine commerce.
+
+Learn more at [mpp.dev](https://mpp.dev/).
+
+## Start Building
+
+- [Quickstart](https://tempo.xyz/developers/docs/quickstart/integrate-tempo)
+- [Documentation](https://tempo.xyz/developers/)
+- [Tempo Overview](https://tempo.xyz/about/)
+- [SDKs](https://tempo.xyz/developers/docs/sdk)
+- [Machine Payments Protocol (MPP)](https://mpp.dev/)
 
 If you've found a security vulnerability in a Tempo project, please see [SECURITY.md](https://github.com/tempoxyz/.github?tab=security-ov-file).
+
+## Repositories
+
+| Category | Repositories |
+| --- | --- |
+| Core Infrastructure | [`tempo`](https://github.com/tempoxyz/tempo), [`zones`](https://github.com/tempoxyz/zones) |
+| SDKs | [`tempo-go`](https://github.com/tempoxyz/tempo-go), [`pympp`](https://github.com/tempoxyz/pympp), [`mpp-go`](https://github.com/tempoxyz/mpp-go), [`mpp-rs`](https://github.com/tempoxyz/mpp-rs), [`accounts`](https://github.com/tempoxyz/accounts) |
+| Protocols | [`mpp`](https://github.com/tempoxyz/mpp), [`mpp-specs`](https://github.com/tempoxyz/mpp-specs) |
+| Applications | [`tempo-apps`](https://github.com/tempoxyz/tempo-apps) |
+| Developer Tooling | [`wallet-cli`](https://github.com/tempoxyz/wallet-cli), [`tidx`](https://github.com/tempoxyz/tidx) |