hila REST API

The hila REST APIs provide CRUD operations to deploy, manage, and monitor machine-learning models — drift detection, explainability, model performance, alerts, data profiling, inference tracking, pipelines, projects, and segments. Authentication is a bearer access_token obtained from POST /v1/user/login. The API is served per customer deployment from the webservices subdomain (e.g. https://webservices.company.vianai.site), with interactive OpenAPI docs at /docs on that host.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/hila-rest-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
name: hila REST API
description: The hila REST APIs provide CRUD operations to deploy, manage, and monitor machine-learning
  models — drift detection, explainability, model performance, alerts, data profiling, inference tracking,
  pipelines, projects, and segments. Authentication is a bearer access_token obtained from POST /v1/user/login.
  The API is served per customer deployment from the webservices subdomain (e.g. https://webservices.company.vianai.site),
  with interactive OpenAPI docs at /docs on that host.
humanURL: https://docs.vian.ai/5.0-r2/apis.html
baseURL: https://webservices.company.vianai.site
tags:
- Machine-Learning
- Model Monitoring
- MLOps
tags_raw:
- Machine Learning
- Model Monitoring
- MLOps
properties:
- type: APIReference
  url: https://docs.vian.ai/5.0-r2/api-list.html
- type: GettingStarted
  url: https://docs.vian.ai/5.0-r2/api-quickstart.html
- type: Authentication
  url: authentication/vianai-systems-authentication.yml
- type: Conventions
  url: conventions/vianai-systems-conventions.yml
- type: X-MCPServerCandidate
  url: mcp/vianai-systems-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate
    — a tool list derived from the published API contracts, not an existing server. The scorer already
    read the manifest and reported mcp_server correctly; the MCPServer type was crediting the artifact-type
    surfaces with a server that does not exist.'