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 publishes 1 API on the APIs.io network. Tagged areas include Company, Security, Identity Security, Authorization, and Access Management.

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

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

38.6/100 thin ▬ flat Agent 39/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs 1 MCP Servers
CompanySecurityIdentity SecurityAuthorizationAccess ManagementIdentity GovernanceAPI

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 38.6/100 · thin
Contract Quality 5.7 / 25
Developer Ergonomics 15.2 / 20
Commercial Clarity 4.7 / 20
Operational Transparency 3.8 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 39/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/veza: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

veza-mcp.yml

MCP SERVER

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
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
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-21'
image: https://veza.com/wp-content/uploads/2024/01/Veza_Stacked-1.png
tags:
- 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:
- 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: MCPServer
  url: mcp/veza-mcp.yml
- 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