Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Roezan Integrations 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%2Froezan.com%2Froezan" | shStep 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%2Froezan.com%2Froezan" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Roezan Integrations API.
Send an SMS or MMS to a phone number, with up to 10 media links, from a chosen sender number
Create or update a contact by phone with first name, last name, email, lists, and tags
Subscribe a contact to a list or unsubscribe them, using list IDs from the lists call
Draft a broadcast for one or more list_ids and get the expected recipient count and credit estimate
GET STARTED
Send a broadcast preview to one phone, then schedule it, send it now, or cancel a pending send
Read a contact's message history and a broadcast's recipients with cursor pagination
Subscribe a hookUrl to Roezan webhook events and delete subscriptions you no longer need
Patterns agents use Roezan Integrations API for, with concrete tasks.
★ AI agent that texts customers from your Roezan number
An AI agent handling follow-ups can send a text from the business's own Roezan number instead of a separate SMS gateway. Through Jentic the agent searches for 'send an SMS', loads the Roezan send-message operation with its input schema, and posts the phone, message, and sender with the API key added at call time. Because the contact and its history live in Roezan, the conversation stays in the same inbox the team already uses.
GET /api/integrations/senders to pick a sender, then POST /api/integrations/message/send with phone, countryCode, from, and the follow-up message
Syncing leads into lists and tags
When a form or CRM captures a lead, an integration creates or updates the Roezan contact by phone and subscribes it to the right list. Tags can be added or removed by tag ID, and custom fields defined on the account can be set on the contact. List and tag IDs come from the lists and tags calls, so the integration never hard-codes them.
GET /api/integrations/lists to find the 'New leads' list ID, then POST /api/integrations/lists/subscribe with that list and the lead's phone
Scheduled SMS broadcasts with a safety check
A broadcast starts as a draft that names the lists, message, and optional schedule, and the response returns the expected recipient count and a credit estimate before anything is sent. A preview call sends one test message to a real handset. Scheduling moves the draft to pending, a pending broadcast can be cancelled back to a draft, and the status call reports delivery counters after the send.
POST /api/integrations/broadcasts with name, list_ids, and message, POST /api/integrations/broadcasts/{id}/preview to one phone, then POST /api/integrations/broadcasts/{id}/schedule with scheduled_time and scheduled_timezone
Delivery and reply events to your own service
A webhook subscription is one event and URL pair, so a service subscribes once per event it wants. Subscriptions can be filtered by lists and tags, include broadcasts, and carry a signing secret for verifying deliveries. Listing subscriptions shows those created through the API, the Roezan dashboard, or connected apps such as Zapier.
POST /api/integrations/hooks with event 'message.status', a hookUrl, and a signingSecret, then GET /api/integrations/hooks to confirm it is listed
22 endpoints — the roezan integrations api sends sms and mms messages from a roezan account and keeps its contact lists, tags, and custom fields in sync with other services.
METHOD
PATH
DESCRIPTION
/api/integrations/message/send
Send an SMS or MMS
/api/integrations/contacts
Create or update a contact
/api/integrations/lists/subscribe
Subscribe a contact to a list
/api/integrations/broadcasts
Create a draft broadcast
/api/integrations/broadcasts/{id}/schedule
Schedule or send a broadcast
/api/integrations/broadcasts/{id}
Get broadcast status and delivery stats
/api/integrations/contacts/{id}/messages
Get a contact's message history
/api/integrations/hooks
Subscribe to a webhook event
/api/integrations/message/send
Send an SMS or MMS
/api/integrations/contacts
Create or update a contact
/api/integrations/lists/subscribe
Subscribe a contact to a list
/api/integrations/broadcasts
Create a draft broadcast
/api/integrations/broadcasts/{id}/schedule
Schedule or send a broadcast
/api/integrations/broadcasts/{id}
Get broadcast status and delivery stats
/api/integrations/contacts/{id}/messages
Get a contact's message history
/api/integrations/hooks
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Roezan by hand means sending the account key in the x-api-key header, looking up list, tag, and sender IDs before you can act, and following the draft, preview, and schedule sequence for broadcasts. Through Jentic you install once, import Roezan from the API Directory, store the key once, and your agent calls it.
Permission scoping
Roezan carries the phone number and list inside the request body for sends and subscriptions, so rules bound which operations your agent may call, not which contact it reaches. Broadcast calls put the broadcast id in the URL path, so a rule can pin your agent to one broadcast for preview and status. You choose the operations it may call, so sending ones like message send or broadcast scheduling are not included unless you add them.
Credential isolation
Your Roezan 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 SMS' or 'schedule a text broadcast', and Jentic returns the matching Roezan operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Roezan Integrations API through Jentic.
What authentication does the Roezan Integrations API use?
Per its OpenAPI spec, the Roezan Integrations API authenticates with your account API key sent in the `x-api-key` request header. Through Jentic the key is held by your own instance and injected at call time, so the agent never sees it.
Can I schedule an SMS broadcast with the Roezan Integrations API?
Yes. POST /api/integrations/broadcasts creates a draft for one or more list_ids and returns the expected recipient count and a credit estimate. POST /api/integrations/broadcasts/{id}/schedule then schedules it with scheduled_time and scheduled_timezone, or sends it now with send_now, and GET /api/integrations/broadcasts/{id} reports its status and delivery counters.
What are the rate limits for the Roezan Integrations API?
The OpenAPI spec states per-credential limits on some operations, in addition to a global integrations limit it does not quantify: 5 requests/second for the message-history and broadcast-recipient reads, and 1 request/second for creating, previewing, scheduling, and cancelling broadcasts. Exceeding a limit returns 429 with RateLimit headers. Contact support@roezan.com for the current global limit.
Is there a Roezan MCP server?
You do not need an MCP server to give your agent Roezan. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the messaging, contact, and broadcast operations it needs on demand without loading another server's tool definitions into its context.
How do I send an SMS through Jentic with the Roezan Integrations API?
Search Jentic for 'send an SMS', load the POST /api/integrations/message/send operation, and execute it with phone and message, plus from to choose one of the numbers returned by GET /api/integrations/senders. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Roezan Integrations API?
Yes. For a list-hygiene agent, write a rule that allows only POST /api/integrations/contacts and POST /api/integrations/lists/subscribe, so it can add and update contacts and subscribe them to lists but cannot send a message, schedule a broadcast, or delete webhooks. Every call it makes is logged.
Can I send MMS with images through the Roezan Integrations API?
Yes. POST /api/integrations/message/send accepts media links alongside the message body. The spec allows a maximum of 10 media links per message and a maximum message size of 5MB.
For Agents
Send SMS and MMS through a Roezan account, manage contacts, lists, and tags by phone number, and draft, preview, schedule, and track SMS broadcasts.
Use for: Send a text message to this customer's phone number, Subscribe a new lead to my Roezan list, I need to tag a contact as a VIP, Draft a broadcast to my newsletter list for Friday morning
Not supported: Does not place voice calls, send email campaigns, or provision new phone numbers. Use for SMS and MMS messaging, contact lists, and broadcasts on a Roezan account only.
The Roezan Integrations API sends SMS and MMS messages from a Roezan account and keeps its contact lists, tags, and custom fields in sync with other services. It creates or updates contacts by phone number, subscribes and unsubscribes them from lists, and adds or removes tags. Broadcasts follow a two-step flow: create a draft against one or more lists with a recipient count and credit estimate, send a test to one phone, then schedule it or send it now, and poll its status and delivery counters afterwards. Webhook subscriptions deliver events such as message status to a URL of your choice.
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.
Subscribe to a webhook event
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>