Install Jentic One Beta

Connect the CardClan Integration API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CardClan Integration 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%2Fcardclan.io%2Fcardclan" | 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%2Fcardclan.io%2Fcardclan" | 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 CardClan Integration API.

Send a personalized digital card to a recipient through a connected email account

Generate a shareable URL for a card

List the cards and workspaces available to a user

Read the details of a specific card by its id

Create and read integration configurations that drive card workflows

GET STARTED

Start building with CardClan Integration API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CardClan Integration API for, with concrete tasks.

★ Agent-sent personalized cards

An AI agent handling customer touchpoints can send a personalized digital card at the right moment, choosing a card from the user's workspace and sending it through a connected email account. Because the CardClan Integration API also returns a shareable card URL, the agent can include the link in a follow-up message rather than only emailing it.

Send a personalized card from a workspace to a recipient through a connected email account and confirm it was sent

Milestone and engagement automation

Teams that send cards on customer milestones can wire the trigger to CardClan so a card goes out automatically. The API lists workspace cards, sends the chosen card through an email account, and reads which cards already have workflows attached, so an automation sends the right card without manual steps.

List the cards that have workflows attached, then send the matching card for a customer milestone

Card workflow configuration

Before automating sends, an integrator sets up how cards map to a workflow. The CardClan Integration API creates and reads integration configurations, including the configuration tied to a specific card, so the setup is defined once and then reused by every send. An integration key authenticates the automation.

Generate an integration key, then create an integration configuration that maps a card to a workflow

Key Endpoints

12 endpoints — the cardclan integration api lets applications and automation platforms send personalized digital cards and drive card workflows from existing systems.

METHOD

PATH

DESCRIPTION

POST

/integration/send-card

Send a personalized card through a connected email account

POST

/integration/get-card-url

Get a shareable URL for a card

POST

/integration/cards

List the cards available to a user

GET

/integration/workspaces

List a user's workspaces

GET

/integration/email-accounts

List the connected email accounts

GET

/integration/card-details/{cardId}

Read the details of a specific card

POST

/integration/auth/create-key

Generate an integration key

POST

/integration/send-card

Send a personalized card through a connected email account

POST

/integration/get-card-url

Get a shareable URL for a card

POST

/integration/cards

List the cards available to a user

GET

/integration/workspaces

List a user's workspaces

GET

/integration/email-accounts

List the connected email accounts

GET

/integration/card-details/{cardId}

Read the details of a specific card

POST

/integration/auth/create-key

Generate an integration key

Why Jentic?

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

Setup

Wiring the CardClan Integration API by hand means handling its bearer-token auth, generating an integration key from a Firebase token, and connecting an email account before you can send anything. Through Jentic you install once, import CardClan from the API Directory, store the key once, and your agent calls it.

Permission scoping

The card and recipient travel in the request body, not the URL path, so a rule bounds which operations your agent may call rather than which card it sends. You choose the operations it may call, such as sending cards and listing workspaces, so integration key generation or config changes are not included unless you add them.

Credential isolation

Your CardClan integration key 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 digital card' or 'generate a card link', and Jentic returns the matching CardClan operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using CardClan Integration API through Jentic.

What authentication does the CardClan Integration API use?

The CardClan Integration API authenticates with a bearer token: your CardClan integration key for integration calls, and a Firebase ID token sent as a bearer token to generate a key, as declared in its OpenAPI spec. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.

Can I get a shareable link for a card with the CardClan Integration API?

Yes. Alongside sending a card through a connected email account, the API returns a shareable card URL, so an agent can include the link in a chat message or other channel instead of only sending the card by email.

What are the rate limits for the CardClan Integration API?

The OpenAPI spec does not state numeric rate limits for the CardClan Integration API. Check the vendor documentation at https://docs.cardclan.io for current limits before sending cards at volume.

How do I send a card through Jentic with the CardClan Integration API?

Search Jentic for 'send a digital card', which returns the POST /integration/send-card operation with its input schema, then call it with the card and recipient. 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 CardClan Integration API?

Yes. Write a rule that allows only the send-card and list operations, so the agent can send cards and read workspaces but cannot generate integration keys or change configurations, and every call it makes is logged. The card and recipient travel in the request body, so the rule bounds which operations run rather than which card is sent.

CardClan Integration API

AI ReadinessFoundational (D)45/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer12 EndpointsREST

For Agents

Send personalized digital cards through a connected email account, generate shareable card links, and read cards, workspaces, and card details. Integration configurations drive automated card workflows.

Use for: Send a thank-you card to a customer, Generate a shareable link for a card, List the cards in my workspace, Get the details of a specific card

Not supported: Does not handle SMS, physical mail, or payment processing. Use for sending digital cards and managing card workflows only.

The CardClan Integration API lets applications and automation platforms send personalized digital cards and drive card workflows from existing systems. It sends cards through a connected email account, generates shareable card URLs, lists the cards and workspaces available to a user, and reads the details of a specific card. Integration configurations tie cards into automated workflows, and an integration key authenticates each request.

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

98%

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

39%

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

26%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

50%

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: ASignals: 1

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CardClan Integration API to your agent

Capabilities

Start building with CardClan Integration API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CardClan Integration API

Jentic AI Readiness Score

CardClan Integration 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