ContextVM

It is shipping time! 🚀 cvmi v0.4.0 is out!

The ContextVM CLI now speaks CEP-8 payments natively. Priced capabilities are first-class in the CLI:

💳 See prices upfront — cvmi call now shows advertised per-tool prices and accepted payment rails right in the tool list and --help.

🔀 Two payment modes:

• transparent (default for call) — PMI-agnostic settlement, the server picks the rail.
• explicit_gating — priced tools surface a clean Payment Required error with payment options. Pay one, retry, done. Now the default for cvmi use, so agent hosts over stdio get explicit signals instead of silent notifications.

🛡 Spec-hardened parser — malformed cap prices (negative values, out-of-order ranges) are now rejected per CEP-8, not coerced into bogus ranges.

⚙ cvmi serve gained payment interaction config.

Plus bumps to @contextvm/sdk ^0.13.9 and @modelcontextprotocol/sdk ^1.29.

Upgrade and start charging for your capabilities 🔌 npx cvmi@latest

#ContextVM #MCP #CEP8 #Bitcoin #Lightning #OpenSource

CEP-8 can now talk directly to AI agents. 🧵

With the just released ContextVM SDK 0.13.0 we're shipping full support for a new CEP-8 mode called Explicit Payment Gating.

Why we built it: CEP-8 already let servers charge for their tools and capabilities, but only "behind the scenes", payment was handled silently by the transport layer. That's great for a wallet app. It's not great for an AI agent that actually needs to decide whether a call is worth paying for.

The fix: Agents reason through normal MCP responses, so we turned payment into one. Now a paid call returns a clean "Payment Required" error (-32042) that carries human-readable instructions and one or more payment options. Feed that straight to your LLM, it reads the instruction, pays the invoice its own way, and retries the same call. No special SDK knowledge required, and it works with any MCP-compatible agent runtime.

This design is based on the MPP spec and inspired by HTTP's 402 Payment Required status code, a long-reserved error code for exactly this idea, now adapted for JSON-RPC and AI agents.

What it unlocks:

• AI agents that natively understand and handle paid MCP capabilities
• Per-call budgets and consent at the agent layer
• Payment as a first-class decision: pay, decline, or escalate to a human

Under the hood, each successful payment grants a single-use authorization that's matched to the exact same request on retry, and a "Payment Pending" error (-32043) keeps verification from spamming invoices.

Fully backward compatible, the existing silent "transparent" flow stays the default, so nothing breaks for current users.

Try it: Upgrade to @contextvm/sdk 0.13.0 and turn on a paid capability with explicit gating.

Docs: CEP-8 spec — https://docs.contextvm.org/reference/ceps/cep-8/ Explicit gating guide — https://docs.contextvm.org/how-to/payments/explicit-gating/ API reference — https://docs.contextvm.org/reference/ts-sdk/payments/explicit-gating/

Go build something agents can pay for. 🔌

#ContextVM #MCP #AI #Bitcoin #Lightning #Nostr

🚀 Serve and Use: two new commands, one CLI, zero hassle

We merged our standalone gateway‑cli and proxy‑cli tools directly into cvmi. What used to require separate installations and configuration now lives under one unified CLI, and it couldn’t be simpler.

Serve any MCP server over Nostr:

• For example, the NostrBook: npx cvmi serve npx -y @nostrbook/mcp@latest
• Or even expose a remote HTTP server through Nostr👀👀: npx cvmi serve https://mcp.applesauce.build/mcp

This is a very new feature and led us to bump our SDK version to 0.3.x. More info is available in the CHANGELOG (https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md) and the gateway overview (https://docs.contextvm.org/ts-sdk/gateway/overview/).

Use a remote server and access it locally via stdio: npx cvmi use 7506...5fa3

Both new commands work out of the box with ephemeral keys and default relays. Override relays, keys, or other settings via flags, config files, or environment variables when you need more control. To see all available options, just use --help with any command.

For builders who want to ship, and for users who want to connect to their services easily, the toolkit is shaping well: skills, servers, and connectivity in one place. Run npx cvmi and explore. Soon we’ll add new features to complement these and give you everything you need to learn, build, debug, and interact with the CVM ecosystem. Stay tuned.

https://github.com/contextvm/cvmi

#ContextVM #Nostr #MCP #decentralized

🎇Meet CVMI: the Army knife we are building for ContextVM development🧑‍💻

If you are building/vibing on Nostr, this is for you. We are shipping CVMI alongside a complete skill set that makes ContextVM development delightful.

The skills cover the entire stack: protocol fundamentals, architecture concepts, client and server development, troubleshooting, SDK internals, and production deployment. Each skill includes working templates, reference documentation, and patterns distilled from real Nostr development. Everything you need to do is npx cvmi.

Or grab the skills through CVMI with npx cvmi add, or through the skills CLI with npx skills add contextvm/cvmi.

These commands will show you the list of available skills and guide you through their installation for any coding platform. Cool, right?

You can also pick exactly what you need npx cvmi add --skill overview

CVMI starts as a skills manager, but we are building toward the unified toolkit that ContextVM deserves. One CLI for skills, server interaction, dev tools, the works.

For builders who want to ship. The skills are here now.

https://github.com/contextvm/cvmi

If you don't know what skills are: https://agentskills.io/home

#ContextVM #Nostr #MCP #buildinpublic

🚀 Exciting news! We're working on a new CEP for ContextVM: Common Tool Schemas! 🌐

https://github.com/ContextVM/contextvm-docs/issues/15

Imagine a marketplace where users can choose the best server for their specific needs, without being locked into a single provider. That's the vision behind our new CEP!

With Common Tool Schemas, we're enabling interoperability between clients, allowing users to discover equivalent services, switch providers seamlessly, and compare offerings based on quality, cost, or trust. This is the original idea behind DVMs, where users announce a desired output and service providers compete to fulfill the job requirement in the best way possible.

🔧 Key features:

• Reference server pattern for canonical tool schemas
• RFC 8785 JCS for deterministic hashing
• CEP-6 announcements for discovery

We'd love to hear your thoughts and opinions on this proposal! Share your feedback and help us shape the future of ContextVM. You can just share your thoughts in the comments of this note, or in the issue

#ContextVM #CEP