Cryptolens Web API

Name: Cryptolens Web API
Brand: Cryptolens Web API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecuritySecrets ManagementapiKey10 EndpointsREST

For Agents

Activate, block, and extend Cryptolens license keys, and manage the customers and products attached to them.

Install Jentic One Beta

Connect the Cryptolens Web API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cryptolens Web API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cryptolens Web API.

Activate a Cryptolens license key on a customer machine and return a signed activation payload

Deactivate a license key on a specific machine to free an activation slot when hardware changes

Block a license key immediately after a chargeback or fraudulent purchase

GET STARTED

Start building with Cryptolens Web API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cryptolens Web API for, with concrete tasks.

★ Per-Order License Provisioning

When an order is fulfilled in a payment processor like Stripe, the Cryptolens API issues a fresh license key, attaches it to the customer record, and returns a key string the order email template embeds. The licensing service handles activation enforcement client-side, and the API call slots cleanly into a webhook handler. Integration is small because the licensing flow only depends on the key, customer, and product resources.

Call /key/CreateKey with productId and the customer email to issue a key, then return the key field to the order fulfilment workflow.

Hardware Switch Self-Service

Let customers move their software activation from an old laptop to a new one without a support ticket. The agent calls /key/Deactivate against the old machine fingerprint, then /key/Activate against the new one, returning the signed activation response that the desktop client stores. Because activation count limits are enforced server-side, the customer cannot exceed their entitled seats.

Call /key/Deactivate with the old MachineCode, then /key/Activate with the new MachineCode, and return the signed activation payload.

Chargeback and Fraud Response

When a chargeback is filed, the support team needs to disable access immediately while the dispute is investigated. The Cryptolens API exposes /key/BlockKey for instant revocation and /key/UnblockKey to restore access if the dispute is resolved in the customer's favour. This avoids forcing engineering to manually update license records in a database.

Call /key/BlockKey with the productId and key string when the chargeback webhook fires, and /key/UnblockKey if the dispute is reversed.

AI Agent License Self-Service

An AI agent in a customer success workflow can resolve common licensing tickets like activation, deactivation, and expiry extension without engineering involvement. Through Jentic the agent searches for the right Cryptolens operation, loads its schema, and executes against the access token stored in the vault. The query-string auth is invisible to the agent because Jentic appends it during execution.

Search Jentic for 'activate a Cryptolens license', load the /key/Activate operation, and execute it with productId, key, and MachineCode supplied by the customer.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for cryptolens web api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/key/Activate

Activate a license key on a machine

POST

/key/Deactivate

Deactivate a license key on a machine

POST

/key/BlockKey

Block a license key

POST

/key/UnblockKey

Unblock a previously blocked key

POST

/key/ExtendLicense

Extend the expiry date of a license

POST

/key/CreateKey

Create a new license key

POST

/key/GetKey

Retrieve a license key and its status

POST

/customer/AddCustomer

Create a customer record

POST

/key/Activate

Activate a license key on a machine

POST

/key/Deactivate

Deactivate a license key on a machine

POST

/key/BlockKey

Block a license key

POST

/key/UnblockKey

Unblock a previously blocked key

POST

/key/ExtendLicense

Extend the expiry date of a license

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Cryptolens access tokens are stored encrypted in the Jentic vault (MAXsystem) and appended to each request as the token query parameter at execution time. The agent never sees the raw token, so a leaked transcript cannot be replayed.

Intent-based discovery

Agents search by intent (for example 'activate a software license' or 'block a license after a chargeback') and Jentic returns the matching Cryptolens operation with its input schema.

Time to first call

Direct Cryptolens integration: 1-2 days for auth, activation flow, and webhook handlers. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Cryptolens Web API through Jentic.

Why is there no official OpenAPI spec for Cryptolens Web API?

Cryptolens does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cryptolens Web API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cryptolens Web API use?

Cryptolens uses an access token supplied as the query string parameter named token. Tokens are issued from the Cryptolens dashboard. Through Jentic the token is stored in the vault and appended at execution time so it never appears in the agent context.

Can I extend a license expiry through the Cryptolens Web API?

Yes. Call /key/ExtendLicense with the productId, key, and the number of days to add. The API returns the updated license expiry date, which the client app verifies on next activation.

What are the rate limits for the Cryptolens Web API?

Cryptolens does not publish a hard request rate limit; activation throughput is governed by the plan's monthly activation quota. Inspect the dashboard for plan-level limits before bulk operations.

How do I activate a license through Jentic?

Search Jentic for 'activate a Cryptolens license' and execute the loaded operation against /key/Activate with productId, key, and the MachineCode produced by the desktop client. Jentic injects the token query parameter from the vault.

Is the Cryptolens Web API free?

Cryptolens has a free tier and paid plans that scale with active licenses. The Web API is included in every plan; pricing is published at https://cryptolens.io/pricing.

How do I block a license after a refund?

Call /key/BlockKey with the productId and key when the refund webhook fires. The next call to /key/Activate from the client returns a blocked status, which the desktop app uses to disable access.

Cryptolens Web API

Connect the Cryptolens Web API to your agent

Capabilities

Start building with Cryptolens Web API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs