Skip to content

docs: monetization solution page + tighten attribution rules#2

Open
adacapo21 wants to merge 2 commits into
mainfrom
claude/x402-monetization-docs-C2Vz3
Open

docs: monetization solution page + tighten attribution rules#2
adacapo21 wants to merge 2 commits into
mainfrom
claude/x402-monetization-docs-C2Vz3

Conversation

@adacapo21
Copy link
Copy Markdown
Member

@adacapo21 adacapo21 commented Apr 27, 2026

Summary

  • Add a use-case-first solution page (docs/solutions/monetize-mcp-and-apis.mdx) targeting the "I have an MCP server / API, how do I charge per call?" reader. Seven sections, plain MDX, portable to Mintlify / Nextra / Docusaurus.
  • Extend the contributor rule in CLAUDE.md: AI-attribution strings are forbidden not only in commit messages but also in commit trailers, PR titles, and PR descriptions, with a spelled-out remediation path.

What's on the page

  1. What you can monetize
  2. How it works (the 402 handshake)
  3. Two integration paths
    • A. Wrap your own server (withX402Server, x402Express, x402Hono)
    • B. Proxy CLI in front of an existing MCP server — coming soon, gated on QBT-598
  4. Pricing model — tier numbers match src/pricing.ts exactly ($0 / $0.001 / $0.005 / $0.01)
  5. Client experience — MCP client config + createPaymentFetch
  6. Supported chains — Base today, Solana via PayAI today, Cardano self-settled via Blockfrost
  7. Why QBT x402

All code samples compile against current @qbtlabs/x402 exports — no aspirational APIs.

Decisions worth flagging

  • Used current SDK pricing tiers (option a from the planning thread) rather than 10× values. If product wants $0.01 / $0.05 / $0.10 instead, that's a separate pricing.ts PR and this page updates with it.
  • Plain MDX, no framework-specific components yet, so the page is portable to whichever docs framework is picked.

Related

Test plan

  • Render the MDX in the target docs framework once chosen and confirm tables / code blocks render correctly
  • Cross-check every code sample against current src/index.ts exports
  • Confirm pricing-tier numbers still match src/pricing.ts
  • Verify Cardano caveat ("self-settled via Blockfrost; QBT facilitator coming") still reflects facilitator state at merge time
  • Verify proxy CLI section stays gated as "coming soon" until QBT-598 ships

Use-case-first MDX page targeting the "I have an MCP server / API,
how do I charge per call?" reader. Seven sections: what you can
monetize, how it works, two integration paths (own server vs. proxy
CLI), pricing model, client experience, supported chains, why QBT.

All code samples compile against current @qbtlabs/x402 exports.
Pricing-tier numbers match src/pricing.ts. Cardano flagged as
self-settled via Blockfrost; proxy CLI gated as coming soon
(QBT-598). Plain MDX so it's portable across Mintlify / Nextra /
Docusaurus.

Refs: GitHub #1, QBT-597, QBT-598, QBT-599, QBT-379
Extend the existing 'no Claude reference' rule beyond commit messages
to cover commit trailers, PR titles, and PR descriptions. Spell out
the remediation path (amend / interactive rebase) so the rule is
actionable when a slip happens.
@adacapo21 adacapo21 force-pushed the claude/x402-monetization-docs-C2Vz3 branch from 2b4e546 to dbb8eed Compare April 27, 2026 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant