Install Jentic One Beta

Connect the Romulus API to your agent

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

Validate API authentication

List robocall configurations

Initiate a robocall

Create robocall webhook subscription

Delete robocall webhook subscription

GET STARTED

Start building with Romulus API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Romulus API for, with concrete tasks.

★ Payments Operations

Use the Romulus API to perform payments operations programmatically. The API provides 21 endpoints covering core functionality including validate API authentication, list robocall configurations, initiate a robocall.

Call POST /v1/me to validate API authentication

Automated Authentication Management

Automate authentication operations by combining multiple Romulus API endpoints. Agents can list robocall configurations and then initiate a robocall in a single workflow.

Call GET /v1/call-tasks/robocalls/configurations to list robocall configurations, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Romulus 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 'validate API authentication', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

21 endpoints — romulus is a solution for automated qualification calls and messaging.

METHOD

PATH

DESCRIPTION

POST

/v1/me

Validate API authentication

GET

/v1/call-tasks/robocalls/configurations

List robocall configurations

POST

/v1/call-tasks/robocalls

Initiate a robocall

POST

/v1/call-tasks/webhook-subscriptions

Create robocall webhook subscription

GET

/v1/call-tasks/webhook-subscriptions

List robocall webhook subscriptions

DELETE

/v1/call-tasks/webhook-subscriptions/{webhookSubscriptionId}

Delete robocall webhook subscription

GET

/v1/ai-agents/agents/search

Search AI agents

POST

/v1/ai-agents/agents/{agentId}/call

Initiate outbound call via AI agent

POST

/v1/me

Validate API authentication

GET

/v1/call-tasks/robocalls/configurations

List robocall configurations

POST

/v1/call-tasks/robocalls

Initiate a robocall

POST

/v1/call-tasks/webhook-subscriptions

Create robocall webhook subscription

GET

/v1/call-tasks/webhook-subscriptions

List robocall webhook subscriptions

DELETE

/v1/call-tasks/webhook-subscriptions/{webhookSubscriptionId}

Delete robocall webhook subscription

GET

/v1/ai-agents/agents/search

Search AI agents

POST

/v1/ai-agents/agents/{agentId}/call

Why Jentic?

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

Setup

Wiring the Romulus API by hand means passing its API key in the Authorization header on every request and handling the request plumbing yourself. Through Jentic you install once, import the Romulus API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Romulus puts ids like the webhook subscription and agent in the URL path (/call-tasks/webhook-subscriptions/{webhookSubscriptionId}), so a rule can pin your agent to those resources. You choose the operations it may call, so destructive ones like deleting a webhook subscription or placing a robocall are not included unless you add them.

Credential isolation

Your Romulus 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 'list robocall configurations' or 'search AI agents', and Jentic returns the matching Romulus operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Romulus API through Jentic.

What authentication does the Romulus API use?

The Romulus API uses an API key passed in the `Authorization` header. 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 validate API authentication with the Romulus API?

Yes. Use the POST /v1/me endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Romulus 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 validate API authentication through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate API authentication'. Jentic returns the matching Romulus API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Romulus API have?

The Romulus API exposes 21 endpoints covering authentication, robocalls, agents operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Romulus operations your agent may call and which credentials it may use. Because Romulus puts resource ids in the URL path, such as /v1/call-tasks/webhook-subscriptions/{webhookSubscriptionId} and /v1/ai-agents/agents/{agentId}/call, you can pin the agent to specific webhook subscriptions or agents. You choose the operations it can reach, so destructive calls like deleting a webhook subscription or placing a robocall stay out of scope unless you grant them.

Romulus Live Romulus API

Name: Romulus API
Brand: Romulus API
Availability: InStock

AI ReadinessAI-Aware (B)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey21 EndpointsREST

For Agents

Programmatically validate API authentication, list robocall configurations. Covers 21 operations with apiKey authentication.

Use for: I need to validate API authentication, I want to robocall configurations, Search for initiate a robocall, Find all robocall webhook subscription

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

Romulus is a solution for automated qualification calls and messaging. Supports robocalls, AI agent calls, campaigns, WhatsApp messaging, and webhook subscriptions. The API exposes 21 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

98%

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: B-Signals: 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: C-Signals: 4

49%

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.

55%

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

50%

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

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Romulus API to your agent

Capabilities

Start building with Romulus API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Romulus Live Romulus API

Jentic AI Readiness Score

Romulus 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