Use Cases

Every layer of the stack.
One payment primitive.

From autonomous AI agents to CI pipelines to composable multi-agent systems - HTTP 402 on Solana is the missing payment layer for machine-to-machine workflows.

402
HTTP status code
~800ms
Solana finality
$0.00025
avg tx fee
0
accounts needed
0human approvals required

Autonomous agents that pay their own way

LLM-powered agents browse, reason, and act - but today they can't pay for the premium data they need without a human handing them an API key. HTTP 402 closes that gap. Each agent session generates an ephemeral Solana keypair, funds it, and pays per query. No accounts. No billing dashboard. No key rotation.

Flow
  1. 01Agent receives a task from user
  2. 02Calls mppFetch() - no setup needed
  3. 03SDK auto-generates ephemeral keypair
  4. 04Faucet airdrops SOL (devnet/testnet)
  5. 05Server returns 402 with price
  6. 06SDK pays, retries, returns data
  7. 07Agent processes result, task complete
import { mppFetch } from "mpp-test-sdk";

// Research agent - pays for every query autonomously
async function researchAgent(topic: string) {
  // No API key. No pre-registration. Just fetch.
  const context = await mppFetch(
    `https://api.research.io/v1/search?q=${topic}`
  );

  const facts = await mppFetch(
    "https://api.factcheck.io/v1/verify",
    { method: "POST", body: JSON.stringify(await context.json()) }
  );

  // SDK paid 0.001 SOL per call. Agent never knew.
  return facts.json();
}
Overview

What you can build right now

Get Started

Your use case is one npm install away.

No wallet setup. No testnet faucet hunting. No billing integration. Just code.

npm i mpp-test-sdk