Make Your API Payable by AI Agents with MPP Discovery

Where this fits

You run an API that charges per generation request. A user's agent can call it, but it stalls when it hits a paywall—no way to discover cost or payment method. agent-ready-mpp solves that by publishing payment metadata in OpenAPI, letting agents find and pay for endpoints automatically.

Why agents benefit

• Agent can identify payable operations before calling, avoiding unexpected 402s.
• Reads exact amount, currency, and payment method (tempo, stripe, lightning, card) from x-payment-info.
• Distinguishes one-time charges from sessions, so it can choose the right flow.
• Can compare requirements across endpoints and quote costs to the user.
• Works with standard OpenAPI discovery—no custom protocol to implement.

Practical scenarios

Content generation API

An agent needs a generated image. It fetches /openapi.json, sees POST /api/generate with x-payment-info amount $0.01, method stripe. Agent initiates payment via MPP and submits the request.

Subscription-gated assistant

An API uses intent: session with tempo. The agent opens a session payment, gets access credentials, then makes multiple calls without repeated per-call charges.

Multi-vendor comparison

A shopping agent queries several APIs. Each declares payment methods and prices. The agent compares total cost and chooses one, then pays directly from the agentic workflow.

Add it to your agent workflow

Install the skill in your agent environment:

npx skills add fabricioctelles/skills --skill agent-ready-mpp

Then run your OpenAPI doc through the skill. Example output:

{
  "openapi": "3.1.0",
  "info": { "title": "My API", "version": "1.0" },
  "paths": {
    "/api/generate": {
      "post": {
        "x-payment-info": {
          "intent": "charge",
          "method": "stripe",
          "amount": "0.01",
          "currency": "USD"
        }
      }
    }
  }
}

The skill verifies that /openapi.json serves with HTTP 200 and each payable operation carries valid x-payment-info extensions.

Compare before adopting

Check how actively the skill is maintained: last commit date, open issues, and whether it tracks the MPP spec (paymentauth.org/draft-payment-discovery-00.txt). Compare with alternatives like custom payment endpoints or manual API documentation. For workflow fit, confirm your API can expose payment metadata without breaking clients that ignore unknown extensions. Quality signals matter because payment interoperability depends on consistent metadata.

Why it is worth tracking

This skill sits at the intersection of OpenAPI and machine payments, a space that is still young. The 74 GitHub stars and active repository show early developer interest, but evaluate it when you add paid endpoints or when agents become primary API clients. For a one-line summary of what this skill enables, see https://www.openagentskill.com/skills/fabricioctelles-agent-ready-mpp. Tracking it now means you'll be ready when MPP adoption reaches your toolchain.