Yeti-Switch API

Name: Yeti-Switch API
Brand: Yeti-Switch API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationbearer101 EndpointsREST

For Agents

Programmatically set account balance, apply balance correction. Covers 101 operations with bearer authentication.

Use for: I need to set account balance, I want to apply balance correction, Search for account, Find all accounts

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Yeti-Switch is a Session Border Controller (SBC) for VoIP interconnection. It provides two JSONAPI-compliant REST APIs: an Admin API for configuration and provisioning, and a Customer API for end-user access to rates, CDRs, and account information. This spec covers the Admin API. All requests and responses use the JSONAPI specification (application/vnd.api+json). The API exposes 101 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Yeti-Switch API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Yeti-Switch 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%2Fyeti-switch.org%2Fyeti-switch" | 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%2Fyeti-switch.org%2Fyeti-switch" | 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 Yeti-Switch API.

Set account balance

Apply balance correction

Create Account

List Accounts

Get Account by ID

GET STARTED

Start building with Yeti-Switch API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Yeti-Switch API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Yeti-Switch API to perform identity auth operations programmatically. The API provides 101 endpoints covering core functionality including set account balance, apply balance correction, create account.

Call PUT /balances/{account_external_id} to set account balance

Automated Accounts Management

Automate accounts operations by combining multiple Yeti-Switch API endpoints. Agents can apply balance correction and then create account in a single workflow.

Call PUT /balances-correction/{account_external_id} to apply balance correction, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Yeti-Switch 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 bearer tokens manually.

Search Jentic for 'set account balance', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

101 endpoints — yeti-switch is a session border controller (sbc) for voip interconnection.

METHOD

PATH

DESCRIPTION

PUT

/balances/{account_external_id}

Set account balance

PUT

/balances-correction/{account_external_id}

Apply balance correction

POST

/accounts

Create Account

GET

/accounts

List Accounts

GET

/accounts/{id}

Get Account by ID

PATCH

/accounts/{id}

Update Account

DELETE

/accounts/{id}

Delete Account

POST

/contractors

Create Contractor

PUT

/balances/{account_external_id}

Set account balance

PUT

/balances-correction/{account_external_id}

Apply balance correction

POST

/accounts

Create Account

GET

/accounts

List Accounts

GET

/accounts/{id}

Get Account by ID

PATCH

/accounts/{id}

Update Account

DELETE

/accounts/{id}

Delete Account

POST

/contractors

Create Contractor

Why Jentic?

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

Setup

Wiring Yeti-Switch by hand means sending its admin bearer token against your own server_url host, accepting that the token carries full administrator access, and handling retries yourself. Through Jentic you install once, import Yeti-Switch from the API Directory, store the token once, and your agent calls it.

Permission scoping

Yeti-Switch puts the account id in the URL path (/accounts/{id}), so a rule can pin your agent to one account: it can read and update that account and nothing else. You choose the operations it may call, so destructive ones like deleting an account or correcting a balance are not included unless you add them.

Credential isolation

Your Yeti-Switch token 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 'set an account balance' or 'create an account', and Jentic returns the matching Yeti-Switch operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Yeti-Switch API through Jentic.

What authentication does the Yeti-Switch API use?

The Yeti-Switch API uses a Bearer token 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 set account balance with the Yeti-Switch API?

Yes. Use the PUT /balances/{account_external_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Yeti-Switch 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 set account balance through Jentic?

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

How many endpoints does the Yeti-Switch API have?

The Yeti-Switch API exposes 101 endpoints covering accounts, adminusers, balances operations.

Can I limit what my agent is allowed to do with the Yeti-Switch API?

Yes. Jentic One runs self-hosted, so your own rules decide which operations and credentials the agent can use. Because Yeti-Switch puts the account id in the URL path, such as /accounts/{id}, you can pin the agent to a single account and let it read and update only that one. You also choose which operations it may call, so destructive actions like DELETE /accounts/{id} or applying a balance correction stay off unless you add them.

Yeti-Switch API

Connect the Yeti-Switch API to your agent

Capabilities

Start building with Yeti-Switch API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs