Install Jentic One Beta

Connect the Skaala API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Skaala 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%2Fskaala.ai%2Fskaala" | sh

Step 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%2Fskaala.ai%2Fskaala" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Skaala API.

POST /conversations

GET /conversations

Integrate Skaala API into automated workflows

Query and filter Skaala API records by parameters

Monitor Skaala API operational status and events

GET STARTED

Start building with Skaala API

Explore with Jentic One

View OpenAPI Document

Automated Bookings Management

Automate bookings operations by combining multiple Skaala API endpoints. Agents can get /conversations and then get /calls in a single workflow.

Call GET /conversations to get /conversations, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Skaala 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 'post /conversations', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — ai-powered receptionist platform api for managing bookings, calls, contacts, and more.

METHOD

PATH

DESCRIPTION

POST

/conversations

POST /conversations

GET

/conversations

GET /conversations

GET

/calls

GET /calls

POST

/bookings

POST /bookings

GET

/bookings

GET /bookings

POST

/webhooks/verify

POST /webhooks/verify

GET

/bookings/{bookingId}

GET /bookings/{bookingId}

PUT

/bookings/{bookingId}

PUT /bookings/{bookingId}

POST

/conversations

POST /conversations

GET

/conversations

GET /conversations

GET

/calls

GET /calls

POST

/bookings

POST /bookings

GET

/bookings

GET /bookings

POST

/webhooks/verify

POST /webhooks/verify

GET

/bookings/{bookingId}

GET /bookings/{bookingId}

PUT

/bookings/{bookingId}

PUT /bookings/{bookingId}

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Skaala API by hand means setting up its key in the Authorization header and carrying it across every conversation, call, and booking request yourself. Through Jentic you install once, import Skaala from the API Directory, store the key once, and your agent calls it.

Permission scoping

Skaala puts the booking id in the URL path (/bookings/{bookingId}), so a rule can pin your agent to one booking: it can read and update that booking and nothing else. You choose the operations it may call, so creating new bookings or reading conversations is not included unless you add it.

Credential isolation

Your Skaala 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 conversations' or 'read a booking', and Jentic returns the matching Skaala operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Skaala API through Jentic.

What authentication does the Skaala API use?

The Skaala 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 post /conversations with the Skaala API?

Yes. Use the POST /conversations endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Skaala 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 post /conversations through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post /conversations'. Jentic returns the matching Skaala API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Skaala API have?

The Skaala API exposes 15 endpoints covering bookings, calls, conversations operations.

Can I limit what my agent is allowed to do with the Skaala API?

Yes. Because you run Jentic One yourself, your own rules decide which Skaala operations and credentials the agent may use. Since Skaala puts the booking id in the URL path (/bookings/{bookingId}), you can pin the agent to a single booking so it can read and update that one booking and nothing else. Any other operation, such as creating new bookings or reading conversations, stays off limits unless you explicitly grant it.

Skaala API

Name: Skaala API
Brand: Skaala API
Availability: InStock

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey15 EndpointsREST

For Agents

Programmatically post /conversations, get /conversations. Covers 15 operations with apiKey authentication.

Use for: I need to post /conversations, I want to /conversations, Search for /calls, Find all post /bookings

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

AI-powered receptionist platform API for managing bookings, calls, contacts, and more. The API exposes 15 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Skaala API to your agent

Capabilities

Start building with Skaala API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Skaala API