@solvapay/server 1.0.8-preview.9 → 1.0.8

package/README.md

@@ -52,6 +52,64 @@ const solvapay = createSolvaPayClient({
 })
 ```
 
+### Web-standards runtimes — `@solvapay/server/fetch` subpath
+
+For Deno / Supabase Edge / Cloudflare Workers / Bun / Next edge /
+Vercel Functions deploys, use the `./fetch` subpath export. Every
+SolvaPay route ships as a ready-made `(req: Request) => Promise<Response>`
+handler with CORS + JSON serialisation baked in, so each Edge Function
+is a one-liner:
+
+```ts
+// supabase/functions/check-purchase/index.ts
+import { checkPurchase } from '@solvapay/server/fetch'
+
+Deno.serve(checkPurchase)
+```
+
+Available handlers: `checkPurchase`, `trackUsage`, `createPaymentIntent`,
+`processPayment`, `createTopupPaymentIntent`, `customerBalance`,
+`cancelRenewal`, `reactivateRenewal`, `activatePlan`, `getPaymentMethod`,
+`listPlans`, `syncCustomer`, `createCheckoutSession`,
+`createCustomerSession`, `getMerchant`, `getProduct`, `solvapayWebhook`.
+
+Configure CORS for production origins:
+
+```ts
+import { checkPurchase, configureCors } from '@solvapay/server/fetch'
+
+configureCors({ origins: ['https://myapp.com', 'http://localhost:5173'] })
+
+Deno.serve(checkPurchase)
+```
+
+Webhook handler (verifies the `SV-Signature` header via Web Crypto,
+returns 401 on invalid signatures, 500 on handler failures):
+
+```ts
+import { solvapayWebhook } from '@solvapay/server/fetch'
+
+Deno.serve(
+  solvapayWebhook({
+    secret: Deno.env.get('SOLVAPAY_WEBHOOK_SECRET')!,
+    onEvent: async event => {
+      if (event.type === 'purchase.created') {
+        // handle new purchase
+      }
+    },
+  }),
+)
+```
+
+Full reference implementation in
+[`examples/supabase-edge`](https://github.com/solvapay/solvapay-sdk/tree/main/examples/supabase-edge).
+
+> **History**: the `./fetch` subpath was formerly shipped as the
+> standalone package `@solvapay/fetch@1.0.0` (renamed from
+> `@solvapay/supabase@1.0.1`). It was folded into `@solvapay/server`
+> in `@solvapay/server@1.0.8` — see the CHANGELOG for the migration
+> one-liner.
+
 ### Paywall Protection
 
 Use the unified payable API to protect your endpoints and functions with usage limits and metered billing:
@@ -128,13 +186,33 @@ export const POST = solvaPay.payable({ product: 'my-api' }).next(
 This automatically extracts the user ID from authentication tokens and uses it as the customer reference for paywall checks.
 Fail closed on missing/invalid auth. Do not fall back to shared identities like `anonymous`.
 
-For MCP bearer-token flows, the SDK also exports helper utilities:
+### MCP servers
+
+`@solvapay/server` is framework-free. For a full SolvaPay MCP server
+(transport tools + `open_*` bootstrap tools + UI resource) use
+[`@solvapay/mcp`](https://github.com/solvapay/solvapay-sdk/tree/main/packages/mcp)'s
+`createSolvaPayMcpServer` — the official `@modelcontextprotocol/sdk`
+adapter. For framework-neutral descriptors (`fastmcp`, raw JSON-RPC),
+use
+[`@solvapay/mcp-core`](https://github.com/solvapay/solvapay-sdk/tree/main/packages/mcp-core)'s
+`buildSolvaPayDescriptors`. OAuth-bridge middleware ships as runtime-
+specific subpath exports of `@solvapay/mcp`:
+[`@solvapay/mcp/express`](https://github.com/solvapay/solvapay-sdk/tree/main/packages/mcp/src/express)
+(`createMcpOAuthBridge`) for Node, and
+[`@solvapay/mcp/fetch`](https://github.com/solvapay/solvapay-sdk/tree/main/packages/mcp/src/fetch)
+(`createSolvaPayMcpFetchHandler`, `createSolvaPayMcpFetch`) for
+Web-standards runtimes (Deno / Supabase Edge / Cloudflare Workers /
+Bun / Next edge / Vercel Functions). JWT bearer helpers
+(`getCustomerRefFromBearerAuthHeader`, `McpBearerAuthError`) live
+in `@solvapay/mcp-core`.
+
+For MCP bearer-token flows, import the helpers from `@solvapay/mcp-core`:
 
 ```ts
 import {
   getCustomerRefFromBearerAuthHeader,
   McpBearerAuthError,
-} from '@solvapay/server'
+} from '@solvapay/mcp-core'
 
 const handler = solvaPay.payable({ product: 'my-api' }).mcp(
   async args => ({ ok: true }),