Labs64 NetLicensing for AI agents

Labs64 NetLicensing is a license management service that lets software vendors track and control license distribution for their products, from trials through renewals. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Labs64 NetLicensing See the 2 actions ↓

Developer toolsAPI keyMCP + RESTnetlicensing.io

AUDIT LOG · LABS64 NETLICENSINGPOLICY: acme-support

09:41:09 · claude · u_8f2write

labs64_netlicensing.license_list

List Licenses✓ approved · approved by user

EVERY LABS64 NETLICENSING CALL, ON THE RECORD

01 · USE CASES

What agents do in Labs64 NetLicensing.

List issued licenses

Pull the current list of licenses issued for a product to check activation status.

Review product license inventory

List the products under a vendor account before deciding which needs new licenses.

Read-only license audit

Read licenses across products for a compliance check without modifying any records.

02 · ACTIONS

2 Labs64 NetLicensing actions, graded by risk.

Every Labs64 NetLicensing action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

No read actions.

write

Create and change things. Allow, or ask the user first.

labs64_netlicensing.license_list
List Licenses
labs64_netlicensing.product_list
List Products

destructive

Delete, cancel or archive. Ask first, or deny outright.

No destructive actions.

03 · HOW IT WORKS

Labs64 NetLicensing in three steps.

01Your users connect Labs64 NetLicensingThey add their Labs64 NetLicensing api key on Arc0 Connect, under your brand. It goes straight into the vault.
02You set the rulesReads run, and writes like “list Licenses” can wait for the user to approve.
03Any agent can actYour agent calls Labs64 NetLicensing through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.

POLICY.TS

await arc0.policies.set('labs64_netlicensing', {
  read: 'allow',
  write: 'ask',        // license_list
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2

04 · AUTH AND DATA

How Labs64 NetLicensing connects.

Users add their Labs64 NetLicensing api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Labs64 NetLicensing connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH: API key
CREDENTIALS: Per-tenant encrypted vault
MODEL SEES: Results only, never credentials
AUDIT LOG: Every call, on every plan

05 · WORKS WITH

Use Labs64 NetLicensing from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

More developer tools apps.

Addressfinder17 actions

Addresszen2 actions

Alchemy36 actions

ALL DEVELOPER TOOLS APPS →

07 · FAQ

Labs64 NetLicensing and Arc0, answered.

Q01

Can I use Labs64 NetLicensing with Claude, ChatGPT or Cursor?

Yes. Connect Labs64 NetLicensing to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Labs64 NetLicensing actions you allow.

Q02

How do users connect Labs64 NetLicensing?

Users add their Labs64 NetLicensing api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Labs64 NetLicensing actions can my agent take?

2 in total: 0 read, 2 write and 0 destructive, such as “list Licenses”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Labs64 NetLicensing?

Yes. Allow read actions and deny writes in the Labs64 NetLicensing policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Labs64 NetLicensing too?

Yes. The same Labs64 NetLicensing connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Labs64 NetLicensing into your agent.

Your users connect Labs64 NetLicensing once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.

Connect Labs64 NetLicensing Browse all apps →

Free to build · MCP + REST · Audit log on every plan