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

🌟 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