Reads live license records and the product catalogue so entitlement questions get answered from the licensing system, not from memory.
2actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves all products in your licensing system. Your team knows what's available to assign to customers.
Ayro retrieves all licenses across your system. Your team tracks which customers have active access.
Each card is one request a support team gets, and the Labs64 netlicensing actions Ayro runs to close it.
Ayro pulls the customer's license record from NetLicensing and reports its current state, so a question about whether a key is still valid is answered from the licensing system rather than escalated.
Ayro retrieves the product catalogue and matches the customer's license to the product it belongs to, so an entitlement question gets a specific answer instead of a link to the pricing page.
When a licensing problem needs a human, Ayro attaches the matching license and product records to the conversation so the agent opens it already knowing what the customer is entitled to.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Labs64 netlicensing actions it has and picks the ones a request needs.
Authorize the Labs64 netlicensing account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Labs64 netlicensing actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeLabs64 netlicensing · Ayro
What can you do in Labs64 netlicensing without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Labs64 netlicensing.
No. This toolkit is read-only: it exposes List Licenses and List Products and nothing that writes. Ayro can tell a customer what their license record says and hand the conversation to an agent, but the license itself is still created or changed inside NetLicensing.
All 2 actions your agent can call on Labs64 netlicensing, straight from the live MCP connection.
List all licenses.
Retrieve a list of all products.
Same connection, same setup. Pick the next one your team already uses.
Reads pages that expose no API, drives portal and form work to completion, runs versioned browser tasks by name, and reuses saved login profiles.
Confirms token details, lists the organizations and connected agents a token reaches, and returns the webhook IPs a firewall needs to allow.
Provisions Droplets, databases, and clusters on request, reports what is running, edits DNS records, and keeps resource tags and firewalls in order.
Reports check-ins, deployments, exceptions, and custom events into Honeybadger, and uploads the source maps behind readable stack traces.
Sends batches of templated email, explains bounces and complaints from real statistics, manages per-stream suppressions, and spam-scores a draft.
Brings domains under Certificate Transparency monitoring, lists unexpired issuances, inspects a single event, and silences known certificates.

Authorize the account and your agent has all 2 actions from the first conversation.
