diff --git a/bun.lockb b/bun.lockb
index 3946eddd..7bdb33b8 100755
Binary files a/bun.lockb and b/bun.lockb differ
diff --git a/src/pages/cli/wallet.mdx b/src/pages/cli/wallet.mdx
index 85dc2dff..bae71361 100644
--- a/src/pages/cli/wallet.mdx
+++ b/src/pages/cli/wallet.mdx
@@ -192,7 +192,7 @@ tempo wallet sessions close --orphaned
/>
diff --git a/src/pages/guide/machine-payments/index.mdx b/src/pages/guide/machine-payments/index.mdx
index e9b89a10..b6984474 100644
--- a/src/pages/guide/machine-payments/index.mdx
+++ b/src/pages/guide/machine-payments/index.mdx
@@ -1,15 +1,15 @@
---
-title: Machine Payments
-description: Charge for APIs, MCP tools, and digital content using the Machine Payments Protocol (MPP) on Tempo with TIP-20 stablecoins.
+title: Agentic Payments
+description: Make agentic payments using the Machine Payments Protocol (MPP) on Tempo — charge for APIs, MCP tools, and digital content with TIP-20 stablecoins.
---
import { Card, Cards } from 'vocs'
import { MermaidDiagram } from '../../../components/MermaidDiagram'
import { TerminalDemo } from '../../../components/TerminalDemo'
-# Make Machine Payments
+# Make Agentic Payments
-The [Machine Payments Protocol](https://mpp.dev) (MPP) adds inline payments to any HTTP endpoint. Clients — apps, agents, or humans — pay as part of their request, and the server verifies payment before returning the response.
+Make agentic payments using the [Machine Payments Protocol](https://mpp.dev) (MPP). MPP adds inline payments to any HTTP endpoint — agents, apps, or humans pay as part of their request, and the server verifies payment before returning the response.
## Try it out
@@ -42,7 +42,7 @@ A client requests a paid resource, the server responds with `402` and a `Challen
## Why Tempo
-Tempo's transaction model is explicitly designed for inline payments using MPP:
+Tempo's transaction model is designed for agentic payments using MPP:
- **~500ms finality** — Deterministic confirmation fast enough for synchronous request/response flows
- **Sub-cent fees** — Low enough for micropayments and per-request billing
diff --git a/src/pages/guide/machine-payments/use-cases/monetize-your-api.mdx b/src/pages/guide/machine-payments/use-cases/monetize-your-api.mdx
index 2c286d30..ad3d5412 100644
--- a/src/pages/guide/machine-payments/use-cases/monetize-your-api.mdx
+++ b/src/pages/guide/machine-payments/use-cases/monetize-your-api.mdx
@@ -1,11 +1,11 @@
---
-title: Monetize Your API with Machine Payments
+title: Monetize Your API with Agentic Payments
description: Accept stablecoin payments for your API using MPP on Tempo. Charge per request without requiring signups, billing accounts, or API keys.
---
import { Card, Cards } from 'vocs'
-# Monetize your API with machine payments
+# Monetize your API with agentic payments
Accept stablecoin payments for any HTTP endpoint. No signup flows, no billing accounts, no API key management. Your users — agents, apps, or humans — pay per request with stablecoins on Tempo, and you get paid instantly.
diff --git a/src/pages/index.mdx b/src/pages/index.mdx
index 53e6cba2..4b8658bc 100644
--- a/src/pages/index.mdx
+++ b/src/pages/index.mdx
@@ -34,8 +34,8 @@ These docs cover everything from creating a wallet to building payment systems o
icon="lucide:arrow-left-right"
/>
diff --git a/src/pages/learn/tempo/index.mdx b/src/pages/learn/tempo/index.mdx
index 0603147a..ed464c96 100644
--- a/src/pages/learn/tempo/index.mdx
+++ b/src/pages/learn/tempo/index.mdx
@@ -48,9 +48,9 @@ Explore the key features that make Tempo purpose-built for payments:
title="Privacy"
/>
diff --git a/src/pages/learn/tempo/machine-payments.mdx b/src/pages/learn/tempo/machine-payments.mdx
index dcae26cd..d861c02e 100644
--- a/src/pages/learn/tempo/machine-payments.mdx
+++ b/src/pages/learn/tempo/machine-payments.mdx
@@ -4,7 +4,7 @@ description: The Machine Payments Protocol (MPP) is an open standard for machine
import { Cards, Card } from 'vocs'
-# Machine Payments [Programmable payments for agents and services]
+# Agentic Payments [Programmable payments for agents and services]
Agents can write code, coordinate services, and execute complex workflows. What they can't do, until now, is pay for things.
@@ -83,7 +83,7 @@ The core [Payment HTTP Authentication Scheme](https://paymentauth.org) is submit
## Why Tempo
-Tempo's infrastructure is purpose-built for the transaction patterns that machine payments produce:
+Tempo's infrastructure is purpose-built for the transaction patterns that agentic payments produce:
- **~500ms deterministic finality**: Fast enough for synchronous request/response flows
- **Sub-cent fees**: Low enough for micropayments and per-request billing
diff --git a/vocs.config.ts b/vocs.config.ts
index e6af94f5..0a9b6543 100644
--- a/vocs.config.ts
+++ b/vocs.config.ts
@@ -207,7 +207,7 @@ export default defineConfig({
],
},
{
- text: 'Make Machine Payments',
+ text: 'Make Agentic Payments',
collapsed: true,
items: [
{
@@ -798,7 +798,7 @@ export default defineConfig({
link: '/learn/tempo/privacy',
},
{
- text: 'Machine Payments',
+ text: 'Agentic Payments',
link: '/learn/tempo/machine-payments',
},
],