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.

Verta publishes 11 API contracts indexed on the APIs.io network, including AuthzService API, DatasetService API, ExperimentRunService API, and 8 more. Tagged areas include MLOps, Machine Learning, Model Management, Experiment Tracking, and Model Registry.

The Verta catalog on APIs.io includes 1 Spectral governance ruleset.

Verta’s developer surface includes authentication, changelog, documentation, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

24.8/100 emerging ▬ flat Agent 19/100 agent aware Front door AI 6/6 dominant Heartbeat 0/100 dormant self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

12 published contracts 2 Agent Skills

MLOps Machine Learning Model Management Experiment Tracking Model RegistryModel VersioningMetadata Open Source Company

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information & Data Management

BC-610

DatasetServiceExperimentRunServiceExperimentServiceMonitoredEntityServiceRegistryServiceStageService

POST /model_versions/find POST /api/v1/monitoring/monitored_entity/createMonitoredEntity POST /stage/commitTransition

Cybersecurity Management

BC-620

AuthzServiceUACService

POST /uac/addDevKey POST /uac/createUser GET /uac/getCurrentUser

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 24.8/100 · emerging

Contract Quality 5.6 / 16

Developer Ergonomics 2.7 / 13

Access Clarity 0.0 / 13

Operational Transparency 1.6 / 8

Contract Governance 1.4 / 8

Discoverability 5.1 / 7

Regulatory Posture 1.5 / 15

Open Source Surface 2.5 / 10

Create-or-Update Ergonomics 1.1 / 10

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/verta/"><img src="https://apis.io/badge/verta/card.svg" alt="Verta on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points
Contract Quality scores 34.2 — up to +16.5 composite points
Developer Ergonomics scores 20.8 — up to +15.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/verta/apis.yml: open an issue on github.com/api-evangelist/verta to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 11

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 for all 11

Open Collections 11

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

deployment/APISync.proto AuthzService API

OPEN COLLECTION

deployment/APISync.proto AuthzService DatasetService API

OPEN COLLECTION

deployment/APISync.proto AuthzService ExperimentRunService API

OPEN COLLECTION

deployment/APISync.proto AuthzService ExperimentService API

OPEN COLLECTION

deployment/APISync.proto AuthzService MonitoredEntityService API

OPEN COLLECTION

deployment/APISync.proto AuthzService ProjectService API

OPEN COLLECTION

deployment/APISync.proto AuthzService RegistryService API

OPEN COLLECTION

deployment/APISync.proto AuthzService SCIMConfigurationService API

OPEN COLLECTION

deployment/APISync.proto AuthzService StageService API

OPEN COLLECTION

deployment/APISync.proto AuthzService UACService API

OPEN COLLECTION

deployment/APISync.proto AuthzService VersioningService API

OPEN COLLECTION

Scroll for all 11

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Register and version a model in Verta ModelDB

AGENT SKILL

Track an ML experiment in Verta ModelDB

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Verta API Rules

38 rules · 34 errors 2 warnings 2 info

SPECTRAL

OpenAPI Overlays 12

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Verta Apisync Overlay

2 actions · documentation · verta-APISync.swagger.json

GENERATED

Verta Authorization Overlay

2 actions · documentation · verta-Authorization.swagger.json

GENERATED

Verta Datasetservice Overlay

2 actions · documentation · verta-DatasetService.swagger.json

GENERATED

Verta Experimentrunservice Overlay

2 actions · documentation · verta-ExperimentRunService.swagger.json

GENERATED

Verta Experimentservice Overlay

2 actions · documentation · verta-ExperimentService.swagger.json

GENERATED

Verta Monitoredentity Overlay

2 actions · documentation · verta-MonitoredEntity.swagger.json

GENERATED

Verta Projectservice Overlay

2 actions · documentation · verta-ProjectService.swagger.json

GENERATED

Verta Registryservice Overlay

2 actions · documentation · verta-RegistryService.swagger.json

GENERATED

Verta Scimconfiguration Overlay

2 actions · documentation · verta-SCIMConfiguration.swagger.json

GENERATED

Verta Stageservice Overlay

2 actions · documentation · verta-StageService.swagger.json

GENERATED

Verta Uacservice Overlay

2 actions · documentation · verta-UACService.swagger.json

GENERATED

Verta Versioningservice Overlay

2 actions · documentation · verta-VersioningService.swagger.json

GENERATED

Scroll for all 12

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Verta Authentication

custom · 0 schemes

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Verta Agentic Access

264 operations · 178 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

DataModel

Conformance

Lifecycle

Build 4

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

GitHubOrganization

GitHubOrganization

SourceCode

SourceCode

Access & Security 1

Authentication, authorization, and security posture

Authentication

Authentication

Operate 3

Status, limits, changes, and where to get help

IssueTracker

IssueTracker

Releases

Releases

ChangeLog

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

License

License

Company 1

The organization behind the API

Website

Website

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

ParentCompany

ParentCompany

Overlay

Overlay

Source (apis.yml)

aid: verta
name: Verta
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/verta/refs/heads/main/apis.yml
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-11-06'
  method: derived
image: https://github.com/VertaAI.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- MLOps
- Machine Learning
- Model Management
- Experiment Tracking
- Model Registry
- Model Versioning
- Metadata
- Open Source
- Company
tags_raw:
- MLOps
- Machine Learning
- Model Management
- Experiment Tracking
- Model Registry
- Model Versioning
- Metadata
- Open Source
- Company
- Machine-Learning
- Open-Source
apis:
- aid: verta:verta-authzservice-api
  name: Verta AuthzService API
  description: The AuthzService API from Verta — 4 operation(s) for authzservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - AuthzService
  properties:
  - type: OpenAPI
    url: openapi/verta-authzservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-datasetservice-api
  name: Verta DatasetService API
  description: The DatasetService API from Verta — 17 operation(s) for datasetservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - DatasetService
  properties:
  - type: OpenAPI
    url: openapi/verta-datasetservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-experimentrunservice-api
  name: Verta ExperimentRunService API
  description: The ExperimentRunService API from Verta — 60 operation(s) for experimentrunservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - ExperimentRunService
  properties:
  - type: OpenAPI
    url: openapi/verta-experimentrunservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-experimentservice-api
  name: Verta ExperimentService API
  description: The ExperimentService API from Verta — 25 operation(s) for experimentservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - ExperimentService
  properties:
  - type: OpenAPI
    url: openapi/verta-experimentservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-monitoredentityservice-api
  name: Verta MonitoredEntityService API
  description: The MonitoredEntityService API from Verta — 4 operation(s) for monitoredentityservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - MonitoredEntityService
  properties:
  - type: OpenAPI
    url: openapi/verta-monitoredentityservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-projectservice-api
  name: Verta ProjectService API
  description: The ProjectService API from Verta — 32 operation(s) for projectservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - ProjectService
  properties:
  - type: OpenAPI
    url: openapi/verta-projectservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-registryservice-api
  name: Verta RegistryService API
  description: The RegistryService API from Verta — 31 operation(s) for registryservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - RegistryService
  properties:
  - type: OpenAPI
    url: openapi/verta-registryservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-scimconfigurationservice-api
  name: Verta SCIMConfigurationService API
  description: The SCIMConfigurationService API from Verta — 1 operation(s) for scimconfigurationservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - SCIMConfigurationService
  properties:
  - type: OpenAPI
    url: openapi/verta-scimconfigurationservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-stageservice-api
  name: Verta StageService API
  description: The StageService API from Verta — 9 operation(s) for stageservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - StageService
  properties:
  - type: OpenAPI
    url: openapi/verta-stageservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-uacservice-api
  name: Verta UACService API
  description: The UACService API from Verta — 13 operation(s) for uacservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - UACService
  properties:
  - type: OpenAPI
    url: openapi/verta-uacservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
- aid: verta:verta-versioningservice-api
  name: Verta VersioningService API
  description: The VersioningService API from Verta — 40 operation(s) for versioningservice.
  humanURL: https://docs.verta.ai/
  baseURL: https://docs.verta.ai/
  tags:
  - VersioningService
  properties:
  - type: OpenAPI
    url: openapi/verta-versioningservice-api-openapi.yml
  - type: Protobuf
    url: grpc/verta-APISync.proto
  - type: Protobuf
    url: grpc/verta-Authorization.proto
  - type: Protobuf
    url: grpc/verta-DatasetService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentRunService.proto
  - type: Protobuf
    url: grpc/verta-ExperimentService.proto
  - type: Protobuf
    url: grpc/verta-MonitoredEntity.proto
  - type: Protobuf
    url: grpc/verta-ProjectService.proto
  - type: Protobuf
    url: grpc/verta-RegistryService.proto
  - type: Protobuf
    url: grpc/verta-SCIMConfiguration.proto
  - type: Protobuf
    url: grpc/verta-StageService.proto
  - type: Protobuf
    url: grpc/verta-UACService.proto
  - type: Protobuf
    url: grpc/verta-VersioningService.proto
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/verta-capability-edges.yml
  name: Verta Business Capability Map
- type: ParentCompany
  url: https://apis.io/providers/cloudera/
  name: Cloudera
  x-relationship: acquired
  x-evidence: description names Cloudera and https://verta.ai now redirects to cloudera.com (roadmap#390, corroborate-dead.py)
- type: Website
  url: https://verta.ai
- type: IssueTracker
  url: https://github.com/VertaAI/modeldb/issues
- type: Releases
  url: https://github.com/VertaAI/modeldb/releases
- type: Overlay
  url: overlays/verta-apisync-overlay.yaml
- type: License
  name: Apache-2.0
  url: https://github.com/VertaAI/modeldb/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/verta-agentic-access.yml
- type: Authentication
  url: authentication/verta-authentication.yml
- type: Conventions
  url: conventions/verta-conventions.yml
- type: ErrorCatalog
  url: errors/verta-problem-types.yml
- type: DataModel
  url: data-model/verta-data-model.yml
- type: Conformance
  url: conformance/verta-conformance.yml
- type: Lifecycle
  url: lifecycle/verta-lifecycle.yml
- type: ChangeLog
  url: changelog/verta-changelog.yml
- type: Packages
  url: packages/verta-packages.yml
- type: SDKs
  url: packages/verta-packages.yml
- type: X-MCPServerCandidate
  url: mcp/verta-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.'
- type: LLMsTxt
  url: llms/verta-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Documentation
  url: https://docs.verta.ai/
- type: GitHubOrganization
  url: https://github.com/VertaAI
- type: SourceCode
  url: https://github.com/VertaAI/modeldb
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 14
  pass: local-v1

Verta API — frequently asked questions

Does Verta have an API?

Yes. APIs.io lists 11 APIs from Verta, including Verta AuthzService API, Verta DatasetService API and Verta ExperimentRunService API, and 8 more.

Is there an OpenAPI specification for the Verta API?

Yes. APIs.io indexes 11 OpenAPI specifications for Verta, each linked for download from this page.

How do I authenticate with the Verta API?

Verta uses bearer-token authentication (custom · 0 schemes). The details are profiled on APIs.io as Verta Authentication.

Is the Verta API ready for AI agents?

Verta has a Kin Score of 24.8 out of 100 (emerging) and an Agent Readiness score of 18.5 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/verta"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/verta/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/verta/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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