Pricing and licensing

Use this page to decide whether you need a license key.

If you already know the gated method or runtime behavior you need, read Licensed features for the operational details before you buy.

Open license key page

First decision: do you need a key?

Start from the method or integration your workflow calls. The current docs mark licensed methods as restricted, insiders, or none in the generated method metadata. Methods marked none are not license-gated in the schema.

Feature	Decision	Next step
Your workflow only uses methods marked `none`	You do not need a license key for that method based on the current schema.	Run the workflow normally, then keep the generated API reference for your deployed version as the source of truth.
Your workflow calls a `restricted` method	You need a restricted license key before you rely on that gated behavior.	Buy or request the key through the license key page, then validate it against the host account and session you will run.
Your workflow calls an `insiders` method	You need insiders access before you rely on that gated behavior.	Use the purchase flow for the current insiders option, then test the exact method in the real runtime session.
You are unsure which method an integration calls	Do not buy based on the integration name alone.	Map the integration to the exact method or runtime behavior first, then decide from the licensed-feature metadata.

Current gated methods

The current licensed-feature page lists these gated methods. Treat this as a buying checklist, not a promise that every past or future build uses the same mapping.

Feature	License tier	Methods listed in the current docs
Restricted	`restricted`	`createGroup`, `joinGroupViaLink`, and `joinGroup`
Insiders	`insiders`	`getNumberProfile`, `checkNumberStatus`, `getOrder`, status and story methods, button and list message methods, starred message access, and profile picture methods listed on the licensed-feature page.

What a license key changes at runtime

You provide the key at launch

Supply the key through runtime config or the Easy API / CLI --license-key option.

The runtime checks the key

When the host account context is available, the runtime sends the key to the validation service and classifies the result before the client is marked ready.

The gated method still needs testing

A valid key is not a substitute for testing. Confirm the exact restricted or insiders method works in the same session and deployment you plan to run.

Integration buyers

Integrations do not need a separate license just because they are integrations. The license decision follows the behavior the integration calls.

Feature	License question	Buyer action
Webhooks	Does the webhook only receive normal runtime events, or does the workflow also call a gated method?	If it only receives ungated events, decide from the underlying method list. If it calls restricted or insiders behavior, buy for that gated behavior.
Chatwoot	Which open-wa methods does the Chatwoot bridge need for your support workflow?	Buy only if the bridge depends on restricted or insiders methods in your real workflow.
Node-RED	Which Easy API methods do your Node-RED nodes call?	Match those methods to the licensed-feature metadata before buying.
MCP	Which Easy API tools will the MCP client execute?	MCP exposes Easy API methods as tools, so the same method-level license decision applies.
Plugin SDK	Which methods or runtime behavior does the plugin call after it loads?	A plugin wrapper does not decide the tier. The called behavior does.

Team and organization buying

The current source-backed path for team or organization questions is the public license key page plus the project support paths. The docs do not define multi-seat terms, per-developer scope, customer deployment scope, transfer rules, or support service levels.

If more than one person, account, environment, or customer deployment is involved, do not assume the scope. Use the license key page first, then use Discord or the paid consult/support links from the project README if the purchase flow does not answer your buying question.

Before you buy

Feature	Check	Why it matters
Exact method or behavior	Name the restricted or insiders method your workflow depends on.	The current licensing guidance is method-level, not page-name-level.
Runtime session	Know which host account and session will run the workflow.	The licensed-feature docs tell readers to validate against the real host-account context.
Deployment path	Know whether the workflow runs through Easy API, custom code, MCP, Chatwoot, Node-RED, webhooks, or a plugin.	The wrapper can change the setup steps, but the license decision still follows the gated behavior.
Buying scope	For team or organization use, confirm unanswered scope questions through purchase or support.	The local sources do not publish team-seat or organization-license terms.

Buy or verify first

Read licensed-feature operations

Ask in Discord

Frequently asked questions

Where are the prices?+

Prices are shown in the purchase flow and may change. Open the license key page for the current purchase options.

Can I decide from an integration name like webhooks, Chatwoot, Node-RED, MCP, or plugin SDK?+

No. Decide from the exact method or runtime behavior the integration calls. Webhooks, Chatwoot, Node-RED, MCP, and plugin SDK workflows only need a key when the behavior they rely on is marked restricted or insiders.

What if I need team or organization licensing?+

Use the license key page first. If the purchase flow does not answer your team or organization scope question, use Discord or the paid consult/support links from the README. The docs do not publish multi-seat terms.

What should I read before buying?+

Read [Licensed features](/docs/licensing/licensed-features), identify the exact gated method, then validate the key in the real host-account session after purchase.

Was this helpful?

Wally and his cute companion coffee mug are coding day and night to keep this up-to-date!