Install Jentic One Beta

Connect the RooR SMS API to your agent

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

Send automated SMS campaign message

Manage communications data programmatically

Integrate RooR SMS API into automated workflows

Query and filter RooR SMS API records by parameters

Monitor RooR SMS API operational status and events

GET STARTED

Start building with RooR SMS API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query RooR SMS API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary RooR SMS API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call RooR SMS API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'send automated sms campaign message', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

1 endpoints — roor sms api for sending automated campaign sms messages with recipient management.

METHOD

PATH

DESCRIPTION

POST

/v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id}

Send automated SMS campaign message

POST

/v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id}

Send automated SMS campaign message

Why Jentic?

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

Setup

Wiring the RooR SMS API by hand means placing your API key in the URL path on the campaign-send call and handling the request plumbing yourself. Through Jentic you install once, import the RooR SMS API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The RooR SMS API exposes a single campaign-send operation with the campaign id in the URL path, so limit the agent to just that send operation. You choose whether it may call it, and it can do nothing beyond what you allow.

Credential isolation

Your RooR SMS API 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 'send an automated SMS campaign', and Jentic returns the matching RooR SMS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using RooR SMS API through Jentic.

What authentication does the RooR SMS API use?

The RooR SMS API uses an API key passed in the `api_key` path. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I send automated sms campaign message with the RooR SMS API?

Yes. Use the POST /v2.0/api/post/autoCampaignSend/key/{api_key}/response/json/campaign/{campaign_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RooR SMS API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I send automated sms campaign message through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send automated sms campaign message'. Jentic returns the matching RooR SMS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the RooR SMS API have?

The RooR SMS API exposes 1 endpoints covering sms campaigns operations.

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

Yes. Jentic One is self-hosted, so you set the rules that decide which operations and credentials your agent may use. The RooR SMS API exposes only a single campaign-send operation, POST autoCampaignSend with the campaign id in the URL path, so you can allow the agent to trigger that send and nothing else. Your stored API key is injected at execution time and never enters the agent's prompt or context, and the agent can do nothing beyond the send call you permit.

Roor App RooR SMS API

Name: RooR SMS API
Brand: RooR SMS API
Availability: InStock

AI ReadinessNon-Ready (F)0/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey1 EndpointsREST

For Agents

Programmatically send automated sms campaign message. Covers 1 operations with apiKey authentication.

Use for: I need to send automated sms campaign message, Find available communications operations, Get the current status of RooR SMS API resources, List all records from RooR SMS API

Not supported: Does not handle payments, crm, or developer tools - use for communications only.

RooR SMS API for sending automated campaign SMS messages with recipient management. The API exposes 1 endpoints secured with apiKey authentication.

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.

Specification Validity

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

100%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

76%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

50%

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

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

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RooR SMS API to your agent

Capabilities

Start building with RooR SMS API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Roor App RooR SMS API

Jentic AI Readiness Score

RooR SMS 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