canonical: https://jentic.com/apis/yeti-snow.com/yeti-snow # Yeti Snow API API for snow removal and service management. The API exposes 3 endpoints secured with apiKey authentication. ## For AI agents Programmatically create service request, list service requests. Covers 3 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Create service request - List service requests - Integrate Yeti Snow API into automated workflows - Query and filter Yeti Snow API records by parameters - Monitor Yeti Snow API operational status and events ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create service request', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/service-requests` | Create service request | | GET | `/service-requests` | List service requests | | GET | `/routes` | List service routes | ## Key resources - **routes** — Operations related to routes - **service-requests** — Operations related to service-requests ## AI readiness 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. - **Score:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 52 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/yeti-snow.com/yeti-snow/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### 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.