Getting started
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
- QuickstartCreate a test key and verify your first licence key.
- AuthenticationSecret keys, the Bearer header, test and live.
- How licensing worksLicences, subscriptions and when to check a key.
- Protect an MCP serverRequire a licence for tool calls in one line.
- Report usageRecord each tool call and deduct credits.
- API referenceEvery endpoint, request and response.
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.
- Your userCalls a tool
PLOBA_LICENSE_KEY - Your MCP server or APIChecks the key, does the work
withPlobaAuth() - Ploba APILicence and usage
verify-license · report-usage
The basics
| Base URL | https://api.ploba.app/api/v1/external/developer |
| Authentication | Authorization: Bearer <secret key> from the maker console |
| Keys | Test and live. Each can expire, be regenerated or be revoked. |
| Format | JSON 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.