Yeti Snow API

Name: Yeti Snow API
Brand: Yeti Snow API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey3 EndpointsREST

For Agents

Programmatically create service request, list service requests. Covers 3 operations with apiKey authentication.

Install Jentic One Beta

Connect the Yeti Snow API to your agent

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

Create service request

List service requests

Integrate Yeti Snow API into automated workflows

Query and filter Yeti Snow API records by parameters

GET STARTED

Start building with Yeti Snow API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Yeti Snow API for, with concrete tasks.

★ Developer Tools Operations

Use the Yeti Snow API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including create service request, list service requests, list service routes.

Call POST /service-requests to create service request

Automated routes Management

Automate routes operations by combining multiple Yeti Snow API endpoints. Agents can list service requests and then list service routes in a single workflow.

Call GET /service-requests to list service requests, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Yeti Snow 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 'create service request', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — api for snow removal and service management.

METHOD

PATH

DESCRIPTION

POST

/service-requests

Create service request

GET

/service-requests

List service requests

GET

/routes

List service routes

POST

/service-requests

Create service request

GET

/service-requests

List service requests

GET

/routes

List service routes

Why Jentic?

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

Setup

Wiring Yeti Snow by hand means sending your key in the Authorization header on api.yetisnow.com, and coding retries yourself. Through Jentic you install once, import Yeti Snow from the API Directory, store the key once, and your agent calls it.

Permission scoping

Yeti Snow carries no resource id in the URL path for these endpoints, so limit the agent to the operations it needs, such as creating and listing service requests or reading routes. You choose that set, so nothing beyond those operations travels with the credential.

Credential isolation

Your Yeti Snow 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 'create a service request' or 'list routes', and Jentic returns the matching Yeti Snow operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Yeti Snow API through Jentic.

What authentication does the Yeti Snow API use?

The Yeti Snow 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 create service request with the Yeti Snow API?

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

What are the rate limits for the Yeti Snow 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 create service request through Jentic?

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

How many endpoints does the Yeti Snow API have?

The Yeti Snow API exposes 3 endpoints covering routes, service-requests operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Yeti Snow operations and credentials the agent may use. Since these endpoints carry no resource id in the URL path, you scope the agent to only the operations it needs, such as creating service requests (POST /service-requests), listing service requests (GET /service-requests), or reading routes (GET /routes). Nothing beyond the operations you allow travels with the stored API key.