diff --git a/development-guide/nevermined-x402.mdx b/development-guide/nevermined-x402.mdx index 68e5729..27ea425 100644 --- a/development-guide/nevermined-x402.mdx +++ b/development-guide/nevermined-x402.mdx @@ -621,7 +621,7 @@ For other frameworks or custom implementations, follow these steps: Some services accept **MPP (Merchant Payment Protocol)** instead of x402. MPP settles against the same Nevermined Payment Plans as x402 — same credits, same delegation, same meter — so the buyer flow mirrors the one above with `/api/v1/mpp/*` in place of `/api/v1/x402/*`. You recognise an MPP service by its `402`: it carries a `WWW-Authenticate: Payment …` header instead of an x402 `accepts` body. -This is the **buyer** side. To make *your own* plan-protected endpoint MPP-payable, see [Accepting MPP payments](/products/x402-facilitator/mpp-seller). +This is the **buyer** side. To make *your own* plan-protected endpoint MPP-payable, see [Accepting MPP payments](/products/payments-facilitator/mpp-seller). ### Recommended: the SDK does it for you diff --git a/docs.json b/docs.json index 69dd843..487356e 100644 --- a/docs.json +++ b/docs.json @@ -195,9 +195,9 @@ "group": "Payments Facilitator", "icon": "credit-card", "pages": [ - "products/x402-facilitator/overview", - "products/x402-facilitator/how-it-works", - "products/x402-facilitator/mpp-seller" + "products/payments-facilitator/overview", + "products/payments-facilitator/how-it-works", + "products/payments-facilitator/mpp-seller" ] }, { @@ -486,13 +486,33 @@ "source": "/products/nvm-pay/faq", "destination": "/products/payments/faq" }, + { + "source": "/products/payments-facilitator", + "destination": "/products/payments-facilitator/overview" + }, + { + "source": "/products/payments-facilitator/", + "destination": "/products/payments-facilitator/overview" + }, { "source": "/products/x402-facilitator", - "destination": "/products/x402-facilitator/overview" + "destination": "/products/payments-facilitator/overview" }, { "source": "/products/x402-facilitator/", - "destination": "/products/x402-facilitator/overview" + "destination": "/products/payments-facilitator/overview" + }, + { + "source": "/products/x402-facilitator/overview", + "destination": "/products/payments-facilitator/overview" + }, + { + "source": "/products/x402-facilitator/how-it-works", + "destination": "/products/payments-facilitator/how-it-works" + }, + { + "source": "/products/x402-facilitator/mpp-seller", + "destination": "/products/payments-facilitator/mpp-seller" }, { "source": "/products/nevermined-app", diff --git a/products/catalog/overview.mdx b/products/catalog/overview.mdx index aaa653e..9a64167 100644 --- a/products/catalog/overview.mdx +++ b/products/catalog/overview.mdx @@ -11,7 +11,7 @@ The **Nevermined Catalog** is a curated directory of external AI services your a The Catalog is the front door; the **[Router](/products/catalog/router/overview)** is how you walk through it. You discover a service in the Catalog, then pay it through the Router from a budget you control. The two are one product read in one direction: **spending** at services that were never onboarded to Nevermined. -The Catalog lists services you **buy from**. If instead you want your own API to *get paid* by callers, that's the seller side — see the **[Payments Facilitator](/products/x402-facilitator/overview)**. You can be on both sides at once, and you can even **[add your own AI service](/products/catalog/ai-services#add-your-ai-service)** to the Catalog so other buyers discover it. +The Catalog lists services you **buy from**. If instead you want your own API to *get paid* by callers, that's the seller side — see the **[Payments Facilitator](/products/payments-facilitator/overview)**. You can be on both sides at once, and you can even **[add your own AI service](/products/catalog/ai-services#add-your-ai-service)** to the Catalog so other buyers discover it. ## What's in it diff --git a/products/catalog/router/overview.mdx b/products/catalog/router/overview.mdx index c7f8fb1..016aa4c 100644 --- a/products/catalog/router/overview.mdx +++ b/products/catalog/router/overview.mdx @@ -18,7 +18,7 @@ The Router is how you **pay** for services you find in the **[Nevermined Catalog Nevermined has two halves, and it's worth being precise about which one you're reading: -| | **Router** (this section) | **[Payments Facilitator](/products/x402-facilitator/overview)** | +| | **Router** (this section) | **[Payments Facilitator](/products/payments-facilitator/overview)** | | --- | --- | --- | | Role | **Buyer** — your agent pays someone else | **Seller** — your API charges its callers | | Who integrates | Only you | Only the service being paid | diff --git a/products/x402-facilitator/how-it-works.mdx b/products/payments-facilitator/how-it-works.mdx similarity index 98% rename from products/x402-facilitator/how-it-works.mdx rename to products/payments-facilitator/how-it-works.mdx index 36eca91..253f296 100644 --- a/products/x402-facilitator/how-it-works.mdx +++ b/products/payments-facilitator/how-it-works.mdx @@ -11,7 +11,7 @@ For the complete technical specification, see the [x402 Smart Accounts Extension -This page covers the **x402** protocol. The Payments Facilitator also speaks **MPP (Merchant Payment Protocol)** against the same plans and credits — see [Accepting MPP payments](/products/x402-facilitator/mpp-seller) for the seller side and [Paying an MPP-protected service](/development-guide/nevermined-x402#paying-an-mpp-protected-service) for the buyer side. +This page covers the **x402** protocol. The Payments Facilitator also speaks **MPP (Merchant Payment Protocol)** against the same plans and credits — see [Accepting MPP payments](/products/payments-facilitator/mpp-seller) for the seller side and [Paying an MPP-protected service](/development-guide/nevermined-x402#paying-an-mpp-protected-service) for the buyer side. If you're new to the programmable extension concepts, see: diff --git a/products/x402-facilitator/mpp-seller.mdx b/products/payments-facilitator/mpp-seller.mdx similarity index 100% rename from products/x402-facilitator/mpp-seller.mdx rename to products/payments-facilitator/mpp-seller.mdx diff --git a/products/x402-facilitator/overview.mdx b/products/payments-facilitator/overview.mdx similarity index 88% rename from products/x402-facilitator/overview.mdx rename to products/payments-facilitator/overview.mdx index 61419a5..d27ce8d 100644 --- a/products/x402-facilitator/overview.mdx +++ b/products/payments-facilitator/overview.mdx @@ -4,17 +4,15 @@ description: "The Nevermined Payments Facilitator verifies and settles both x402 icon: "credit-card" --- -{/* The docs path stays /products/x402-facilitator/* for link stability — it is historical, from when the product was x402-only, and not a sign the facilitator is x402-only today. Do not "fix" it by renaming the route without adding redirects from every old path. */} - The Nevermined Payments Facilitator is an **enforcement and settlement engine** for HTTP-native agent payments. It lets any API, agent, MCP tool, or protected resource get paid without running on-chain infrastructure — and it speaks **two sibling payment protocols that settle against the same Nevermined Payment Plans**: - **[x402](/development-guide/nevermined-x402)** — payment terms travel in a `payment-required` header and the payment is presented in `payment-signature`. Covers standard "pay-per-request" x402 and Nevermined's programmable extension (`nvm:erc4337` and `nvm:card-delegation` schemes, with smart accounts, session keys, and contract settlement). -- **[MPP (Merchant Payment Protocol)](/products/x402-facilitator/mpp-seller)** — the same plan, credits, and delegation, negotiated with an RFC 7235 `WWW-Authenticate: Payment …` challenge and an `Authorization: Payment …` credential instead. +- **[MPP (Merchant Payment Protocol)](/products/payments-facilitator/mpp-seller)** — the same plan, credits, and delegation, negotiated with an RFC 7235 `WWW-Authenticate: Payment …` challenge and an `Authorization: Payment …` credential instead. A request that costs 2 credits burns 2 whether it was paid over x402 or MPP: **one meter, one delegation budget, two wire protocols.** -For the complete technical specification of the x402 extension, see the [x402 Smart Accounts Extension Spec](/specs/x402-smart-accounts). For the MPP seller integration, see [Accepting MPP payments](/products/x402-facilitator/mpp-seller). +For the complete technical specification of the x402 extension, see the [x402 Smart Accounts Extension Spec](/specs/x402-smart-accounts). For the MPP seller integration, see [Accepting MPP payments](/products/payments-facilitator/mpp-seller). The Facilitator sits in the payment flow — when a server receives a payment token, it delegates verification and settlement to the Facilitator rather than handling it directly. See [how the x402 flow works end to end](/development-guide/nevermined-x402). @@ -85,7 +83,7 @@ Each protocol has its own verify/settle route pair. The plan, the credits, and t -Buyers mint their access token at `POST /api/v1/x402/permissions` (x402) or `POST /api/v1/mpp/permissions` (MPP). A token minted for one protocol is refused on the other's routes — see [protocol isolation](/products/x402-facilitator/mpp-seller#protocol-isolation). Full MPP seller reference: [Accepting MPP payments](/products/x402-facilitator/mpp-seller). +Buyers mint their access token at `POST /api/v1/x402/permissions` (x402) or `POST /api/v1/mpp/permissions` (MPP). A token minted for one protocol is refused on the other's routes — see [protocol isolation](/products/payments-facilitator/mpp-seller#protocol-isolation). Full MPP seller reference: [Accepting MPP payments](/products/payments-facilitator/mpp-seller). ## How it works @@ -150,11 +148,11 @@ After the server completes its work, the facilitator can execute the settlement One-line payment protection with Express middleware - + End-to-end flow (client + server) with x402 headers and facilitator calls - + Advertise your plan-protected endpoint as MPP-payable, metered exactly like x402 diff --git a/solutions/api-providers.mdx b/solutions/api-providers.mdx index 3255ef2..8b5fbc5 100644 --- a/solutions/api-providers.mdx +++ b/solutions/api-providers.mdx @@ -6,7 +6,7 @@ icon: "plug" Agents are a new buyer of your API, and they don't onboard the way humans do. They don't sit at a browser, fill out a Stripe Checkout, or remember to top up a credit balance. Today they either stall at your paywall or hardcode a human's API key. -Nevermined turns that failure mode into revenue with a small server-side integration. Agents holding a delegated card mint an [x402](/development-guide/nevermined-x402) access token, send it to your endpoint, and you provision or top up access in response. You verify and settle through Nevermined's [Payments Facilitator](/products/x402-facilitator/overview); the buyer's card is charged through Stripe, Braintree, or the Visa Trusted Agent Protocol depending on how it was enrolled. All three settle x402 charges through the same `nvm:card-delegation` scheme — your endpoint code doesn't change. +Nevermined turns that failure mode into revenue with a small server-side integration. Agents holding a delegated card mint an [x402](/development-guide/nevermined-x402) access token, send it to your endpoint, and you provision or top up access in response. You verify and settle through Nevermined's [Payments Facilitator](/products/payments-facilitator/overview); the buyer's card is charged through Stripe, Braintree, or the Visa Trusted Agent Protocol depending on how it was enrolled. All three settle x402 charges through the same `nvm:card-delegation` scheme — your endpoint code doesn't change. ## Featured providers @@ -585,7 +585,7 @@ Prices above are indicative; the live price for each tier is shown on the upgrad - [x402 Card Delegation Spec](/specs/x402-card-delegation) - full verify/settle protocol with JWT claims, error codes, and the four-phase flow -- [Payments Facilitator: How it works](/products/x402-facilitator/how-it-works) +- [Payments Facilitator: How it works](/products/payments-facilitator/how-it-works) - end-to-end walk-through of the facilitator API - [Validate Requests](/integrate/patterns/validate-requests) and [Charge Credits](/integrate/patterns/charge-credits) - copy-paste