Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sendr 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%2Fsendr.io%2Fsendr" | 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%2Fsendr.io%2Fsendr" | 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 Sendr API.
Verify API key
List page templates
Get template variables
Generate personalized Sendr page
Sendr page webhook handler
GET STARTED
Patterns agents use Sendr API for, with concrete tasks.
★ Developer Tools Operations
Use the Sendr API to perform developer tools operations programmatically. The API provides 13 endpoints covering core functionality including verify API key, list page templates, get template variables.
Call GET /seat/me to verify API key
Automated Audio Management
Automate audio operations by combining multiple Sendr API endpoints. Agents can list page templates and then get template variables in a single workflow.
Call GET /api/v1/page-template/list to list page templates, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Sendr 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 'verify API key', load the operation schema, and execute with Jentic-managed credentials
13 endpoints — sendr provides personalized page generation, dynamic audio, video generation, and webhook management apis.
METHOD
PATH
DESCRIPTION
/seat/me
Verify API key
/api/v1/page-template/list
List page templates
/api/v1/page-template/{id}/variables
Get template variables
/api/v1/enrichment/sendr-page
Generate personalized Sendr page
/api/v1/enrichment/sendr-page-webhook
Sendr page webhook handler
/api/v1/enrichment/dynamic-audio
Generate dynamic audio
/api/v1/enrichment/generate-video
Generate video
/api/v1/webhook
Create webhook
/seat/me
Verify API key
/api/v1/page-template/list
List page templates
/api/v1/page-template/{id}/variables
Get template variables
/api/v1/enrichment/sendr-page
Generate personalized Sendr page
/api/v1/enrichment/sendr-page-webhook
Sendr page webhook handler
/api/v1/enrichment/dynamic-audio
Generate dynamic audio
/api/v1/enrichment/generate-video
Generate video
/api/v1/webhook
Create webhook
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Sendr by hand means setting the X-API-Key header on every request and handling its page-template and enrichment calls yourself. Through Jentic you install once, import Sendr from the API Directory, store the key once, and your agent calls it.
Permission scoping
Sendr puts the page-template id in the URL path (/api/v1/page-template/{id}/variables), so a rule can pin your agent to one template: it can read that template's variables and nothing else. You choose the operations it may call, so webhook creation or secret reveal is not included unless you add it.
Credential isolation
Your Sendr 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 page templates' or 'generate a personalized video', and Jentic returns the matching Sendr 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 Sendr API through Jentic.
What authentication does the Sendr API use?
The Sendr 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 verify API key with the Sendr API?
Yes. Use the GET /seat/me endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Sendr 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 verify API key through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'verify API key'. Jentic returns the matching Sendr API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Sendr API have?
The Sendr API exposes 13 endpoints covering audio, authentication, pages operations.
Can I limit what my agent is allowed to do with the Sendr API?
Yes. Because you run Jentic One yourself, your own rules decide which Sendr operations and credentials the agent may use. Since Sendr puts the template id in the URL path, such as GET /api/v1/page-template/{id}/variables, you can pin the agent to a single template so it reads that template's variables and nothing else. You also choose the operations it may call, so actions like creating a webhook via POST /api/v1/webhook or generating video stay off limits unless you explicitly grant them.
For Agents
Programmatically verify API key, list page templates. Covers 13 operations with apiKey authentication.
Use for: I need to verify API key, I want to page templates, Search for template variables, Find all generate personalized sendr page
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Sendr provides personalized page generation, dynamic audio, video generation, and webhook management APIs. The API exposes 13 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>