Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Certifier 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%2Fcertifier.me%2Fcertifier" | shStep 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%2Fcertifier.me%2Fcertifier" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Certifier API.
Create, issue, and send digital certificates and badges to recipients
Produce, issue, and deliver a credential in one create-issue-send call
Search and list issued credentials for a recipient
Define credential templates that set what a credential contains
Apply design templates to brand each certificate
GET STARTED
Record recipient interactions with issued credentials
Patterns agents use Certifier API for, with concrete tasks.
★ AI Agent Certificate Delivery
An AI agent connected through Jentic can hand out a certificate on request: it builds the credential from a template for a recipient, issues it, and emails it. The create-issue-send operation collapses those steps into one call, so the agent completes delivery in a single action.
Build a certificate from a template for a recipient, issue it, and email it to them
Event and Membership Badges
Recognize attendance or membership by issuing a badge tied to a credential template. Certifier fills recipient details from the issue request and delivers the badge, which fits automated flows triggered after an event or renewal.
Issue an event-attendance badge from a template to a recipient and send it
Branded Certificate Templates
Keep certificates consistent by pairing a credential template with a design template before issuing. Certifier exposes both template types so an integration picks the right content and look for each program.
Create a credential template that references a chosen design template
Credential Lookup
Support recipients by searching issued credentials and reading their interaction records. Certifier lists credentials and credential interactions so a workflow can confirm what was issued and whether it was opened.
Search credentials for a recipient email and return each one's status and interactions
19 endpoints — the certifier api issues and sends digital certificates and badges to recipients from reusable templates.
METHOD
PATH
DESCRIPTION
/v1/credentials
Create a credential
/v1/credentials/create-issue-send
Create, issue, and send a credential in one call
/v1/credentials/{id}/issue
Issue a credential
/v1/credentials/{id}/send
Send a credential
/v1/credentials
List credentials
/v1/groups
Create a credential template
/v1/designs
List design templates
/v1/credentials
Create a credential
/v1/credentials/create-issue-send
Create, issue, and send a credential in one call
/v1/credentials/{id}/issue
Issue a credential
/v1/credentials/{id}/send
Send a credential
/v1/credentials
List credentials
/v1/groups
Create a credential template
/v1/designs
List design templates
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Certifier by hand means handling its bearer-token auth and tracking the credential, design, template, and interaction paths yourself. Through Jentic you install once, import Certifier from the API Directory, store the token once, and your agent calls it.
Permission scoping
You choose which Certifier operations the agent may call, such as creating and sending certificates, so operations like deleting credentials or templates are not included unless you add them.
Credential isolation
Your Certifier access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send a certificate' or 'issue a badge', and Jentic returns the matching Certifier operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Certifier API through Jentic.
What authentication does the Certifier API use?
The Certifier API authenticates with a bearer access token sent in the Authorization header, per its OpenAPI spec. You create and manage tokens in the Certifier dashboard, and through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never appears in the agent's prompt or logs.
Can I send a certificate in one call with the Certifier API?
Yes. Besides the separate create, issue, and send operations, the API offers a create-issue-send operation that builds a credential from a template, issues it, and delivers it to the recipient in a single request. This fits fully automated badge and certificate flows.
Is there a Certifier MCP server?
You do not need an MCP server to give your agent the Certifier API. Jentic connects it directly from the API Directory: import Certifier, store your token once, and your agent issues and sends certificates through the operations the API already exposes. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.
Can I limit what my agent is allowed to do with the Certifier API?
Yes. Write a rule that allows only the operations the agent needs, for example creating and sending certificates, and leave out operations like deleting credentials or templates. The agent can deliver certificates within those bounds, and every call it makes is logged.
How do I send a certificate through Jentic with the Certifier API?
Search Jentic for 'send a certificate', which returns the Certifier operation with its input schema, then supply the template and recipient details and the agent runs it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Issue and send digital certificates and badges from templates, apply branded designs, and track recipient interactions through the Certifier API.
Use for: Issue a certificate to a program graduate, Create a digital badge for a recipient, Search for certificates issued to an email address, List the design templates on my account
Not supported: Does not handle identity verification, exam proctoring, or course delivery. Use for issuing and sending digital certificates and badges only.
The Certifier API issues and sends digital certificates and badges to recipients from reusable templates. It controls each credential's look through design templates and its content through credential templates, and a single create-issue-send operation produces, issues, and delivers a credential in one request. Credential search, listing, and recipient interaction records support the issuing workflow.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>