$MONGO402 Is Live! Pay-Per-Query MongoDB. Cloud data without subscriptions, API keys, or backend infrastructure. Each request triggers an HTTP 402 payment → you get the result instantly. Turning any MongoDB into an instant data business. ca:

Caching update is live. • Redis-based query caching per endpoint • Configurable TTL + discounts for cached results • Buyers get faster, cheaper queries or can bypass cache • Safe fallback to MongoDB if Redis is down Plus a seller analytics dashboard for revenue and usage.

We’ve added a live demo of the Analytics Dashboard. Track revenue, paid queries, buyers, and usage over time per endpoint. Daily, weekly, monthly breakdowns. When you monetize data per query, analytics isn’t optional. Now it’s built in.

Join our X Community: https://t.co/mVcCVv1oso

What does pay-per-query MongoDB actually look like? In this demo we: – connect with Phantom – run mongo402 in demo mode – send a paid query to a demo database (0.005 USDC) – filter books by author Then we plug in a real MongoDB, send a live find query, watch the transaction

Dev supply is locked: https://t.co/LFTmY5xEb4

Paid data access becomes as simple as opening a Mongo endpoint. No keys. No accounts. No payment platforms. Just MongoDB → 402 → payment → result. A new way to think about data.

You can now try creating a MongoDB endpoint in demo mode, directly on the site. Set a price, connect a collection, choose allowed operations, see how it works end to end. A hands-on preview of how pay-per-query MongoDB works.

This changes how access control is modeled. Authorization is no longer identity-based or quota-based, but settlement-based. The proxy deterministically decides whether a query may execute by verifying a specific on-chain payment tied to that request. No persistent user state

The hardest part of selling data isn’t storage or queries — it’s enforcing payment at execution time. mongo402 sits directly in front of MongoDB and controls query execution at the proxy layer. Queries are priced, invoices are returned via HTTP 402, and execution happens only

The hardest part of selling data isn’t storage or queries — it’s enforcing payment at execution time. mongo402 sits directly in front of MongoDB and controls query execution at the proxy layer. Queries are priced, invoices are returned via HTTP 402, and execution happens only

Smart Caching is live on Mongo402. Cache query results and discount repeat requests. • Instant responses • Up to 100% cheaper cached queries • Less load on MongoDB Set TTL (1 min–24h) + discount (0–100%). Buyers see "is_cached" + actual price paid. Same 402 flow. Smarter

SaaS billing with Mongo402 is simply nothing. SaaS: API keys, auth, dashboards, subscriptions, usage tracking. Weeks to sell one dataset. Mongo402: POST a query → HTTP 402 with a price → pay in USDC/SOL → result instantly. This is far easier than traditional SaaS billing.

Why HTTP 402? Because payment should be part of the request flow. Unpaid query → 402 with a price. Paid query → result. No keys. No accounts. No billing layer. Payment gates the query.

#4 Mongo402 is open-source. Faster time-to-revenue for data owners and zero integration overhead. Try the repo and the example endpoint.

#3 Client pays (USDC or native SOL) in response to the 402, the query executes, and there’s no separate billing system or account onboarding.

#2 Mongo402 removes all that friction — expose a MongoDB collection as a paid endpoint. Unpaid requests return HTTP 402.

#1 Nowadays data monetization is broken. APIs, keys, billing, auth and infra add so much friction that most datasets never ship.

Mongo402 is going open-source! Pay-per-query MongoDB via x402 + USDC on Solana. GitHub: https://t.co/ncnUUIuUmu