Devolens / Cryptolens for AI agents

Cryptolens, from Devolens, is a software licensing API for issuing license keys, managing customers, and tracking product usage and entitlements. 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.

Developer toolsAPI keyMCP + RESTcryptolens.io
AUDIT LOG · DEVOLENS / CRYPTOLENSPOLICY: acme-support
09:41:07 · claude · u_8f2read
devolens_cryptolens.list_messages
List Messages✓ allowed · 212ms
09:41:08 · claude · u_8f2read
devolens_cryptolens.list_products
List Products✓ allowed · 164ms
EVERY DEVOLENS / CRYPTOLENS CALL, ON THE RECORD
01 · USE CASES

What agents do in Devolens / Cryptolens.

01

Look up a customer's license

Retrieve a specific license key and its status when a customer support ticket asks about activation limits.

02

Pull daily usage aggregates

Fetch usage analytics for a product over a date range to spot accounts approaching their seat limit.

03

Review license users before changes

List the users tied to a license key as a read-only check before anyone edits access.

02 · ACTIONS

10 Devolens / Cryptolens actions, graded by risk.

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

read

10

Look things up. Allowed by default.

  • devolens_cryptolens.list_messages
    List Messages
  • devolens_cryptolens.list_products
    List Products
  • devolens_cryptolens.list_customers
    List Customers
  • devolens_cryptolens.list_resellers
    List Resellers
  • devolens_cryptolens.get_license_key
    Get License Key
  • devolens_cryptolens.list_license_keys
    List License Keys
  • devolens_cryptolens.list_web_api_logs
    List Web API Logs
  • devolens_cryptolens.list_license_users
    List License Users
  • devolens_cryptolens.list_license_templates
    List License Templates
  • devolens_cryptolens.list_daily_usage_aggregates
    List Daily Usage Aggregates

write

0

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

  • No write actions.

destructive

0

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

  • No destructive actions.
03 · HOW IT WORKS

Devolens / Cryptolens in three steps.

  1. 01Your users connect Devolens / CryptolensThey add their Devolens / Cryptolens api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Devolens / Cryptolens 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('devolens_cryptolens', {
  read: 'allow',
  write: 'ask',        
  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 Devolens / Cryptolens connects.

Users add their Devolens / Cryptolens 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 Devolens / Cryptolens 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 Devolens / Cryptolens from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Devolens / Cryptolens and Arc0, answered.

Q01

Can I use Devolens / Cryptolens with Claude, ChatGPT or Cursor?

Yes. Connect Devolens / Cryptolens 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 Devolens / Cryptolens actions you allow.

Q02

How do users connect Devolens / Cryptolens?

Users add their Devolens / Cryptolens 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 Devolens / Cryptolens actions can my agent take?

10 in total: 10 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Devolens / Cryptolens?

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

Q05

Can my own backend call Devolens / Cryptolens too?

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

Get started

Plug Devolens / Cryptolens into your agent.

Your users connect Devolens / Cryptolens once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.

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