Install Jentic One Beta

Connect the Algeria Certify API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Algeria Certify 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%2Falgeriacertify.com%2Falgeriacertify" | 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%2Falgeriacertify.com%2Falgeriacertify" | 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 Algeria Certify API.

Issue a verified digital certificate for an institution

List the certificates an institution has issued

Revoke an issued certificate by its id

Verify a certificate from its public token without any key

Fire Zapier triggers when a certificate is issued or revoked, and issue one via a Zapier action

GET STARTED

Start building with Algeria Certify API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Algeria Certify API for, with concrete tasks.

★ Agent-Issued Credentials on Completion

When a learner or applicant completes a program, an agent can issue a verified certificate through the institution endpoint and hand back a public verification token. Because verification is a public, keyless read, the recipient or a third party can confirm the certificate's authenticity from the token alone. This lets an agent close out a workflow by issuing a trusted, independently verifiable credential.

Issue a verified certificate for a named recipient through the institution endpoint, then confirm it by verifying the returned public token.

Public Certificate Verification

An agent checking a credential presented by a candidate can verify it from its public token without holding any institution key. The public verification read returns whether the certificate is valid and current, so a hiring or admissions flow can confirm authenticity in a single call. This separates verification, which anyone can do, from issuance, which only the institution can.

Verify a presented certificate from its public token and report whether it is valid or has been revoked.

Automating Issuance and Revocation Events

Because the API ships Zapier triggers for new and revoked certificates and a Zapier action to issue one, an agent can wire issuance and revocation into Zapier, Make, or n8n without custom polling. A trigger fires as certificates change state, and the action issues a certificate as a step in a larger flow. This makes certificate lifecycle events part of an automation rather than a manual task.

Subscribe to the new-certificate trigger, and when it fires, record the issued certificate's public verification token in a downstream system.

Key Endpoints

9 endpoints — the algeria certify api issues, verifies, and manages trusted digital certificates for institutions.

METHOD

PATH

DESCRIPTION

POST

/institution/certificates

Issue a verified certificate

GET

/institution/issued-certificates

List issued certificates

PATCH

/institution/certificates/{id}/revoke

Revoke a certificate by id

GET

/public/verify/{token}

Verify a certificate from its public token

POST

/zapier/actions/issue-certificate

Zapier action to issue a certificate

GET

/zapier/triggers/new-certificate

Zapier trigger for a newly issued certificate

GET

/ping

Health check

POST

/institution/certificates

Issue a verified certificate

GET

/institution/issued-certificates

List issued certificates

PATCH

/institution/certificates/{id}/revoke

Revoke a certificate by id

GET

/public/verify/{token}

Verify a certificate from its public token

POST

/zapier/actions/issue-certificate

Zapier action to issue a certificate

GET

/zapier/triggers/new-certificate

Zapier trigger for a newly issued certificate

GET

/ping

Health check

Why Jentic?

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

Setup

Wiring the Algeria Certify API by hand means generating a Sanctum token in the Institution Dashboard, sending it as a bearer token on the institution operations, and keeping the public verification path keyless. Through Jentic you install once, import it from the API Directory, store the token once, and your agent issues, lists, and verifies certificates.

Permission scoping

You choose which operations your agent may call, such as issuing and listing certificates, so revoking a certificate is not included unless you add it, and the public verification read needs no key at all. The certificate id travels in the revoke path (/institution/certificates/{id}/revoke), so a rule bounds which operations run.

Credential isolation

Your Algeria Certify Sanctum 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 'issue a verified certificate' or 'verify a certificate token', and Jentic returns the matching Algeria Certify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Algeria Certify API through Jentic.

What authentication does the Algeria Certify API use?

Per its OpenAPI spec the Algeria Certify API uses an HTTP bearer scheme carrying a Sanctum API token, which you generate from the Institution Dashboard under API Keys and send in the Authorization header. The institution issue, list, and revoke operations require this token, while the public certificate verification and the health check need no key.

Can I verify a certificate without an institution key?

Yes. The public verification operation takes a certificate's token and confirms whether it is valid or has been revoked, with no API key required. Issuing and revoking certificates, by contrast, require the institution's bearer token, so only the issuer can change a certificate's state.

What are the rate limits for the Algeria Certify API?

The OpenAPI spec does not publish numeric rate limits for the Algeria Certify API. For current limits check the vendor documentation at https://algeriacertify.com.

How do I issue a certificate with the Algeria Certify API through Jentic?

Import the Algeria Certify API from the Jentic API Directory, then have your agent search by intent such as 'issue a verified certificate' and Jentic returns the issue operation with its input schema. The agent issues the certificate and gets back a public verification token. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Algeria Certify API?

Yes. Write a rule that allows only the issue and list operations, so your agent can create and read certificates but cannot revoke them, and the public verification read needs no key at all. The certificate id appears in the revoke path, so add the revoke operation only when the agent genuinely needs it, and every call it makes is logged.

Is there an Algeria Certify MCP server?

You don't need an MCP server to give your agent the Algeria Certify API. Jentic connects it directly from the API Directory: import it, store your Sanctum token once, and your agent calls the issue, list, revoke, and verify operations on demand without loading another server's tool definitions into its context.

Does the Algeria Certify API work with Zapier, Make, and n8n?

Yes. The API exposes Zapier-shaped triggers for new and revoked certificates and a Zapier action to issue one, plus an auth-test endpoint to validate the key. These let it slot into Zapier, Make, n8n, or any automation tool that speaks those patterns.

Algeria Certify API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthIdentity Verificationbearer9 EndpointsREST

For Agents

Issue, list, verify, and revoke trusted digital certificates for an institution. Public verification needs no key, and built-in Zapier triggers and actions let an agent react to issuance and revocation events.

Use for: Issue a verified certificate for a graduate, List the certificates my institution has issued, Revoke a certificate that was issued in error, Verify a certificate from its public token

Not supported: Does not verify a person's identity, host documents for e-signature, or manage TLS or code-signing certificates. Use for issuing, verifying, and revoking trusted digital certificates only.

The Algeria Certify API issues, verifies, and manages trusted digital certificates for institutions. An institution issues a verified certificate, lists the certificates it has issued, and revokes one by id, while anyone can verify a certificate from its public token without a key. Dedicated Zapier triggers fire when a certificate is issued or revoked, and a Zapier action issues one, so the API drops into Zapier, Make, n8n, or any automation tool. A health check and an API-key validation endpoint round out the integration surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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

36%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

39%

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: DSignals: 4

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

89%

OperationId Quality

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

47%

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: B-Signals: 1

60%

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: A-Signals: 1

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Algeria Certify API to your agent

Capabilities

Start building with Algeria Certify API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Algeria Certify API

Jentic AI Readiness Score

Algeria Certify 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