Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sendit 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%2Fsendit.co.il%2Fsendit-co-il" | 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%2Fsendit.co.il%2Fsendit-co-il" | 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 Sendit SMS API.
Send SMS or campaign
Get message status
Integrate Sendit SMS API into automated workflows
Query and filter Sendit SMS API records by parameters
Monitor Sendit SMS API operational status and events
GET STARTED
Patterns agents use Sendit SMS API for, with concrete tasks.
★ Communications Operations
Use the Sendit SMS API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including send sms or campaign, get message status.
Call POST /sms/send to send sms or campaign
Data Retrieval and Monitoring
Query Sendit 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 Sendit SMS API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Sendit 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 sms or campaign', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — sendit sms api for sending sms messages and managing campaigns.
METHOD
PATH
DESCRIPTION
/sms/send
Send SMS or campaign
/sms/status/{message_id}
Get message status
/sms/send
Send SMS or campaign
/sms/status/{message_id}
Get message status
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Sendit SMS API by hand means setting up its X-API-Key header auth against sendit.co.il/api/v1 and handling status codes yourself. Through Jentic you install once, import the Sendit SMS API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Sendit SMS API sends the message id in the path only to check delivery status, so scope your agent to the operations it needs, such as sending an SMS or reading a message status. You choose the operations it may call, so sending is not included unless you add it.
Credential isolation
Your Sendit 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 SMS message', and Jentic returns the matching Sendit SMS 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 Sendit SMS API through Jentic.
What authentication does the Sendit SMS API use?
The Sendit SMS API uses an API key passed in the `X-API-Key` 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 send sms or campaign with the Sendit SMS API?
Yes. Use the POST /sms/send endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Sendit 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 sms or campaign through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send sms or campaign'. Jentic returns the matching Sendit SMS API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Sendit SMS API have?
The Sendit SMS API exposes 2 endpoints covering sms operations.
Can I limit what my agent is allowed to do with the Sendit SMS API?
Yes. Because you run Jentic One yourself, your own rules decide which Sendit SMS operations and credentials the agent may use. The Sendit SMS API exposes two operations, sending a message with POST /sms/send and reading delivery status with GET /sms/status/{message_id}, and you grant only the ones the agent needs. If you allow status reads but not sending, the agent can check delivery on a message ID without ever being able to send an SMS.
For Agents
Programmatically send sms or campaign, get message status. Covers 2 operations with apiKey authentication.
Use for: I need to send sms or campaign, I want to message status, Get the current status of Sendit SMS API resources, List all records from Sendit SMS API
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Sendit SMS API for sending SMS messages and managing campaigns. Send individual messages or bulk campaigns with scheduling capabilities. The API exposes 2 endpoints secured with apiKey authentication.
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.
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>