Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Schedule to Call Me Integration 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%2Fscheduletocall.me%2Fscheduletocall" | 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%2Fscheduletocall.me%2Fscheduletocall" | 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 Schedule to Call Me Integration API.
Schedule a callback to a destination number at a scheduled_for time in a named timezone, with an Idempotency-Key for safe retries
Add a private announcement_message of up to 1000 characters that is spoken only to your callback phone before connecting
Choose recording_mode off, regular, or silent per call, or fall back to the saved default
Reschedule a pending call to a new time, or cancel it, using If-Match with the current row_version
GET STARTED
List calls with a status filter and a limit of up to 50, or fetch one call by callId
List your verified callback phones, masked to their last four digits, with caller-ID approval status
Patterns agents use Schedule to Call Me Integration API for, with concrete tasks.
★ AI agent booking a call for later
When a user tells their agent to call a supplier first thing tomorrow, the agent searches Jentic for 'schedule a phone callback', loads the createScheduledCall operation, and books the call with the destination, scheduled_for time, and the user's timezone. It can add an announcement_message reminding the user what the call is about, and the integration credential is injected at call time.
POST /api/v1/integration/calls with destination +14155550123, scheduled_for 2026-11-21T14:00:00Z, timezone America/New_York, and announcement_message 'Call about the late shipment', with an Idempotency-Key
Rescheduling and cancelling safely
Plans change, and two edits at once should not silently overwrite each other. Each call carries a row_version, and the reschedule and cancel operations require it in an If-Match header along with an Idempotency-Key, so a stale or repeated request fails cleanly instead of moving the wrong booking. Only pending calls can be rescheduled or cancelled.
GET /api/v1/integration/calls/{callId} for call call_01HZX, then PATCH /api/v1/integration/calls/{callId} with If-Match set to its row_version, scheduled_for 2026-11-21T16:30:00Z, and timezone America/New_York
Reviewing upcoming calls without exposing numbers
An assistant summarizing the day can list scheduled calls with a status filter and see each call's time, timezone, recording mode, and masked destination with its country. Because phone values are masked to the last four digits, the summary is useful without full numbers ever appearing in responses.
Call GET /api/v1/integration/calls with limit 50 and summarize each call's scheduled_for, timezone, and destination last4
6 endpoints — the schedule to call me integration api books phone callbacks for a set time: at the scheduled moment the service rings your verified callback phone, optionally speaks a private announcement, and connects you to the destination number.
METHOD
PATH
DESCRIPTION
/api/v1/integration/calls
Create a scheduled callback
/api/v1/integration/calls
List masked calls
/api/v1/integration/calls/{callId}
Get one call
/api/v1/integration/calls/{callId}
Reschedule a pending call
/api/v1/integration/calls/{callId}
Cancel a pending call
/api/v1/integration/phones
List verified callback phones
/api/v1/integration/calls
Create a scheduled callback
/api/v1/integration/calls
List masked calls
/api/v1/integration/calls/{callId}
Get one call
/api/v1/integration/calls/{callId}
Reschedule a pending call
/api/v1/integration/calls/{callId}
Cancel a pending call
/api/v1/integration/phones
List verified callback phones
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Schedule to Call Me by hand means choosing between an stcm bearer key and a Clerk OAuth flow with scopes, generating an Idempotency-Key per write, and threading row_version into If-Match on every change. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Schedule to Call Me puts the call id in the URL path (/api/v1/integration/calls/{callId}), so a rule can pin your agent to one booked call and the operations you pick. You choose the operations it may call, so changes like rescheduleCall or cancelCall are not included unless you add them.
Credential isolation
Your Schedule to Call Me credential 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 'schedule a phone callback' or 'reschedule a call', and Jentic returns the matching operation, such as createScheduledCall or rescheduleCall, with its input schema and required headers.
Alternatives and complements available in the Jentic catalogue.
Specific to using Schedule to Call Me Integration API through Jentic.
What authentication does the Schedule to Call Me Integration API use?
Per its OpenAPI spec, every operation accepts either a bearer integration credential, formatted as stcm_test_ or stcm_live_ keys, or OAuth 2.0 authorization code through Clerk with the scopes calls:read, calls:write, and phones:read. Reads need calls:read or phones:read and changes need calls:write. Through Jentic the credential is stored by your own instance and attached at call time.
Why are phone numbers masked in Schedule to Call Me responses?
The API masks every phone value in responses: destinations show only last4 and country, and callback phones and caller IDs show only last4. The optional announcement_message is encrypted at rest and excluded from call responses and webhooks.
How do I reschedule a call without conflicts?
Read the call to get its row_version, then send the reschedule with If-Match set to that value, an Idempotency-Key, and the new scheduled_for and timezone. Cancelling uses the same two headers. Both work only on pending calls.
What are the rate limits for the Schedule to Call Me Integration API?
The OpenAPI spec does not specify rate limits. Check https://scheduletocall.me for current limits.
Is there a Schedule to Call Me MCP server?
You don't need an MCP server to give your agent Schedule to Call Me. Jentic connects it directly from the API Directory: import it, store your integration credential once, and your agent calls the scheduling operations when it needs them.
How do I schedule a callback through Jentic?
Search Jentic for 'schedule a phone callback', load the createScheduledCall operation, and execute POST /api/v1/integration/calls with destination, scheduled_for, and timezone, plus an Idempotency-Key header. 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 Schedule to Call Me Integration API?
Yes. Allow only GET /api/v1/integration/calls and GET /api/v1/integration/phones, and the agent can report on upcoming calls and verified phones but cannot book, move, or cancel anything. Every call it makes is logged.
For Agents
Schedule a phone callback that rings your phone and connects you to a destination number at a set time, then list, reschedule, or cancel pending calls.
Use for: Schedule a call to +14155550123 tomorrow at 9am New York time, Move my 3pm callback to 4:30pm, Cancel the pending call with the dentist, List all my upcoming scheduled calls
Not supported: Does not send SMS, record voicemail, or manage calendar events. Use for scheduling, rescheduling, and cancelling phone callbacks only.
The Schedule to Call Me Integration API books phone callbacks for a set time: at the scheduled moment the service rings your verified callback phone, optionally speaks a private announcement, and connects you to the destination number. Calls are created idempotently with a destination, a scheduled_for time, and a timezone, and can be listed, read, rescheduled, or cancelled while pending, with row_version and If-Match guarding against conflicting edits. Phone numbers in responses are always masked to their last four digits, and recording can be set to off, regular, or silent per call. The API is in preview at version 1.0.0-preview.
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>