Install Jentic One Beta

Connect the Claro CPQ Quotes API to your agent

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

Retrieve all quotes linked to a specific customer or sales opportunity

Fetch a single previously created quote that was offered to a customer

Partially update a quote while its status still permits modification

Advance a quote through its lifecycle by changing its status

Work against a stable CPQ quote contract proxied through Claro's Apigee gateway

GET STARTED

Start building with Claro CPQ Quotes API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Claro CPQ Quotes API for, with concrete tasks.

★ Agent-assisted quote lookup and update

An AI agent handling a sales enquiry can call the Claro CPQ Quotes API through Jentic to pull every quote attached to a customer, retrieve the specific quote under discussion, and patch it when the customer requests a change. Jentic returns the right operation from a natural-language query, so the agent works against the CPQ quote contract without parsing the Apigee proxy documentation.

Retrieve all quotes for the given customer, select the one matching the opportunity, and patch its editable fields with the customer's requested change.

Quote status progression

Advance a telecom sales quote through its lifecycle by changing its status from initial to feasibility pending to feasibility concluded as the deal moves forward. The status operation enforces which transitions are allowed, so a workflow tool can drive the quote forward without manually editing backend records.

Change the status of the named quote from its initial state to feasibility pending, then confirm the transition was accepted.

Opportunity-to-quote reconciliation

List every quote linked to a sales opportunity to reconcile what has been offered against what is in the pipeline. The retrieve operation returns the detail of any single quote, so a commercial team can audit outstanding offers tied to one opportunity in a single pass.

List the quotes for the given opportunity, then retrieve the detail of each one and report which quotes are still editable.

Key Endpoints

4 endpoints — the claro cpq quotes api retrieves and updates sales quotes tied to a customer or an opportunity inside claro brazil's configure, price, quote system.

METHOD

PATH

DESCRIPTION

GET

/cpq/quotes

Retrieve all quotes for a customer or opportunity

PATCH

/cpq/quotes

Partially update a previously created quote

GET

/cpq/quotes/retrieve

Retrieve a single previously created quote

PATCH

/cpq/quotes/states

Change the status of a quote

GET

/cpq/quotes

Retrieve all quotes for a customer or opportunity

PATCH

/cpq/quotes

Partially update a previously created quote

GET

/cpq/quotes/retrieve

Retrieve a single previously created quote

PATCH

/cpq/quotes/states

Change the status of a quote

Why Jentic?

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

Setup

Wiring the Claro CPQ Quotes API by hand means picking among its basic, bearer, apiKey, and OAuth2 schemes, targeting the right Apigee host for your environment, and coding each quote call yourself. Through Jentic you install once, import the API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The quote identifier travels in the request body and query, not as an id in the URL path, so bound your agent to the operations it needs, such as listing and retrieving quotes. You choose which operations it may call, so the update and status operations are not included unless you add them.

Credential isolation

Your Claro credential 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 'retrieve a sales quote' or 'change a quote status', and Jentic returns the matching Claro CPQ operation with its input schema so the agent calls the right endpoint without reading the proxy docs.

FAQs

Specific to using Claro CPQ Quotes API through Jentic.

Is there a Claro CPQ Quotes API MCP server?

You do not need an MCP server to give your agent the Claro CPQ Quotes API. Jentic connects it directly from the API Directory: import the API, store your credential once, and your agent calls the quote retrieve, update, and status operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

What authentication does the Claro CPQ Quotes API use?

The API accepts several schemes per its OpenAPI spec: HTTP basic, a bearer token, an apiKey sent in the X-API-Key header, and OAuth2 client credentials. Through Jentic the credential you choose is stored encrypted in your own Jentic One instance and supplied only when an allowed call runs, so it never reaches the agent's context.

Can I update a quote that has already been created with the Claro CPQ Quotes API?

Yes, as long as the quote's status still permits changes, such as initial or feasibility pending. The update operation partially modifies the quote, and a separate status operation advances it once feasibility is concluded.

What are the rate limits for the Claro CPQ Quotes API?

The OpenAPI spec does not specify rate limits. Because the operations are proxied through Claro's Apigee gateway, limits are set per credential on the gateway, so confirm the quota that applies to your keys in the Claro developer documentation at https://developers.claro.com.br.

Can I limit what my agent is allowed to do with the Claro CPQ Quotes API?

Yes. Write a rule that permits only the read operations, listing and retrieving quotes, when the agent should report on the pipeline, and add the update and status operations only for workflows that must change a quote, with every call logged.

How do I retrieve a customer's quotes with the Claro CPQ Quotes API through Jentic?

Search Jentic for 'retrieve a sales quote' to surface the quote operations, load the input schema, pass the customer or opportunity identifier, and execute. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Claro CPQ Quotes API

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Community OpenAPI document · agent-readyCRMDeal PipelineapiKey, oauth2, basic, bearer4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Retrieve and update Configure-Price-Quote sales quotes in Claro Brazil's CPQ system: list quotes for a customer or opportunity, fetch a single quote, patch a quote in progress, and change a quote's status.

Use for: List all quotes for a given Claro customer, Retrieve a specific CPQ quote that was offered to a client, Update the line items on a quote that is still editable, Move a quote from the initial status to feasibility pending

Not supported: Does not handle order fulfillment, billing, or payment collection. Use for retrieving and updating CPQ sales quotes only.

The Claro CPQ Quotes API retrieves and updates sales quotes tied to a customer or an opportunity inside Claro Brazil's Configure, Price, Quote system. It lists every quote linked to a client or opportunity, returns a single previously created quote, partially updates a quote while its status still allows changes, and advances a quote through its lifecycle status. The operations proxy Claro's CPQ backend through its Apigee gateway, so agents work against a stable quote contract rather than the underlying provisioning system. It is aimed at sales and commercial workflows that need programmatic access to telecom quotes.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

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: A-Signals: 4

60%

Example Density

How richly the API is illustrated with examples.

68%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: DSignals: 4

75%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

50%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

47%

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: C-Signals: 1

51%

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: C+Signals: 1

59%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Claro CPQ Quotes API to your agent

Capabilities

Start building with Claro CPQ Quotes API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Claro CPQ Quotes API

Jentic AI Readiness Score

Quote – CPQ Quotes (Proxy Apigee: quote-cpqquotes-v1)

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