Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Runo Call Management CRM 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%2Fruno.in%2Fruno" | 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%2Fruno.in%2Fruno" | 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 Runo Call Management CRM API.
Create or update a customer and log an interaction under it with notes, priority, and userFields
Allocate customers to a caller by assignedTo number, a workflow ruleName, or the common pool, singly or in bulk
Remove allocations for a list of user or customer phoneNumbers, or delete a customer by phone number or customerId
Export one past day's customers, CRM interactions, call logs, or WhatsApp interactions, paged by pageNo and filtered by processName
GET STARTED
Send a call recording URL for AI analysis and fetch the call score, summary, and detected keywords by id
List processes and the CRM fields defined for a process, and list or suspend users
Patterns agents use Runo Call Management CRM API for, with concrete tasks.
★ AI agent routing inbound leads to callers
An AI agent watching a web form needs each new lead in Runo and in front of a caller quickly. Through Jentic the agent searches for 'create a customer interaction in Runo', loads the operation with its input schema, and calls it with the Auth-Key header injected at execution time. It then creates an allocation that assigns the customer to a caller by phone number, or to the common pool when no caller is chosen.
Call POST /crm/interaction with the customer object, processName Sales, and notes, then POST /crm/allocation with the same customer and assignedTo set to the caller's phone number
Daily call activity export to a warehouse
A reporting job copies the previous day's calling activity into a data warehouse. GET /call/logs, GET /crm/interactions, and GET /crm/whatsapp each take a past date in YYYY-MM-DD format, an optional processName, and a required pageNo, and return up to 100 records per page. Setting isLatestOnly on call logs or interactions returns only the latest entry per customer for that day.
Page GET /call/logs with yesterday's date and pageNo starting at 1 until a page returns fewer than 100 records, and load every record into the warehouse
AI call quality review
A sales manager reviewing call quality sends recordings for scoring instead of listening to each one. POST /call/analysis/initiate takes a signed recordingUrl and a callType of incoming or outgoing and returns an id. GET /call/analysis/result/{id} reports progress and, once status reads 0, the call score, summary, speaker sentiment, talk-time split, compliance checks, and keywords; the spec notes credits are charged per minute of recording.
Send POST /call/analysis/initiate with a signed recordingUrl and callType outgoing, then poll GET /call/analysis/result/{id} until status is 0 and return the score and summary
Bulk allocation for a calling campaign
A campaign manager loading a list of customers for outbound calls needs them spread across the team. POST /crm/allocations accepts a processName and an allocations array, assigns them through the common pool, a workflow rule, or an assignedTo number, and can update or override existing customer data. The results query parameter controls whether the response returns only counts, failures, or every outcome.
Call POST /crm/allocations with processName Renewals, isCommonPool true, the customer allocations array, and results set to failed, then report any failed rows
20 endpoints — the runo call management crm api connects to runo, a crm for teams that work customers by phone, and moves customer records and call activity in and out of it.
METHOD
PATH
DESCRIPTION
/crm/interaction
Create a customer interaction
/crm/allocation
Allocate a customer to a caller
/crm/allocations
Create multiple allocations
/call/logs
List call logs for a past date
/crm/interactions
List CRM interactions for a past date
/customer/list
List customers for a past date
/call/analysis/initiate
Send a call recording for AI analysis
/call/analysis/result/{id}
Get the call analysis result
/crm/interaction
Create a customer interaction
/crm/allocation
Allocate a customer to a caller
/crm/allocations
Create multiple allocations
/call/logs
List call logs for a past date
/crm/interactions
List CRM interactions for a past date
/customer/list
List customers for a past date
/call/analysis/initiate
Send a call recording for AI analysis
/call/analysis/result/{id}
Get the call analysis result
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Runo by hand means sending the Auth-Key header on every call, paging daily exports with pageNo, remembering that exports only accept past dates, and polling call analysis status codes. Through Jentic you install once, import Runo from the API Directory, store the key once, and your agent calls it.
Permission scoping
Runo carries the process name and customer details in query strings and request bodies, so rules bound which operations your agent may call, not which process or customer. You choose the operations it may call, so destructive ones like deleting a customer or suspending a user are not included unless you add them.
Credential isolation
Your Runo Auth-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 'export yesterday's call logs' or 'allocate a customer to a caller', and Jentic returns the matching Runo operation with its input schema, including required fields like pageNo or assignedTo, so the agent calls it correctly.
Alternatives and complements available in the Jentic catalogue.
Specific to using Runo Call Management CRM API through Jentic.
What authentication does the Runo Call Management CRM API use?
Per its OpenAPI spec, the Runo API uses an API key sent in the `Auth-Key` request header on every operation. You generate the key in the Runo Admin Web Application. Through Jentic the key is held by your own Jentic One instance and attached at call time, so the agent never sees it.
Can I export today's call logs with the Runo API?
No. GET /call/logs and the other daily exports accept only past dates in YYYY-MM-DD format, so the most recent full day you can pull is yesterday. Each call needs a pageNo and returns up to 100 records, and processName narrows the export to one calling process.
What are the rate limits for the Runo Call Management CRM API?
The OpenAPI spec does not specify rate limits; it only caps the daily export routes at 100 records per page. Check the Runo API documentation at https://docs.runo.in for current limits.
Is there a Runo MCP server?
You do not need an MCP server to give your agent Runo. Jentic connects it directly from the API Directory: import it, store your Auth-Key once, and your agent calls the customer, allocation, call log, and analysis operations on demand without extra tool definitions in its context.
How do I add a lead and assign it to a caller through Jentic?
Search Jentic for 'create a customer interaction in Runo', execute POST /crm/interaction with the customer object and processName, then search for 'allocate a customer to a caller' and execute POST /crm/allocation with the customer and the caller's number as assignedTo. 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 Runo API?
Yes. For a reporting agent, write a rule that allows only the daily export reads such as GET /call/logs and GET /crm/interactions, so it can pull activity but cannot delete customers, remove allocations, or suspend users. Add the allocation routes when it should also assign leads, and every call it makes is logged.
For Agents
Push customers and interactions into Runo, allocate them to callers, export daily call logs and CRM activity by process, and run AI analysis on call recordings.
Use for: Add a new lead to the sales process and assign it to a caller, Get yesterday's call logs for the collections process, List all CRM interactions from last Monday, I want to analyse a recorded sales call
Not supported: Does not place phone calls, send WhatsApp messages, or manage deal pipelines. Use for syncing Runo customers, allocations, call activity, and call analysis only.
The Runo Call Management CRM API connects to Runo, a CRM for teams that work customers by phone, and moves customer records and call activity in and out of it. It creates customers with an interaction in one call, allocates customers to individual callers or a common pool, and removes allocations or customers by phone number or id. Daily, paginated exports cover customers, CRM interactions, call logs, WhatsApp interactions, and user login logs, filtered by date and processName. Call recordings can be sent for AI analysis and the scored result fetched once it completes.
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>