Licensing
How licensing works
When someone subscribes to your product on Ploba, they get a licence key. Your server checks that key before doing paid work.
The life of a licence
A user subscribes
They pick a plan for your product on Ploba. The subscription is tied to your product and organisation.Ploba issues a licence key
The user adds it to their client, for an MCP server usually as the PLOBA_LICENSE_KEY environment variable.Your server checks it
On each request, or once and then from a short cache, call verify-license or use the SDK.It stays valid while it's active
A licence has anissued_atand anexpires_at. Only active licences verify.
When to check
- Check before work that costs you money or that only subscribers should get.
- Cache a successful check for a few minutes so repeat calls stay fast. The SDK caches for 15 minutes by default.
- Leave free actions open. The SDK only guards tool calls; listing your tools stays public, so clients can see what you offer.
What a check tells you
A successful check returns the licence’s status, plan_tier, the product (appName, appSlug) and its dates. Use the plan to unlock plan-specific features. See the reference for every field.