canonical: https://jentic.com/apis/romulus.live/romulus-live

# Romulus Live Romulus API

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.

## For AI agents

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

## Scope

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

## Capabilities

- Validate API authentication
- List robocall configurations
- Initiate a robocall
- Create robocall webhook subscription
- Delete robocall webhook subscription
- Search AI agents

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'validate API authentication', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Authentication** — API authentication validation
- **Robocalls** — Robocall configuration and execution
- **Agents** — AI agent management
- **AgentCallTasks** — AI agent call task management
- **Calls** — Outbound call initiation

## AI readiness

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.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/romulus.live/romulus-live/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

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