@solvapay/server 1.0.0-preview.20 → 1.0.0-preview.21

package/README.md

@@ -64,8 +64,8 @@ const solvaPay = createSolvaPay({
   apiKey: process.env.SOLVAPAY_SECRET_KEY!
 });
 
-// Create a payable with your agent configuration
-const payable = solvaPay.payable({ agent: 'my-agent' });
+// Create a payable with your product configuration
+const payable = solvaPay.payable({ product: 'my-product' });
 
 // Use the appropriate adapter for your context:
 
@@ -109,7 +109,7 @@ const auth = new SupabaseAuthAdapter({
 const solvaPay = createSolvaPay({ apiKey: process.env.SOLVAPAY_SECRET_KEY! })
 
 // Use with Next.js adapter
-export const POST = solvaPay.payable({ agent: 'my-api' }).next(
+export const POST = solvaPay.payable({ product: 'my-api' }).next(
   async args => {
     return { result: 'success' }
   },
@@ -124,6 +124,32 @@ export const POST = solvaPay.payable({ agent: 'my-api' }).next(
 
 This automatically extracts the user ID from authentication tokens and uses it as the customer reference for paywall checks.
 
+For MCP bearer-token flows, the SDK also exports helper utilities:
+
+```ts
+import {
+  getCustomerRefFromBearerAuthHeader,
+  McpBearerAuthError,
+} from '@solvapay/server'
+
+const handler = solvaPay.payable({ product: 'my-api' }).mcp(
+  async args => ({ ok: true }),
+  {
+    getCustomerRef: args => {
+      try {
+        return getCustomerRefFromBearerAuthHeader(args._authHeader as string | undefined)
+      } catch (error) {
+        if (error instanceof McpBearerAuthError) return 'anonymous'
+        throw error
+      }
+    },
+  },
+)
+```
+
+`payable({ getCustomerRef })` is now supported as a default extractor across adapters. Adapter-level
+`getCustomerRef` still takes precedence when both are provided.
+
 ### When to Use Each Adapter
 
 Choose the adapter based on your context:
@@ -189,7 +215,7 @@ type Agent = components['schemas']['Agent']
 type Plan = components['schemas']['Plan']
 ```
 
-**Note:** The generated types complement the existing hand-written types in `src/types.ts`. Run `pnpm generate:types` whenever the backend API changes to keep types in sync.
+**Note:** The generated types complement the existing hand-written types in `src/types/client.ts`. Run `pnpm generate:types` whenever the backend API changes to keep types in sync.
 
 ## Testing
 
@@ -216,13 +242,13 @@ pnpm test:watch
 
 ### Unit Tests
 
-Unit tests (`__tests__/paywall.test.ts`) use a mock API client and test:
+Unit tests (`__tests__/paywall.unit.test.ts`, `__tests__/mcp-auth.unit.test.ts`) use a mock API client and test:
 
 - Paywall protection logic
 - Handler creation (HTTP, Next.js, MCP)
 - Error handling
 - Authentication flows
-- Agent resolution
+- Product resolution
 
 **No backend required** - runs fast and deterministically.