Verta
Verta was an MLOps model-management, experiment-tracking, and model-registry platform (verta.ai) acquired by Cloudera on 2024-06-03; verta.ai now redirects to Cloudera Machine Learning. Its open-source core, ModelDB (Apache-2.0, github.com/VertaAI/modeldb), remains actively maintained and provides ML model versioning, metadata management, and experiment tracking. The REST API is a grpc-gateway transcoding of the ModelDB and UAC gRPC services — 11 services and 264 operations served under /v1 — covering projects, experiments, experiment runs, datasets, a model registry, Git-style versioning, deployment stages, monitoring, and SCIM/UAC access control.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Verta the way a machine reads it — 14 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Verta scores 30.4/100 (thin), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Verta
Each block below is one kind of artifact we hold for Verta. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Verta AuthzService API
The AuthzService API from Verta — 4 operation(s) for authzservice.
Verta DatasetService API
The DatasetService API from Verta — 17 operation(s) for datasetservice.
Verta ExperimentRunService API
The ExperimentRunService API from Verta — 60 operation(s) for experimentrunservice.
Verta ExperimentService API
The ExperimentService API from Verta — 25 operation(s) for experimentservice.
Verta MonitoredEntityService API
The MonitoredEntityService API from Verta — 4 operation(s) for monitoredentityservice.
Verta ProjectService API
The ProjectService API from Verta — 32 operation(s) for projectservice.
Verta RegistryService API
The RegistryService API from Verta — 31 operation(s) for registryservice.
Verta SCIMConfigurationService API
The SCIMConfigurationService API from Verta — 1 operation(s) for scimconfigurationservice.
Verta StageService API
The StageService API from Verta — 9 operation(s) for stageservice.
Verta UACService API
The UACService API from Verta — 13 operation(s) for uacservice.
Verta VersioningService API
The VersioningService API from Verta — 40 operation(s) for versioningservice.
Scroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
verta-mcp.yml
MCP SERVERSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Verta — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
← All providers · Data indexed from github.com/api-evangelist/verta · machine-readable index on apis.io