Install Jentic One Beta

Connect the Dialb API to your agent

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

Add new contacts and keep their details up to date

Find a contact by email or list the most recent contacts

Tag a contact to group or segment it

Create short links and look them up by search

Subscribe to webhook events and unsubscribe when done

GET STARTED

Start building with Dialb API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dialb API for, with concrete tasks.

★ Contact Capture Agent

An AI agent captures a new lead into Dialb: it searches by email to avoid duplicates, creates the contact if none exists, updates details, and tags it for the right segment. The agent discovers the search, create, update, and tag operations through Jentic by intent, so it captures contacts without hardcoding endpoint paths.

Search Dialb for a contact by email, create it if missing, update its details, and tag it for a segment

Short Link Automation

A team wants trackable short links generated on demand. The agent creates a short link for a destination and can look up existing links by search, so campaigns reuse links rather than duplicate them. Dialb also records QR scans, which the agent lists to gauge engagement.

Create a short link for a destination URL, then list recent QR scans to report engagement

Webhook-Driven Sync

An integration keeps Dialb in sync with another system. The agent subscribes to the relevant webhook event, processes notifications as they arrive, and unsubscribes when the integration is torn down. Because Dialb powers a Zapier integration, the same webhook events drive both custom and no-code automations.

Subscribe to a Dialb webhook event, then unsubscribe it by id when the integration is removed

Key Endpoints

14 endpoints — the dialb api manages contacts, short links, digital cards, and webhooks for the dialb platform and its zapier integration.

METHOD

PATH

DESCRIPTION

GET

/contacts/recent

List recent contacts

GET

/contacts/search

Find a contact by email

POST

/contacts

Create a contact

PUT

/contacts/{id}

Update a contact

POST

/contacts/{id}/tags

Tag a contact

POST

/short-links

Create a short link

POST

/webhooks/subscribe

Subscribe to a webhook event

GET

/qr-scans/recent

List recent QR scans

GET

/contacts/recent

List recent contacts

GET

/contacts/search

Find a contact by email

POST

/contacts

Create a contact

PUT

/contacts/{id}

Update a contact

POST

/contacts/{id}/tags

Tag a contact

POST

/short-links

Create a short link

POST

/webhooks/subscribe

Subscribe to a webhook event

GET

/qr-scans/recent

List recent QR scans

Why Jentic?

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

Setup

Wiring Dialb by hand means issuing an API key, sending it in the X-API-Key header, and managing the webhook subscriptions that drive its Zapier integration yourself. Through Jentic you install once, import Dialb from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which Dialb operations your agent may call, so you can allow contact lookups and creation while leaving updates, tagging, and webhook subscriptions out unless you add them. Dialb carries the contact id in the URL path, so rules bound which operations run.

Credential isolation

Your Dialb 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 find a contact by email or create a short link, and Jentic returns the matching Dialb operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Dialb API through Jentic.

What authentication does the Dialb API use?

The Dialb API authenticates with an API key sent in the X-API-Key request header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's prompt or logs.

Can I manage contacts with the Dialb API?

Yes. You can create a contact, update it, find it by email, list the most recent contacts, and tag it. Combine search with create so your agent avoids making duplicate records.

What are the rate limits for the Dialb API?

The OpenAPI spec does not publish rate limits for the Dialb API. Check Dialb's own API documentation for the current per-key limits before running frequent recent-activity polls.

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

Yes. Write a rule that allows only contact lookups and creation, so the agent can capture leads while contact updates, tagging, and webhook subscriptions stay out unless you add them. Every call the agent makes is logged.

How do I add a contact with the Dialb API through Jentic?

Search Jentic for an intent like create a contact, store your Dialb key once, and your agent calls the search operation to check for duplicates and then the create operation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Dialb MCP server?

You don't need an MCP server to give your agent the Dialb API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the operations it needs on demand.

Dialb API

AI ReadinessFoundational (D)43/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey14 EndpointsREST

For Agents

Create, update, find, and tag contacts through Dialb, and create short links. Subscribe to webhook events, list recent activity, and look up digital cards by slug.

Use for: Create a new contact, Find a contact by email, Update a contact's details, Tag a contact

Not supported: Does not handle email sending, deal pipelines, or payment processing. Use for managing contacts, short links, cards, and webhooks only.

The Dialb API manages contacts, short links, digital cards, and webhooks for the Dialb platform and its Zapier integration. Agents create and update contacts, find them by email, and tag them, while short-link operations create and look up links and webhook operations subscribe to or cancel event notifications. Recent-activity endpoints list the latest contacts, short links, cards, and QR scans.

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

34%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

30%

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

24%

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

50%

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 Dialb API to your agent

Capabilities

Start building with Dialb API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dialb API

Jentic AI Readiness Score

Dialb 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