docs: copy improvements across landing, overview, FAQ, and quickstart

- Replace 'Monetize your API' with 'Add payments to your API' everywhere
- Remove 'internet-native' (4 instances) — replace with specific language
- Replace 'inline' with 'in the same HTTP request/response' in user-facing pages
- Replace 'Multi rail'/'Multi currency' with plain English descriptions
- Convert x402 comparison from bullet list to comparison table in FAQ
- Rewrite 'Why build MPP on Tempo?' to acknowledge other rails first
- Remove duplicate 'What is MPP?' FAQ (already covered in overview)
- Remove zero-value 'Can any Agent use MPP?' FAQ
- Rename Manual mode to 'Advanced: manual mode' in server quickstart
- Add '// pathUSD on Tempo' comment on first hex address in server quickstart
- Update sidebar and analytics labels to match

Author: brendanjryan

src/components/LandingPage.tsx

@@ -528,12 +528,12 @@ function Hero() {
               }}
               onClick={() =>
                 captureEvent(AnalyticsEvents.LANDING_CTA_CLICKED, {
-                  cta_label: "Monetize your API",
+                  cta_label: "Add payments to your API",
                   href: "/quickstart/server",
                 })
               }
             >
-              Monetize your API
+              Add payments to your API
             </Link>
           </div>
         </div>
@@ -552,8 +552,8 @@ function Tagline() {
       className="leading-relaxed max-w-xl font-normal max-[1080px]:max-w-lg"
       style={{ color: "var(--vocs-text-color-secondary)" }}
     >
-      The open protocol for internet-native payments. Charge for API requests,
-      tool calls, or content. Agents, apps, and humans securely pay per request.
+      The open protocol for machine-to-machine payments. Charge for API requests,
+      tool calls, or content—agents and apps pay per request in the same HTTP call.
     </div>
   );
 }

src/pages/faq.mdx

@@ -1,9 +1,5 @@
 # Frequently asked questions [Common questions about the Machine Payments Protocol]
 
-## What is MPP?
-
-The Machine Payments Protocol (MPP) is an internet-native protocol that lets any client—agents, software, or humans—pay for services inline over HTTP. The protocol is payment-method agnostic, open by design, and engineered for extensibility, performance, and security.
-
 ## Is MPP only for stablecoins?
 
 No. MPP is payment-method agnostic—the protocol works with any payment rail.
@@ -20,21 +16,25 @@ For Tempo payments, you need a stablecoin wallet to sign transactions. The SDK a
 
 Both MPP and x402 use HTTP `402` to signal that a request requires payment. The key differences:
 
-- **Payment-method agnostic.** MPP supports stablecoins, cards, wallets, and custom rails through extensible payment method specifications. x402 only supports blockchains.
-- **Designed for production.** MPP supports idempotency, expiration, request-body binding (digest), and request-tampering mitigations as first-class primitives.
-- **Performant payments.** MPP's session intent enables pay-as-you-go metering for payments as small as 0.0001 USD. Sessions achieve sub-100ms latency and near-zero per-request fees by settling off-chain vouchers, enabling high-throughput applications like token streaming or content aggregation. x402 requires an on-chain transaction per request.
-- **Permissionless extensibility.** Anyone can author and publish a new payment method or intent specification without approval from a foundation or intermediary. Payment methods compete on adoption and are independently maintained.
-- **IETF standards track.** The core [Payment HTTP Authentication Scheme](https://paymentauth.org) is submitted to the IETF for standardization.
+| | **MPP** | **x402** |
+|---|---------|----------|
+| **Payment methods** | Stablecoins, cards, wallets, custom rails | Blockchain only |
+| **Production primitives** | Idempotency, expiration, request-body binding, tampering mitigations | Limited |
+| **Low-value payments** | Session intent: sub-100ms latency, near-zero per-request fees via off-chain vouchers | On-chain transaction per request |
+| **Extensibility** | Anyone can author and publish new payment methods or intents | Foundation-controlled |
+| **Standardization** | [IETF standards track](https://paymentauth.org) | Not submitted |
 
 ## Is MPP compatible with x402?
 
 Yes. The core x402 "exact" flows map directly onto MPP's charge intent. MPP clients can consume existing x402 services. MPP extends beyond x402 with idempotency, receipts, request binding, multiple payment methods including stablecoins and fiat, and efficient low-cost flows like sessions.
 
 ## Why build MPP on Tempo?
 
-High-throughput, low-value transactions require specific properties from the settlement layer:
+MPP works with any payment rail—Stripe for cards, Lightning for Bitcoin, or any custom method. You don't have to use Tempo.
+
+That said, high-throughput, low-value transactions benefit from specific properties that Tempo provides:
 
-- **Fast, deterministic finality**—Tempo consensus provides certainty that a payment has settled, not probabilistic confirmation.
+- **Fast, deterministic finality**—Certainty that a payment has settled, not probabilistic confirmation.
 - **Low, predictable cost**—Transaction fees stay stable regardless of global network congestion.
 - **Payment lanes**—Dedicated transaction routing for payment traffic, ensuring reliability even under heavy load.
 - **Stablecoin-native**—TIP-20 stablecoins (USDC, USDT) are first-class citizens, so payments are denominated in familiar currency.
@@ -59,12 +59,6 @@ MPP requires TLS 1.2+ for all connections. Challenge IDs are cryptographically b
 
 Payments use the same security model as the underlying payment method. For Tempo, that means cryptographic signatures over every transaction. For Stripe, it means Stripe's existing fraud and dispute infrastructure.
 
-## Can any agent use MPP?
-
-Yes. Any agent can interact with MPP services via a compatible CLI or SDK. The [quickstart guide](/quickstart/agent) has copy-paste setup instructions for Claude, Codex, and Amp.
-
-For programmatic integration, the [TypeScript](/sdk/typescript), [Python](/sdk/python), and [Rust](/sdk/rust) SDKs provide native support.
-
 ## What happens if a payment fails?
 
 The service returns an error with details following [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) (Problem Details for HTTP APIs). Your client can retry with a different payment method or surface the error. No money is deducted for failed requests.

src/pages/overview.mdx

@@ -4,16 +4,16 @@ import { TerminalPing } from '../components/TerminalPing'
 import { TypeScriptSdkCard, PythonSdkCard, RustSdkCard, QuickstartCard, ProtocolConceptsCard } from '../components/cards'
 import { PaymentFlowDiagram } from '../components/PaymentFlowDiagram'
 
-# Machine Payments Protocol [The open protocol for internet-native payments]
+# Machine Payments Protocol [The open protocol for machine-to-machine payments]
 
-The Machine Payments Protocol (MPP) lets any client—agents, apps, or humans—pay for any service, inline, over HTTP. Developers use MPP to let their agents pay for services. Service operators use MPP to monetize their APIs.
+The Machine Payments Protocol (MPP) lets any client—agents, apps, or humans—pay for any service in the same HTTP request. Developers use MPP to let their agents pay for services. Service operators use MPP to accept payments for their APIs.
 
 MPP is built around a simple extensible core and is neutral to the implementation of underlying payment flows and methods.
 
 - **Open standard built for the internet**—Built on an [open specification proposed to the IETF](https://paymentauth.org), not a proprietary API
 - **Designed for payments**—Idempotency, security, and receipts are first-class primitives
-- **Multi rail**—Stablecoins, cards, bank transfers, and digital wallets. All payment methods can be supported through one protocol and flexible control flow
-- **Multi currency**—The protocol is currency agnostic, allowing for transactions in USD, EUR, BRL, USDC, BTC, or any other asset
+- **Works with stablecoins, cards, and bank transfers**—All payment methods can be supported through one protocol and flexible control flow
+- **Any currency**—Transact in USD, EUR, BRL, USDC, BTC, or any other asset
 - **Composable and designed for extension**—A flexible core allows advanced flows like disputes or additional primitives like identity to be gradually introduced
 
 ## Who is MPP for?
@@ -22,7 +22,7 @@ MPP involves three parties:
 
 - **Developers** build apps and agents that consume paid services. You integrate an MPP client so your agent can discover, pay for, and use third-party APIs without manual signup or API keys.
 - **Agents** are the entities that take action—calling APIs, generating images, querying data. They pay for services autonomously on behalf of your users.
-- **Services** operate APIs that charge for access—LLM inference, image generation, web search, and more. You integrate an MPP server to accept payments inline with zero onboarding friction.
+- **Services** operate APIs that charge for access—LLM inference, image generation, web search, and more. You integrate an MPP server to accept payments with zero onboarding friction.
 
 ## The problem with payments on the internet
 
@@ -32,7 +32,7 @@ However, the very things that make these payment flows familiar and fast for hum
 
 This is not the fault of any individual payment method or credential. This is a global problem which exists at the _interface_ level: how buyer and seller negotiate cost, supported payment methods, and ultimately transact.
 
-The Machine Payments Protocol addresses this gap by providing an internet-native payment interface that strips away the complexity of rich checkout flows, while still providing robust security and reliability. By using MPP, you can accept payments from any client — agents, apps, or humans — and across any payment method, without the need for a complex checkout flows and integrations.
+The Machine Payments Protocol addresses this gap by providing a payment interface built for programmatic access that strips away the complexity of rich checkout flows, while still providing robust security and reliability. By using MPP, you can accept payments from any client—agents, apps, or humans—and across any payment method, without complex checkout flows and integrations.
 
 ## Try it out
 
@@ -45,9 +45,9 @@ See the full payment flow in action. The terminal creates an ephemeral wallet, f
 ## Use cases
 
 * **Pay for LLM usage**—Your agent calls LLM providers through MPP, paying per token over a Tempo session. No API key management needed.
-* **Generate an image**—Request image generation from fal.ai or ElevenLabs audio, paying per request with a Tempo charge. The agent gets the result inline.
+* **Generate an image**—Request image generation from fal.ai or ElevenLabs audio, paying per request with a Tempo charge. The agent gets the result in the same response.
 * **Search the web**—Query Parallel for real-time search results, paying per query over a Tempo session. Results flow back in the same HTTP response.
-* **Monetize your API**—Accept payments from any client—agents, apps, or humans—without requiring signups, billing accounts, or API keys.
+* **Accept payments for your API**—Accept payments from any client—agents, apps, or humans—without requiring signups, billing accounts, or API keys.
 
 ## Payment flow
 

src/pages/protocol/index.mdx

@@ -3,7 +3,7 @@ import { PaymentFlowDiagram } from "../../components/PaymentFlowDiagram";
 
 # Protocol overview [Standardizing HTTP 402 for machine-to-machine payments]
 
-The Machine Payments Protocol (MPP) is an internet-native protocol for machine-to-machine payments. It standardizes HTTP `402` "Payment Required" with an extensible framework that works with any payment network.
+The Machine Payments Protocol (MPP) is a protocol for machine-to-machine payments. It standardizes HTTP `402` "Payment Required" with an extensible framework that works with any payment network.
 
 These docs provide a developer-friendly overview. For the full specification, see the full [IETF Specification](https://paymentauth.org).
 

src/pages/quickstart/server.mdx

@@ -2,15 +2,15 @@ import { Badge, Cards } from 'vocs'
 import { ServerPrompt } from '../../components/QuickstartPrompt'
 import { ClientQuickstartCard, TempoMethodCard, MppxCreateReferenceCard } from '../../components/cards'
 
-# Monetize your API [Charge for access to protected resources]
+# Add payments to your API [Charge for access to protected resources]
 
 ## Overview
 
 This quickstart demonstrates how to plug MPP into any server framework to accept payments for protected resources. Pick the path that suits you:
 
 - [**Prompt mode**](#prompt-mode): paste a prompt into your coding agent and build in one prompt
 - [**Framework mode**](#framework-mode): use `mppx` middleware for Next.js, Hono, Elysia, or Express
-- [**Manual mode**](#manual-mode): call `mppx/server` directly with the Fetch API
+- [**Manual mode**](#advanced-manual-mode): call `mppx/server` directly with the Fetch API
 
 ## Prompt mode
 
@@ -30,7 +30,7 @@ import { Mppx, tempo } from 'mppx/nextjs'
 // [!code hl:start]
 const mppx = Mppx.create({
   methods: [tempo({
-    currency: '0x20c0000000000000000000000000000000000000',
+    currency: '0x20c0000000000000000000000000000000000000', // pathUSD on Tempo
     recipient: '0xa726a1CD723409074DF9108A2187cfA19899aCF8',
   })],
 })
@@ -119,10 +119,10 @@ mppx.charge({
 :::
 
 :::note
-Don't see your framework? `mppx` is designed to be framework-agnostic. See [Manual mode](#manual-mode) below.
+Don't see your framework? `mppx` is designed to be framework-agnostic. See [Manual mode](#advanced-manual-mode) below.
 :::
 
-## Manual mode
+## Advanced: manual mode
 
 If you prefer full control over the payment flow, use `mppx/server` directly with the Fetch API.
 

vocs.config.ts

@@ -95,7 +95,7 @@ export default defineConfig({
         text: "Quick Start",
         items: [
           { text: "Overview", link: "/quickstart" },
-          { text: "Monetize your service", link: "/quickstart/server" },
+          { text: "Add payments to your API", link: "/quickstart/server" },
           { text: "Use with agents", link: "/quickstart/agent" },
           { text: "Use with your app", link: "/quickstart/client" },
         ],