For Agents
Place outbound AI-agent voice calls with a configured script, voice, and contact list through a single Dialgood endpoint.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dialgood 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%2Fdialgood.com%2Fdialgood" | 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%2Fdialgood.com%2Fdialgood" | 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 Dialgood API.
Place outbound AI-driven voice calls to a list of contacts
Configure the voice agent's script, persona, and speech settings per call
Submit batches of contacts to be dialed sequentially or in parallel
GET STARTED
Use for: I need to place an outbound AI voice call, Run a calling campaign across a list of contacts, Send appointment reminder calls for tomorrow's bookings, Qualify a list of leads with an AI voice agent
Not supported: Does not handle inbound call routing, SMS messaging, or contact-centre staffing - use for outbound AI voice calls only.
The Dialgood API places outbound voice calls staffed by AI agents that follow a configurable script and speech profile. A single POST /external/v1/outbound endpoint accepts the contact list, agent settings, and speech parameters, then dispatches the calls and reports outcomes back. It is built for sales outreach, lead qualification, appointment reminders, and survey workflows that need an AI voice agent rather than a human dialer.
Receive call outcomes and disposition codes after the call completes
Customise speech parameters such as voice ID, language, and pacing
Patterns agents use Dialgood API for, with concrete tasks.
★ Sales Outreach Campaigns
Run AI-voiced outbound sales campaigns across a list of prospects without staffing human SDRs. POST /external/v1/outbound accepts the contact list and agent configuration, then Dialgood places the calls, runs the configured script, and returns disposition data per contact. Suitable for top-of-funnel qualification at volume.
Submit 500 contacts with a discovery-call script and a friendly voice agent persona, then collect disposition codes when the campaign completes
Appointment Reminder Calls
Reduce no-shows by placing reminder calls 24 hours before appointments. The endpoint handles dialing, the AI agent confirms or reschedules, and a webhook or response payload reports whether the customer confirmed. Useful for clinics, salons, and service businesses with high-cost no-shows.
For each appointment scheduled tomorrow, place a reminder call with a confirmation script and capture whether the customer confirmed, rescheduled, or did not answer
Lead Qualification at Scale
Push freshly captured leads to Dialgood for an AI-voiced qualification call before routing the warm ones to a human rep. The AI agent runs a structured discovery script, scores the lead based on responses, and surfaces the qualification outcome to the CRM. This collapses the lead-to-meeting funnel into hours rather than days.
On each new MQL, place a Dialgood call with the qualification script and post the resulting score and notes back to the CRM contact record
AI Agent Voice Channel
Give an AI agent a voice channel for follow-ups by calling Dialgood through Jentic. The agent searches for the outbound-call operation, loads the input schema (contact, script, voice settings), and executes - the AI on the other end of the line is a separate Dialgood agent the orchestrator dispatches.
When a high-priority lead does not respond to email, place a Dialgood follow-up call with the configured persona and capture the disposition for the CRM timeline
1 endpoints — the dialgood api places outbound voice calls staffed by ai agents that follow a configurable script and speech profile.
METHOD
PATH
DESCRIPTION
/external/v1/outbound
Place an outbound AI voice call with the configured script and contact list
/external/v1/outbound
Place an outbound AI voice call with the configured script and contact list
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Dialgood API by hand means setting the API-key header and building the outbound call payload against the single outbound endpoint yourself. Through Jentic you install once, import the Dialgood API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The API exposes a single outbound voice-call operation, so the agent can only place outbound calls and nothing else, and you decide whether to give it that one operation. It cannot route inbound calls or send SMS.
Credential isolation
Your Dialgood API 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 'place an AI voice call', and Jentic returns the Dialgood outbound 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 Dialgood API through Jentic.
What authentication does the Dialgood API use?
Dialgood uses an API key passed in a request header. Through Jentic the key is stored encrypted in the vault and injected at execution time, so it never enters the agent's prompt context.
Can I customise the AI agent's voice and script per call?
Yes. The POST /external/v1/outbound body accepts script, persona, voice ID, language, and pacing fields, so each campaign can run a different agent configuration without touching the Dialgood dashboard.
What are the rate limits for the Dialgood API?
Dialgood applies per-account concurrency limits negotiated at signup rather than a request-per-second cap. High-volume customers should confirm their concurrent-call ceiling with Dialgood before launching a campaign.
How do I place a call through Jentic?
Run a Jentic search for "place an outbound AI call". Jentic returns the Dialgood outbound-call operation with its input schema, and the agent loads the schema, populates contact and script fields, and executes - no need to fetch the Dialgood spec separately.
Does the API support batch contact lists?
Yes. The outbound endpoint accepts an array of contacts in a single request, so a campaign of dozens or hundreds of calls can be queued with one call to the API.
How do I install the Jentic SDK to call Dialgood?
Run pip install jentic, set JENTIC_AGENT_API_KEY to your ak_* key, then use Jentic with SearchRequest, LoadRequest, and ExecutionRequest. Get started with Jentic One, the self-hosted execution layer.
Can I limit what my agent is allowed to do with the Dialgood API?
Yes. Because Jentic One is self-hosted, your own rules decide which Dialgood operations and credentials the agent can use. The Dialgood API exposes only a single outbound voice-call operation (POST /external/v1/outbound), so you can grant the agent that one operation and nothing more. It cannot route inbound calls or send SMS, and your stored API key is injected only at execution time rather than exposed to the agent.