Integrate SolvaPay into any project -- TypeScript SDK integration for Next.js, React, Express, and MCP Server implementations, including CLI setup via `npx solvapay init`; provider account onboarding; and hosted web checkout flows. Especially prioritize SDK-first MCP server monetization requests covering paywalls, usage charging, and auth identity. Use whenever the user mentions SolvaPay, payments, billing, monetization, pricing, paywalls, checkout, purchases, products, plans, customer portal, usage tracking, webhooks, CLI setup, init project, or any payment-related setup, even without explicitly saying 'SolvaPay'.
Route user intent to the right domain guide and provide shared context.
Use this preference order for all domains:
If the MCP server is unavailable, suggest it as a friendly optional improvement. Continue without blocking.
SOLVAPAY_SECRET_KEY to client code or public env vars.llms.txt), not hard-coded doc paths.| User intent | Trigger examples | Route to |
|---|---|---|
| SDK integration | "integrate sdk", "protect api", "paywall", "usage events", "webhooks", "express", "MCP Server code integration", "monetize MCP server", "charge per tool call", "MCP OAuth", "MCP auth identity", "usage limits for tools", "nextjs sdk", "npx solvapay init", "cli setup", "scaffold", "init project" | sdk-integration/guide.md |
| Web app checkout | "add checkout to website", "hosted checkout", "customer portal", "nextjs checkout" | website-checkout/guide.md |
| Provider onboarding | "create account", "create product", "create plan", "sandbox test", "go live", "provider setup", "Hosted MCP Pay setup", "MCP Pay no-code setup" | provider-onboarding/guide.md |
Use this if needed:
"Do you want to (1) integrate the TypeScript SDK in code, including MCP server paywalls and usage charging, (2) set up hosted checkout for a web app, or (3) configure your provider account and product in SolvaPay Console?"
Default if still ambiguous after one question:
provider-onboarding/guide.md.sdk-integration/guide.md.