Skip to content

Expand paid MCP tool guide#23

Open
chico10117 wants to merge 1 commit into
pyrimid-ai:mainfrom
chico10117:codex/paid-mcp-tool-guide
Open

Expand paid MCP tool guide#23
chico10117 wants to merge 1 commit into
pyrimid-ai:mainfrom
chico10117:codex/paid-mcp-tool-guide

Conversation

@chico10117
Copy link
Copy Markdown

Summary:

  • Expand the paid MCP tool example into a reproducible guide for selling an MCP tool or API call with x402 and Pyrimid.
  • Include a complete Next.js paid endpoint pattern, no-payment 402 response example, MCP tool schema, Pyrimid catalog metadata, discovery file snippet, repro checks, and common mistakes.
  • Link the guide back to Pyrimid catalog, quickstart, and proof surfaces.

Bounty scope:

Validation:

  • npm run build
  • git diff --check

Payment requested if accepted/merged:

  • Native USDC on Base
  • 0x820a7bf90d944bb26bfD9b62Ab172Fc3A0829cB9

No secrets, wallet signatures, payment headers, or paid calls were used.

@egoriklok
Copy link
Copy Markdown

Free public readiness snapshot for Expand paid MCP tool guide:

  • Public signal: No-payment readiness snapshot draft for Expand paid MCP tool guide #23: Expand paid MCP tool guide. Focus: api, mcp, payment, x402.
  • R1 fit: api, mcp, payment, tool, wallet, x402.
  • Buyer-agent check I would add before autonomous spend: explicit price/cap unit, policy/version hash, receipt or charge-evidence reference, revocation/dispute path, and allow/caution/block preflight result.
  • This separates "interesting paid surface" from "safe for an agent wallet to use".

No invoice, no payment link, no delivery link, no private endpoint; this is only a free public snapshot.

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.

2 participants