Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CosVoice 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%2Fcosvoice.com%2Fcosvoice" | 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%2Fcosvoice.com%2Fcosvoice" | 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 CosVoice API.
Place a phone call on the owner's behalf and read its outcome, notes, and transcript
Send and read text messages from the line's own number
Book a restaurant table by phone and list the tables the line has booked
Read mail that reached the line and forward a message on to an inbox
Keep a contact list with per-number standing instructions and forget a number
GET STARTED
Configure the line's name, voice, greeting, and standing instructions
Catch up on calls, texts, and mail since a timestamp or read the full history
Patterns agents use CosVoice API for, with concrete tasks.
★ Agent-Placed Phone Calls
An agent asks the CosVoice line to call someone in plain English, the line holds the conversation, and the agent reads back the outcome, notes, and transcript once the call completes. Calls run for a few minutes, so the agent either polls the call or waits for the completion webhook before acting on what was said.
Place a call with POST /calls, then poll GET /calls/{id} until the outcome, notes, and transcript are ready
Restaurant and Contact Handling
An agent books a restaurant table by phone through the line and manages a contact list that tells the line how to treat each number. CosVoice records the booked reservations and lets the agent add or forget contacts, so repeat interactions follow the standing instructions set for that caller.
Book a table with POST /reservations, then add the caller with POST /contacts and standing instructions
AI Agent Integration via Jentic
An AI agent reaches CosVoice through Jentic without handling the bearer key itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time. This lets an agent place a call or send a text as one step in a larger task without wiring the line's auth in code.
Search Jentic for 'place a phone call', load the POST /calls schema, and execute it with Jentic-managed credentials
20 endpoints — the cosvoice api gives an ai assistant its own phone line, a single number and email address, that it can use to place calls, send texts, and handle mail on the owner's behalf.
METHOD
PATH
DESCRIPTION
/calls
Call someone on the owner's behalf
/calls/{id}
Read a call's outcome, notes, and transcript
/messages
Send a text from the line's number
/reservations
Book a table by phone
/emails/{id}/forward
Forward a message on to an inbox
/activity
Calls, texts, and mail since a timestamp
/settings
Change the line's name, voice, greeting, or instructions
/calls
Call someone on the owner's behalf
/calls/{id}
Read a call's outcome, notes, and transcript
/messages
Send a text from the line's number
/reservations
Book a table by phone
/emails/{id}/forward
Forward a message on to an inbox
/activity
Calls, texts, and mail since a timestamp
/settings
Change the line's name, voice, greeting, or instructions
What agents get from Jentic-routed access to this vendor.
Setup
Wiring CosVoice by hand means managing the line's bearer key, placing calls that run asynchronously over minutes, and polling each call or handling its completion webhook yourself. Through Jentic you install once, import CosVoice from the API Directory, store the key once, and your agent calls it.
Permission scoping
CosVoice carries the recipient inside the request body, so rules bound which operations your agent may call, not which number it can reach. You choose the operations it may call, so placing calls and reading transcripts can be allowed while contact deletion and settings changes are not included unless you add them.
Credential isolation
Your CosVoice 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 a phone call' or 'send a text', and Jentic returns the matching CosVoice 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 CosVoice API through Jentic.
What authentication does the CosVoice API use?
The CosVoice API authenticates with a bearer API key in the Authorization header, per its OpenAPI spec, where the key belongs to a specific line. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I place a phone call with the CosVoice API?
Yes. You call the place-a-call operation with the request described in plain English, the line holds the conversation, and you read the outcome, notes, and transcript from the call once it completes. Calls take minutes, so an agent polls the call or waits for the call-completed webhook before acting.
What are the rate limits for the CosVoice API?
The OpenAPI spec documents a rate limit of 240 requests a minute per key. Because calls run asynchronously over minutes, an agent typically places a call and then polls its status rather than making a burst of requests, which keeps it well within that limit.
Is there a CosVoice MCP server?
You don't need an MCP server to give your agent CosVoice. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the call, message, and reservation operations. Nothing extra is loaded into the agent's context until an operation is actually invoked.
Can I limit what my agent is allowed to do with the CosVoice API?
Yes. CosVoice carries the recipient inside the request body, so rules bound which operations your agent may call rather than which number it can reach. Allow only the operations it needs, such as placing calls and reading their transcripts, and the line's settings and contact-deletion operations stay out of reach, with every call logged by your own Jentic One instance.
How do I place a call with the CosVoice API through Jentic?
Search Jentic for 'place a phone call', and it returns the CosVoice call operation with its input schema. Load the schema and execute POST /calls with the request, then read the result from GET /calls/{id}, with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Place phone calls, send and read texts, handle email, and book tables through an AI phone line, then read each call's outcome, notes, and transcript. Authenticated with a bearer API key.
Use for: Place a phone call on the owner's behalf, Check how a call went and read its transcript, Send a text from the line's number, Book a restaurant table by phone
Not supported: Does not handle payment processing, CRM pipelines, or video conferencing. Use for an AI phone line's calls, texts, emails, and reservations only.
The CosVoice API gives an AI assistant its own phone line, a single number and email address, that it can use to place calls, send texts, and handle mail on the owner's behalf. You ask it to call someone in plain English, it holds the conversation, and it writes up the outcome, notes, and transcript that you read back after the call completes. Around the line it books restaurant tables by phone, keeps a contact list with standing instructions per number, and streams activity and full history so an agent can catch up on what happened.
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>