Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CRM Smart 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%2Fgestorasmart.com.br%2Fgestorasmart" | 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%2Fgestorasmart.com.br%2Fgestorasmart" | 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 CRM Smart API.
Create and update client records and import clients in bulk
Open contracts for a client and move them through status changes
Place orders and link SIM cards and IMEIs from stock to an order
Track SIM card and IMEI stock by operator and by model
Register sellers and the referrers that bring in clients
GET STARTED
Record client addresses and contract representatives
Patterns agents use CRM Smart API for, with concrete tasks.
★ Agent-Managed Sales Intake
An AI agent connected through Jentic creates a client, opens a contract for them, and places the first order in one flow, so a new sale is captured without a back-office operator keying it in. Because the agent works against the same client, contract, and order records the CRM Smart app uses, the sale is visible to the team at once.
Create a client, open a contract for them, and place an order, returning the new order id
Order Fulfilment with SIM and IMEI Stock
A fulfilment workflow places an order and then links the SIM cards and IMEIs it needs from inventory, drawing on the stock-by-operator and stock-by-model counts to pick available devices. This keeps the order and the devices assigned to it in one system rather than a separate inventory tool.
Place an order, then link the required SIM cards and IMEIs from stock to that order
Bulk Client Import
A migration or onboarding job imports a batch of clients in one call rather than creating them one at a time, so moving an existing book of business into CRM Smart is a single step. The imported clients then carry the contracts and orders created against them.
Import this batch of client records in a single bulk call and report how many were created
88 endpoints — the crm smart api runs the sales back office for a telecom reseller, centred on client records and the contracts, orders, and stock that hang off them.
METHOD
PATH
DESCRIPTION
/cliente
List clients
/cliente
Create a client
/cliente/importar-massa
Import clients in bulk
/contratos/list
List contracts
/contratos
Create a contract
/pedidos
Create an order
/simcards/vincular-simcards-pedido/{pedidoId}
Link SIM cards to an order
/produtos
List products
/cliente
List clients
/cliente
Create a client
/cliente/importar-massa
Import clients in bulk
/contratos/list
List contracts
/contratos
Create a contract
/pedidos
Create an order
/simcards/vincular-simcards-pedido/{pedidoId}
Link SIM cards to an order
/produtos
List products
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the CRM Smart API by hand means logging in to obtain a JSON Web Token, carrying it in a cookie on each call, and sequencing clients, contracts, orders, and device stock yourself. Through Jentic you install once, import CRM Smart from the API Directory, store the credential once, and your agent calls it.
Permission scoping
You choose which operations your agent may call, so you can allow listing and creating clients, contracts, and orders while leaving stock edits and deletions out. The record ids travel in the URL path or body, so your rules bound which operations run, and destructive ones like deleting a client or a contract are not included unless you add them.
Credential isolation
Your CRM Smart token 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 'create a client and open a contract' or 'link SIM cards to an order', and Jentic returns the matching CRM Smart operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using CRM Smart API through Jentic.
Is there a CRM Smart MCP server?
You don't need an MCP server to give your agent the CRM Smart API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can create clients, open contracts, and place orders straight away, with no extra server to run and no tool definitions to load into the agent's context.
Can I limit what my agent is allowed to do with the CRM Smart API?
Yes. Write a rule that allows only the operations the agent needs, such as listing and creating clients and orders, so it can handle sales intake without deleting contracts or editing stock. Destructive operations like deleting a client or a contract are not included unless you add them, and every call the agent makes is logged.
What authentication does the CRM Smart API use?
The CRM Smart API authenticates with a JSON Web Token held in an httpOnly cookie named `token`, which you obtain by logging in, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.
Can I import clients in bulk with the CRM Smart API?
Yes. There is a bulk client import operation that creates a batch of clients in a single call, which is how you migrate an existing customer list rather than creating each client one at a time. The imported clients then carry the contracts and orders you create against them.
Can I link SIM cards and IMEIs to an order with the CRM Smart API?
Yes. After placing an order you call the operations that link SIM cards and IMEIs from stock to that order, and you can look up stock quantities by operator and by model to pick available devices. This keeps the order and its assigned devices in one system.
How do I capture a sale through Jentic?
Import the CRM Smart API from the Jentic API Directory, then have your agent issue a request such as 'create a client, open a contract, and place an order'. Jentic matches the intent to the create-client, create-contract, and create-order operations and returns their input schema so the agent fills the right fields, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Manage clients, contracts, and orders in the CRM Smart sales system, and link SIM cards and IMEIs from stock to an order. Authenticates with a JWT held in a cookie.
Use for: Create a new client and import a batch of clients, Open a contract for a client and update its status, Place an order and link SIM cards to it, List all orders tied to a referrer
Not supported: Does not process payments, run marketing campaigns, or provision telecom network service. Use for managing clients, contracts, orders, and device stock in CRM Smart only.
The CRM Smart API runs the sales back office for a telecom reseller, centred on client records and the contracts, orders, and stock that hang off them. Clients can be created, updated, and imported in bulk, contracts move through status changes, and orders are placed and then fulfilled by linking SIM cards and IMEIs from inventory. It also tracks sellers and their referrers, client addresses, and product and device stock, with per-referrer listings of the clients, contracts, and orders tied to each.
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>