Cryptlex Web API

Name: Cryptlex Web API API
Brand: Cryptlex Web API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecuritySecrets Managementbearer284 EndpointsREST

For Agents

Issue and revoke software license keys, activate or deactivate machines, and manage customer entitlements for products distributed by Cryptlex.

Quickstart

Get started with Cryptlex Web API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"issue a software license key"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cryptlex Web API API.

Issue a node-locked or floating license key for a specific product and tie it to a customer record

Activate a license on a machine and return a signed activation response that the client app verifies offline

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

Block or unblock a license key when a refund is processed or a chargeback is detected

GET STARTED

Start building with Cryptlex Web API API

Explore with Jentic

View OpenAPI Document

Use for: I need to issue a license key for a customer who just bought my desktop app, Activate a Cryptlex license on a new machine and return the signed payload, Deactivate a license on a machine that the customer is decommissioning, Block a license key after a chargeback was filed

Not supported: Does not handle code obfuscation, payment processing, or DRM enforcement at the binary level — use for license key issuance and activation only.

Jentic publishes the only available OpenAPI document for Cryptlex Web API, keeping it validated and agent-ready.

The Cryptlex Web API powers software licensing for desktop, mobile, and on-premise applications. It manages products, license keys, activations, customers, releases, and trials, and supports node-locked, floating, and consumption-based licensing models. The API exposes 284 endpoints covering activation logs, analytics, automated emails, billing, custom fields, and webhook management, with HTTPS-only access and a 50-request burst per 5-second window per IP.

Use Cases

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

★ Desktop App License Issuance

Issue per-customer license keys when an order is fulfilled in a payment processor like Stripe or Paddle. The Cryptlex API creates the key, attaches customer metadata, and returns a key string that the order email template embeds. This replaces hand-rolled license servers and centralises analytics across products and platforms.

Call POST /v3/licenses with productId, customerId, and validity to create a license key, then return the key field to the order fulfilment workflow.

Activation Fraud Investigation

When support suspects license sharing, an agent can pull the activation log for a license, count distinct machine fingerprints, and block the key if the threshold is exceeded. The /v3/activations and /v3/activation-logs endpoints expose every activation attempt with timestamp, IP, and machine ID, and /v3/licenses supports immediate blocking. The whole flow can be run as an async investigation pipeline rather than manual log inspection.

Call GET /v3/activation-logs with licenseId filter, count distinct machineFingerprint values, and if greater than the policy threshold call PATCH /v3/licenses/{id} to block.

Trial-to-Paid Conversion

Convert an existing trial license to a paid subscription without forcing the customer to reactivate. The agent looks up the trial license by customer email, extends the expiry through the license update endpoint, and clears the trial flag. Combined with Cryptlex's automated email triggers, this powers a frictionless upgrade path when a payment webhook fires from the billing provider.

Find the license via GET /v3/licenses with customerEmail filter and update it through PATCH /v3/licenses/{id} with the new expiresAt and isTrial=false.

AI Agent License Operations

Customer success agents built on Jentic can resolve common licensing tickets like 'activate me on a new laptop' or 'I lost my key' without escalating to engineering. The agent searches Jentic for the right operation, loads its schema, and executes it against Cryptlex with credentials drawn from the vault. Bearer tokens never appear in the agent context, and every action is logged in Cryptlex's activity feed for audit.

Search Jentic for 'deactivate a software license on a machine', load the Cryptlex deactivation operation, and execute it with the licenseId and machineFingerprint provided by the customer.

Key Endpoints

284 endpoints — the cryptlex web api powers software licensing for desktop, mobile, and on-premise applications.

METHOD

PATH

DESCRIPTION

POST

/v3/licenses

Create a license key for a customer and product

GET

/v3/licenses/{id}

Retrieve a license and its policy

PATCH

/v3/licenses/{id}

Update, block, or extend a license

GET

/v3/activations

List activations for a license

GET

/v3/activation-logs

Inspect activation log entries

POST

/v3/customers

Create a customer record

GET

/v3/products

List products and policies

POST

/v3/licenses

Create a license key for a customer and product

GET

/v3/licenses/{id}

Retrieve a license and its policy

PATCH

/v3/licenses/{id}

Update, block, or extend a license

GET

/v3/activations

List activations for a license

GET

/v3/activation-logs

Inspect activation log entries

Why though Jentic?

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

Credential isolation

Cryptlex bearer JWTs are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens and never see the raw JWT, so a compromised agent process cannot exfiltrate license issuing credentials.

Intent-based discovery

Agents search by intent (for example 'issue a software license' or 'deactivate a license on a machine') and Jentic returns the matching Cryptlex operation with its input schema across the 284 endpoints.

Time to first call

Direct Cryptlex integration: 2-4 days for auth, license lifecycle, and activation log handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cryptolens Web API

Software licensing platform with similar key management and activation features

Choose Cryptolens when the team prefers its query-string token auth model or already uses its .NET-friendly client SDKs.

Complementary

Stripe API

Subscription billing and payment processing platform

Use Stripe alongside Cryptlex when subscription state in Stripe should drive license validity in Cryptlex via webhooks.

Complementary

Paddle API

Merchant of record for SaaS and software sales with built-in tax handling

Use Paddle when the seller wants tax compliance handled and Cryptlex to manage the resulting license keys.

FAQs

Specific to using Cryptlex Web API API through Jentic.

What authentication does the Cryptlex Web API use?

Cryptlex uses HTTP bearer JWT authentication. Every request to /v3/* must include an Authorization header with a Bearer token issued from the Cryptlex dashboard. Through Jentic the token is stored in the vault and never enters the agent context.

Can I issue floating licenses with the Cryptlex Web API?

Yes. Cryptlex supports node-locked, floating, and consumption-based licenses. Set the license type and allowedActivations on the product policy, then call POST /v3/licenses to issue a key bound to that policy.

What are the rate limits for the Cryptlex Web API?

Cryptlex enforces a maximum burst of 50 requests per 5-second window per IP regardless of authentication. The headers X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset on every response report current usage.

How do I activate a license on a customer machine through Jentic?

Search Jentic for 'activate a software license' and execute the loaded Cryptlex operation with licenseKey and machineFingerprint as inputs. The response is a signed activation payload the client app stores and verifies offline.

Is the Cryptlex Web API free?

Cryptlex offers a free tier with limits on monthly activations and a paid plan that scales with active licenses. The Web API itself is included in every paid plan; pricing is published at https://cryptlex.com/pricing.

How do I block a license after a chargeback?

Call PATCH /v3/licenses/{id} with suspended=true to freeze activations immediately, or set revoked=true to permanently invalidate the key. Both states are reflected in the next activation request the client makes.