Skip to content

Integrate Monaiq

This section puts Monaiq into your app, so it checks what each customer is licensed for. It is for you or your AI assistant; selling needs none of it.

If your AI assistant builds your app, install the Monaiq plugin and ask it to add licensing. The two other paths do the same job by hand.

Install the plugin (two commands in Claude Code; GitHub Copilot and Codex have their own install), sign in with a code we email you, and ask. Its tools build your catalog (products, features, offerings) and hand back the integration: the base wiring, a feature check, and an embedded purchase flow. They return instructions and snippets; your assistant edits and you review.

Pick this if an assistant already writes your code; it does the catalog work too, which is the part that is easy to get wrong. AI-assisted setup

Point any MCP client at https://api.monaiq.com/mcp. The URL is the whole setup: no API key, no session key. The first request starts a sign-in you confirm with a code we email you, and you get the same tools as the plugin.

Pick this if you already work in your own MCP client and want the tools there. Connect over MCP

Both SDKs do the same work: authorize a credential, read the features it unlocks, and enforce them.

Connect, in the portal’s Developers area (monaiq.com/manage/connect), shows the code that checks a license in C#, TypeScript and HTTP with your account id and the product’s id already filled in.

Pick this if you want to see every call yourself, or your code already has its own shape; the assisted paths produce ordinary SDK code anyway.

Licenses and their seats are not reachable over MCP: no tool finds, creates, changes or reads one, or issues or revokes a license code. That is portal work at monaiq.com, or the management API from your backend. Customers, invoices and analytics are portal work too.

Every path other than MCP itself needs a credential from your account. See Credentials and keys.