ContextVM

The ContextVM website now has agent-native payments, building on the recently updated CEP-8. 🦾🤖

The CEP-8 update brought explicit gating to the payment lifecycle, the same approach that other protocols like 402 or mpp are following, and that small change is what makes agents able to pay natively. That's the building block for an economy where agents pay agents and tools over Nostr.

To make that loop real, the ContextVM site got a built-in Lightning wallet. Connect it once with a NWC string and it is ready across the app. You can check your balance, generate a QR to receive, or paste a bolt11 invoice to pay.

The wallet also shows up exactly where it counts: any Lightning payment card gets a Pay button, and after paying, you get a Retry call button that resumes the tool.

Agents that can spend and earn over Lightning, native to Nostr. Permissionless, seamless.

Try it: https://contextvm.org/

#Nostr #Lightning #Bitcoin #AI #Agents #NIP47

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

🚀 wotrlay v0.2.x is here

As wotrlay matures, we've identified and addressed edge cases where transient issues could temporarily affect user buckets. Timeouts, rate limits, and network conditions sometimes caused the relay to handle cache refreshes less gracefully than intended, which could result in users being downgraded when they shouldn't have been.

v0.2.x resolves this. The relay now preserves cached rank data when encountering these edge cases, ensuring users can continue publishing without issues. We've also replaced IP-based rate limiting for rank lookups with an approach that no longer penalizes users behind VPNs, and improved response handling to be more robust under real-world conditions.

We've also added a special condition for event kinds 0, 3, 10002, 10040, and 30382, which are now always accepted and are not affected by the rate limiting of the bucket algorithm.

For operators: just upgrade.

For users: your posting ability now stays consistent regardless of previously unhandled edge cases.

Docker builds are leaner and faster too.

Building reliable WoT infrastructure means continuously observing, fixing, and improving. v0.2.x represents that ongoing commitment 🫂

#nostr #wotrlay #wot

🌟 Release Time! 🌟

We’re thrilled to announce the new version of DVMCP! This update features support for the latest MCP specification, unlocking exciting possibilities and ensuring a future-proof design for the protocol.

🔧 Highlights:

• Full support for major MCP capabilities.
• Complete refactor of the dvmcp.fun website (currently at next.dvmcp.fun)
• New storage type for relays, enhancing ephemeral event handling.

Explore the available servers at next.dvmcp.fun and share your feedback/bugs over the next 10 days as we roll out new features to the main domain!

Read a more detailed article of this release at dvmcp.fun/blog/release-time

Thank you for joining us on this journey! Stay tuned for more updates! 🚀

#DVMCP #MCP #Nostr #Ai #LLM