Build on Ploba

Sell access to your MCP server or API through Ploba. Check that a user holds a valid licence, report what they use, and let Ploba keep the subscriptions and credits.

Get started

How it fits together

Your users subscribe to your product on Ploba and get a licence key. Your server checks the key, does the work and reports usage. Ploba keeps the subscription, the credits and your earnings in the maker console.

  1. Your userCalls a toolPLOBA_LICENSE_KEY
  2. Your MCP server or APIChecks the key, does the workwithPlobaAuth()
  3. Ploba APILicence and usageverify-license · report-usage

The basics

Base URLhttps://api.ploba.app/api/v1/external/developer
AuthenticationAuthorization: Bearer <secret key> from the maker console
KeysTest and live. Each can expire, be regenerated or be revoked.
FormatJSON in, JSON out: { message, code, success, data }

A first request

Check a licence key with your secret key. The full walk-through is in the quickstart.

curl -X POST https://api.ploba.app/api/v1/external/developer/verify-license \
  -H "Authorization: Bearer $PLOBA_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "licenseKey": "<the user's licence key>" }'

Help

Stuck, or found something wrong in these docs? Contact maker support. Changes to Ploba are listed in the changelog.

Last updated Oct 9, 2026Report a problem with this page