Install Jentic One Beta

Connect the Perlego Partner API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Perlego Partner 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fperlego.com%2Fperlego" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fperlego.com%2Fperlego" | 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 Perlego Partner API.

List the users under a partner account

Create a new user and update an existing user record

Read the entitlements that grant a user library access

Grant an entitlement to a user

Remove an entitlement from a user

GET STARTED

Start building with Perlego Partner API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Perlego Partner API for, with concrete tasks.

★ Provision members for library access

Keep a partner's members in step with Perlego. The agent creates and updates user records so the people who should have reading access exist in Perlego, matching the partner's own membership list.

Create or update the user records so a partner's members exist in Perlego and are ready for entitlements.

Manage entitlements to the library

Control who can read through Perlego. The agent reads a user's entitlements and grants or removes them, so access matches a member's current plan or subscription status.

Read a user's entitlements, then grant or remove entitlements so their access matches their current status.

Start a reading session for a user

Hand a member into Perlego from a partner's own product. The agent mints an access token for the user so a reading session can start without the member managing separate Perlego credentials.

Mint an access token for the given user so a reading session can begin from the partner's product.

Reconcile access with membership

Keep library access honest as membership changes. The agent lists users and their entitlements so a partner can compare them against its own records and correct any drift.

List the users and read their entitlements so a partner can reconcile Perlego access against its own membership records.

Key Endpoints

8 endpoints — the perlego partner api lets a partner manage the users and access it provides to perlego's digital book library.

METHOD

PATH

DESCRIPTION

GET

/users

List the users under the partner account

POST

/user

Create a new user

GET

/user/{userId}

Read a single user

GET

/user/{userId}/entitlements

List a user's entitlements

POST

/user/{userId}/entitlement

Grant an entitlement to a user

GET

/users

List the users under the partner account

POST

/user

Create a new user

GET

/user/{userId}

Read a single user

GET

/user/{userId}/entitlements

List a user's entitlements

POST

/user/{userId}/entitlement

Grant an entitlement to a user

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Perlego Partner API by hand means provisioning API key or HMAC-SHA256 credentials, learning how users, entitlements, and access tokens relate, and mapping the endpoints. Through Jentic you install once, import the Perlego Partner API from the Jentic API Directory, configure your credentials, and your agent calls it.

Permission scoping

Provisioning users and changing entitlements sit behind the same credentials, and because Jentic One is self-hosted, your own rules decide which operations the agent may call. You can allow reading users and entitlements while withholding operations that grant or remove access, so the agent reaches only what you approved.

Credential isolation

Your Perlego API key or HMAC-SHA256 credentials are held encrypted by your own Jentic One instance and applied to requests only at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent, such as granting an entitlement or minting an access token, and Jentic returns the matching Perlego operation with typed inputs, so the agent calls the right one without hard-coding endpoints.

FAQs

Specific to using Perlego Partner API through Jentic.

What authentication does the Perlego Partner API use?

Each operation accepts one of two options: an API key sent in the x-api-key header, or an HMAC-SHA256 request signature. Through Jentic, whichever credentials you configure are held encrypted by your own Jentic One instance and applied to requests at execution time. Check Perlego's partner documentation for how to obtain them.

What does an entitlement control in the Perlego Partner API?

An entitlement is the grant that gives a user access to the Perlego library. You read a user's entitlements and grant or remove them, so a member's reading access matches their current plan or subscription.

What are the rate limits for the Perlego Partner API?

The OpenAPI description does not specify rate limits. Check Perlego's partner documentation for the limits on your account before provisioning users or entitlements in bulk.

Is there an MCP server for Perlego?

You don't need an MCP server to use the Perlego Partner API with your agent. Through Jentic, your agent finds the user and entitlement operations by intent and calls them directly, with your credentials injected at run time by your own Jentic One instance.

How do I connect the Perlego Partner API to my agent through Jentic?

To run it on your own infrastructure, install Jentic One from its GitHub repo, then import the Perlego Partner API from the Jentic API Directory and configure your API key or HMAC-SHA256 credentials. Your agent can then manage users and entitlements with those credentials injected at execution time.

Can I limit what my agent is allowed to do with the Perlego Partner API?

Yes. Because Jentic One is self-hosted, your own rules decide which Perlego operations the agent may call, so you can allow reading users and entitlements while withholding operations that grant or remove access. Your credentials stay encrypted on your own instance and are applied only when a permitted request runs.

Perlego Partner API

Name: Perlego Partner API
Brand: Perlego Partner API
Availability: InStock

AI ReadinessFoundational (C)54/100

See full scorecard

Community OpenAPI document · agent-readyEducationDigital Libraryapikey8 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage Perlego library access for a partner: create and update users, read and change their entitlements, and mint an access token for a user.

Use for: List our Perlego users, Create a new user for a member, Show a user's entitlements, Grant library access to a user

Not supported: Manages partner users, their entitlements, and access tokens for the Perlego library. Does not deliver book content or search the catalogue through these endpoints, and does not handle billing or payment for the subscription.

The Perlego Partner API lets a partner manage the users and access it provides to Perlego's digital book library. You create and update user records, read and change the entitlements that grant a user access to the library, and mint an access token for a user session. It is aimed at institutions, resellers, and platforms that give their own members reading access through Perlego and need to keep that membership and its entitlements in sync with their own systems.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

27%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

50%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

42%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

25%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Perlego Partner API to your agent

Capabilities

Start building with Perlego Partner API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Perlego Partner API

Jentic AI Readiness Score

Perlego Partner API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness