Serving agents over MCP is becoming consensus — and you can charge for access
pritisinghhhh · x · 2026-10-31
Retweeting @ashpreetbedi's take: serving agents over MCP is becoming a consensus idea, and developers should consider charging for access to their agents.
The core logic: if you've already built an agent that knows how to use your product, why not let other agents talk to it? If it improves the experience, people and agents will pay for it — an "agent as an interface" monetization path for product builders.
More from coding & agent
- Chrome sandbox escape still lurks in cached Playwright Chromium inheriting your IDE's macOS permissions — flngr · 2026-10-31
- How to Give Your AI Dot Real Responsibilities: Beyond Reminders to Ongoing Delegation — nickbaumann_ · 2026-10-31
- Socket: Malicious Claude Code 2.1.313 Extension Removed From Cursor Marketplace, Early Reports Overblown — zeeg · 2026-10-31
- Dev laments spending 75% of his time waiting for coding agents to finish — RileyRalmuto · 2026-10-31
- Dev says Opus 5.5 leads on productivity, keeps GPT Pro subscription anyway — kevinkern · 2026-10-31
- GitHub demos Chopin, an experiment in multiplayer planning for the agentic era — 0xkarasy · 2026-10-31