Install Jentic One Beta

Connect the Cadence API to your agent

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

Open conversations and send RCS messages to opted-in numbers

Check whether a brand may message a given number before sending

Poll per-carrier launch and verification state for an agent

GET STARTED

Start building with Cadence API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cadence API for, with concrete tasks.

★ Agent-driven RCS onboarding

An AI agent can create a brand, add an agent to it, run the readiness check, and submit it for carrier review, then poll verification and launch state per carrier until it is live. Sandbox keys let the whole flow run without touching Google.

Create a brand, add an agent, run the readiness check, and submit the brand for carrier review

Consent-checked messaging

A messaging agent can confirm a brand may message a number, open a conversation, send the message, and read the delivery evidence, so it never sends to a number that has not opted in. Re-consent events can be recorded for someone who opted back in.

Check that the brand may message +15551234567, open a conversation, and send a text message

Delivery webhook monitoring

An operations agent can register a delivery webhook, send a signed test event, and inspect recent delivery attempts to confirm inbound activity is routed correctly. Cadence distinguishes delivery webhooks from Google inbound routing so the two are not confused.

Key Endpoints

84 endpoints — the cadence api registers rcs brands and agents, submits them for google and carrier review, and runs conversations that send messages to opted-in numbers.

METHOD

PATH

DESCRIPTION

POST

/v1/brands

Create a brand

POST

/v1/brands/{id}/submit

Submit a brand for carrier review

POST

/v1/conversations

Open a conversation and send the first message

GET

/v1/brands/{id}/optins/{e164}

Check if a brand may message a number

POST

/v1/webhooks

POST

/v1/conversations/{id}/simulate-inbound

Simulate an inbound reply

POST

/v1/brands

Create a brand

POST

/v1/brands/{id}/submit

Submit a brand for carrier review

POST

/v1/conversations

Open a conversation and send the first message

GET

/v1/brands/{id}/optins/{e164}

Check if a brand may message a number

POST

/v1/webhooks

POST

/v1/conversations/{id}/simulate-inbound

Simulate an inbound reply

Why Jentic?

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

Setup

Wiring Cadence by hand means handling its bearer-token auth, choosing between its production and secondary hosts, and respecting the confirmation flag three irreversible operations require. Through Jentic you install once, import Cadence from the API Directory, store the token once, and your agent calls it.

Permission scoping

You choose which Cadence operations the agent may call, such as conversations and consent checks, so irreversible operations like deleting a brand are not included unless you add them.

Credential isolation

Your Cadence 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 'send an RCS message to a number', and Jentic returns the matching Cadence operation with its input schema so the agent calls the right endpoint without browsing the docs.

FAQs

Specific to using Cadence API through Jentic.

What authentication does the Cadence API use?

The Cadence API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Signup and a few onboarding endpoints need no credential, and sandbox keys let you build without reaching a real phone.

Is there a Cadence MCP server?

You do not need an MCP server to give your agent Cadence. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the brand, conversation, and webhook operations without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only conversation and consent-check operations, so the agent can message opted-in numbers but cannot delete a brand or an agent until you add those irreversible operations, and every call it makes is logged.

Can I check whether a brand may message a number with the Cadence API?

Yes. The brand opt-in endpoint answers whether a specific brand may message a specific E.164 number, so an agent can confirm consent before opening a conversation.

What are the rate limits for the Cadence API?

The OpenAPI spec does not publish a numeric rate limit. Carrier and Google review timelines govern how quickly a brand goes live, and the observed-verification-times endpoint reports current estimates.

How do I send an RCS message with the Cadence API through Jentic?

Search Jentic for 'send an RCS message to a number', and it returns the Cadence conversation operation with its input schema. Confirm consent, open a conversation, and send the message, using a sandbox key while you build. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Cadencercs Cadence API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsSms Messagingbearer84 EndpointsREST

For Agents

Register RCS brands and agents, run conversations and send messages, check consent and delivery, and track carrier launch and verification state.

Use for: Register a new RCS brand and submit it for carrier review, Open a conversation and send the first RCS message, Check whether a brand may message a given phone number, Poll the per-carrier launch state for an agent

Not supported: Does not handle email delivery, voice calls, or payment processing. Use for RCS brand and agent registration, messaging, and delivery only.

The Cadence API registers RCS brands and agents, submits them for Google and carrier review, and runs conversations that send messages to opted-in numbers. It tracks consent, delivery evidence, per-carrier launch and verification state, and delivery webhooks. Sandbox keys simulate delivery so nothing reaches a phone while you build, and three operations are irreversible unless re-sent with a confirmation flag.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

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

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

74%

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: D+Signals: 4

53%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

81%

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

88%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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

67%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Cadence API to your agent

Capabilities

Start building with Cadence API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cadencercs Cadence API

Jentic AI Readiness Score

Cadence API

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