Veza

Veza is an identity security platform. Its Open Authorization API (OAA) publishes identity, resource, and authorization metadata from custom or unsupported applications into the Veza Entity Catalog, making access across systems searchable and governable for least-privilege enforcement, access reviews, and rules and alerts. The REST API manages custom providers and their data sources, pushes OAA JSON payloads (users, groups, roles, resources, permissions), and runs authorization assessment queries and reports. It authenticates with a per-tenant API key presented as a bearer token, with official Python and C# SDKs and a command-line client.

Veza is listed with 1 API on the APIs.io network. Tagged areas include Company, Security, Identity Security, Authorization, and Identity and Access Management.

The Veza catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Veza’s developer surface includes engineering blog, documentation, API reference, getting-started guide, signup flow, authentication, CLI, and 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

40.3/100 developing ▬ flat Agent 24/100 agent aware Front door AI 6/6 dominant Heartbeat 88/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 2 Agent Skills

Company Security Identity Security Authorization Identity and Access Management Identity Governance

Kin Score

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

Composite quality — 40.3/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 11.6 / 17

Access Clarity 4.0 / 17

Operational Transparency 2.9 / 11

Contract Governance 0.5 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.1 / 15

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 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 6 / 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 3 / 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.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/veza/"><img src="https://apis.io/badge/veza/card.svg" alt="Veza 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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

8 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 23.7 — up to +15.3 composite points
Contract Governance scores 4.5 — up to +11.5 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/veza/apis.yml: open an issue on github.com/api-evangelist/veza 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.

IAM

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Veza Open Authorization API (OAA)

Publish identity, resource and authorization metadata from custom or unsupported applications into the Veza Entity Catalog, and run authorization assessment queries and reports.

Agent Skills 2

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

Publish an OAA payload to Veza

AGENT SKILL

Run a Veza assessment query and report

AGENT SKILL

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Veza Webhooks

ASYNCAPI

Security Posture 2

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

Veza Authentication

apiKey · 1 scheme

SECURITY

Veza Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

StatusPage

StatusPage

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Blog

BlogRSS

Blog

Website

Source (apis.yml)

aid: veza
name: Veza
description: Veza is an identity security platform. Its Open Authorization API (OAA) publishes identity, resource, and authorization
  metadata from custom or unsupported applications into the Veza Entity Catalog, making access across systems searchable and
  governable for least-privilege enforcement, access reviews, and rules and alerts. The REST API manages custom providers
  and their data sources, pushes OAA JSON payloads (users, groups, roles, resources, permissions), and runs authorization
  assessment queries and reports. It authenticates with a per-tenant API key presented as a bearer token, with official Python
  and C# SDKs and a command-line client.
url: https://raw.githubusercontent.com/api-evangelist/veza/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- accel
- bain-capital-ventures
- gv
- norwest-venture-partners
- true-ventures
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://veza.com/wp-content/uploads/2024/01/Veza_Stacked-1.png
x-docs-platform: vitepress
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
tags:
- Company
- Security
- Identity Security
- Authorization
- Identity and Access Management
- Identity Governance
tags_raw:
- Company
- Security
- Identity Security
- Authorization
- Access Management
- Identity Governance
- API
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Veza Open Authorization API (OAA)
  description: Publish identity, resource and authorization metadata from custom or unsupported applications into the Veza
    Entity Catalog, and run authorization assessment queries and reports.
  humanURL: https://developer.veza.com/
  baseURL: https://tenant.vezacloud.com/api/v1
  properties:
  - type: Documentation
    url: https://developer.veza.com/
  - type: APIReference
    url: https://developer.veza.com/oaa/reference/api/oaa-push-api.html
  - type: GettingStarted
    url: https://developer.veza.com/oaa/guide/getting-started.html
common:
- url: https://veza.com/blog/
  type: Blog
- url: https://veza.com/feed/
  type: BlogRSS
- type: DeveloperPortal
  url: https://developer.veza.com/
- type: Documentation
  url: https://developer.veza.com/
- type: APIReference
  url: https://developer.veza.com/oaa/reference/api/oaa-push-api.html
- type: GettingStarted
  url: https://developer.veza.com/oaa/guide/getting-started.html
- type: GitHubOrganization
  url: https://github.com/veza
- type: Blog
  url: https://www.veza.com/blog
- type: StatusPage
  url: https://status.veza.com/
- type: SignUp
  url: https://www.veza.com/demo/
- type: PrivacyPolicy
  url: https://www.veza.com/privacy-policy/
- type: Authentication
  url: authentication/veza-authentication.yml
- type: Packages
  url: packages/veza-packages.yml
- type: SDKs
  url: packages/veza-packages.yml
- type: CLI
  url: cli/veza-cli.yml
- type: X-MCPServerCandidate
  url: mcp/veza-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: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/veza-llms.txt
- type: Conventions
  url: conventions/veza-conventions.yml
- type: ErrorCatalog
  url: errors/veza-problem-types.yml
- type: Lifecycle
  url: lifecycle/veza-lifecycle.yml
- type: Conformance
  url: conformance/veza-conformance.yml
- type: DataModel
  url: data-model/veza-data-model.yml
- type: Webhooks
  url: asyncapi/veza-webhooks.yml
- type: DomainSecurity
  url: security/veza-domain-security.yml
- type: Website
  url: https://www.veza.com/
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 13
  pass: local-v1

Veza API — frequently asked questions

Does Veza have an API?

Yes. APIs.io lists 1 API from Veza, including Veza Open Authorization API (OAA).

How do I authenticate with the Veza API?

Veza uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Veza Authentication.

Is the Veza API ready for AI agents?

Veza has a Kin Score of 40.3 out of 100 (developing) and an Agent Readiness score of 23.6 (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/veza"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/veza/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.