Install Jentic One Beta

Connect the Canarics API to your agent

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

Read minutes used versus plan for the current billing cycle

List the team's AI voice agents and their dashboard links

Read call logs, conversations, and per-day call statistics

Look up the cross-call history for a single phone number

Schedule an AI voice-agent callback to a phone number

GET STARTED

Start building with Canarics API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Canarics API for, with concrete tasks.

★ Agent-checked account status

An AI assistant can check a Canarics team's minute usage against its plan, list the voice agents, and read recent call statistics in one session, so the person asking gets an account summary without opening the dashboard. Reads are gated by the key's scope.

Read the minutes used versus plan this cycle and list the team's AI voice agents

Scheduled voice callbacks

A support agent can look up the cross-call history for a phone number, then schedule a voice-agent callback to that number with a reason, so a follow-up call is placed without a human dialling. Scheduling a callback requires the callbacks scope on the key.

Look up the call history for +15551234567, then schedule a voice-agent callback with a reason

Outbound campaign drafting

A growth agent can draft an outbound calling campaign from a brief and define a custom mid-call tool the voice agent can use, then dry-run the tool through the live-call executor before anything goes out. Drafting a campaign never places calls on its own.

Draft an outbound calling campaign from a brief and create a custom mid-call tool, then dry-run the tool

Key Endpoints

21 endpoints — the canarics api lets an ai assistant check a team's canarics account for ai voice agents: minutes used versus plan, the voice agents themselves, call history, conversations, and per-day call statistics.

METHOD

PATH

DESCRIPTION

GET

/api/v1/usage

Minutes used versus plan this cycle

GET

/api/v1/agents

List the team's AI voice agents

GET

/api/v1/calls

Read call log summaries

GET

/api/v1/contacts/{number}

Cross-call history for one number

POST

/api/v1/callbacks

Schedule a voice-agent callback

POST

/api/v1/campaigns

Draft an outbound calling campaign

GET

/api/v1/usage

Minutes used versus plan this cycle

GET

/api/v1/agents

List the team's AI voice agents

GET

/api/v1/calls

Read call log summaries

GET

/api/v1/contacts/{number}

Cross-call history for one number

POST

/api/v1/callbacks

Schedule a voice-agent callback

POST

/api/v1/campaigns

Draft an outbound calling campaign

Why Jentic?

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

Setup

Wiring Canarics by hand means handling two auth schemes, a bearer token or an x-api-key header, and the per-scope gating that governs callbacks, campaigns, and tools. Through Jentic you install once, import Canarics from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which Canarics operations the agent may call, such as usage and call-log reads, so operations that schedule a callback or draft a campaign are not included unless you add them.

Credential isolation

Your Canarics 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 'check voice minutes used this cycle', and Jentic returns the matching Canarics operation with its input schema so the agent calls the right endpoint without browsing the docs.

FAQs

Specific to using Canarics API through Jentic.

What authentication does the Canarics API use?

The Canarics API authenticates with a bearer token or an x-api-key header, per its OpenAPI spec. The discovery and signup endpoints need no credential, and individual operations are further gated by scopes on the key.

Is there a Canarics MCP server?

Canarics runs a remote MCP server, exposed as a streamable HTTP endpoint. You can also connect Canarics directly through Jentic: your agent gets the account, call, and campaign operations from the spec without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call.

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

Yes. Write a rule that allows only the usage and call-log read operations, so the agent can report account status but cannot schedule a callback or draft a campaign until you add those operations, and every call it makes is logged.

Can I schedule a voice-agent callback with the Canarics API?

Yes. The callbacks endpoint schedules an AI voice-agent callback to a number with a reason, provided the key carries the callbacks scope, so an agent can arrange a follow-up call.

What are the rate limits for the Canarics API?

The OpenAPI spec does not publish a numeric rate limit. Daily call statistics are capped at a 90-day window, and voice usage is bounded by the minutes your plan includes, which the usage endpoint reports.

How do I check voice minutes with the Canarics API through Jentic?

Search Jentic for 'check voice minutes used this cycle', and it returns the Canarics usage operation with its input schema. Read minutes used versus plan, then list the voice agents or call history as needed. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Canarics API

AI ReadinessFoundational (D)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsVoice Telephonybearer, apiKey21 EndpointsREST

For Agents

Read minutes used, list AI voice agents, read call history and statistics, schedule callbacks, and draft outbound calling campaigns for a team.

Use for: Check how many voice minutes my team has used this cycle, List the AI voice agents on my team, Read the recent call log for my account, Look up the call history for a specific phone number

Not supported: Does not handle SMS, email, or payment processing beyond returning a hosted checkout link. Use for AI voice-agent account data, call history, and callbacks only.

The Canarics API lets an AI assistant check a team's Canarics account for AI voice agents: minutes used versus plan, the voice agents themselves, call history, conversations, and per-day call statistics. It can schedule a voice-agent callback, draft outbound calling campaigns, and define custom mid-call tools, each gated by a scope on the key. A no-auth signup flow can set up a new team and hand back a one-time key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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).

35%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

45%

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

36%

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.

53%

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

55%

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

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Canarics API to your agent

Capabilities

Start building with Canarics API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Canarics API

Jentic AI Readiness Score

Canarics API for AI agents

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