What is MPP? Micropayments for Proxy Infrastructure

The Problem MPP Solves

To access a paid API or service today, you create an account, generate an API key, add a credit card, and get billed monthly. When a person is driving, this is fine.

It breaks for AI agents. An LLM agent can’t fill out a signup form. It can’t verify an email address or wait for a compliance review. If your agent needs proxy access mid-task and the only way to get it is through a human clicking a dashboard, your pipeline isn’t autonomous.

MPP embeds payment directly into HTTP. An agent sends a request, receives a payment challenge, pays in stablecoins, and gets access in a single round-trip. No account creation, no API key management, no human approval.

How MPP Works

1. Your agent makes an HTTP GET to a payment-gated endpoint (e.g. /api/mpp/us_residential_1gb).
2. Instead of blocking the request or redirecting to a login page, the server returns HTTP 402 with payment details: amount, currency, and recipient address on-chain.
3. The agent (or the mppx client library) submits a stablecoin transaction matching the payment challenge — USDC on Solana via Tempo.
4. Once the transaction confirms, the server returns SOCKS5 proxy credentials. The whole flow takes under 3 seconds.

Why MPP Matters for Proxy Infrastructure

Traditional proxy providers gate access behind accounts and API keys. Each layer creates friction an agent can’t resolve on its own:

• Your agent can’t sign up for Bright Data or Oxylabs. A human creates the account and submits KYC documents before a single request goes through.
• API keys get rotated, revoked, and expire. Your agent needs logic to track key lifecycle, which is unrelated to the task you built it for.
• Monthly subscriptions and manual top-ups require a person watching the balance. If your agent runs out of credits at 3 AM, it sits idle until you wake up and refill.
• Enterprise providers demand contracts, KYC documents, and sales calls. An agent can’t negotiate a contract or upload a passport.

MPP folds payment into the request itself. Your agent pays for the bandwidth it needs, when it needs it. The payment is the authentication. No account, no key, no human involved.

How ProxyBase Uses MPP

ProxyBase exposes proxy packages through MPP-gated endpoints. Each package (1GB US residential, 5GB Germany mobile) has a dedicated URL. When your agent hits that URL:

• The mppx/nextjs middleware intercepts the request and returns a 402 payment challenge.
• Your agent pays the challenge in USDC via Tempo on Solana, using the mppx client.
• After payment confirms, the route handler provisions a SOCKS5 proxy and returns the credentials in the response body.
• Your agent connects and routes traffic through a clean residential IP. No signup.

Your AI agent provisions its own proxy access. If it needs a German residential IP for a task, it pays for one and gets one. If it needs to rotate, it pays for another. All programmatic, no human in the loop.