Skip to main content

APIClarity

non-cncf
First Research Pass

Content Lifecycle & Evolution State

1
Initial Seed
Metadata Loaded
2
First Research
Automated Gathering
3
Tech Writing
Content Structured
4
Approval
Editorial Verified
First Research Pass Completed: Initial facts, key features, and documentation links have been gathered. Detailed technical writing and synthesis are currently in queue.

Overview

APIClarity is a cloud API observability open-source project that discovers and monitors API traffic, reporting suspected security weaknesses or possible abuses. It operates by capturing all API traffic or actively testing endpoints, and can automatically reconstruct OpenAPI specifications when none are available.

Key Features

  • OpenAPI automatic reconstruction based on observed API traffic

  • Spec Diffs module to identify Shadow APIs, Zombie APIs, and specification deviations

  • Trace Analyzer module to discover weak authentications, sensitive data leaks, and BOLA risks

  • BFLA Detector to capture authorization models and identify Broken Function Level Authorization

  • Fuzzer module to actively test API endpoints based on specifications

  • Supports integrations with Istio Service Mesh, Kong, Tyk, Tap via DaemonSet, and OpenTelemetry

Use Cases

Used by DevOps and DevSecOps teams to monitor modern applications for zombie APIs, shadow APIs, data injection risks, and various authorization vulnerabilities in Kubernetes environments.

Getting Started

Install APIClarity in a Kubernetes cluster using Helm: `helm repo add apiclarity https://openclarity.github.io/apiclarity` followed by `helm install --values values.yaml --create-namespace apiclarity apiclarity/apiclarity -n apiclarity`.

Recent Updates

The project repository was archived by the owner on May 29, 2026, and is now read-only.

Did You Know?

Developed by Cisco (openclarity), APIClarity offers a modular architecture that supports a wide range of external traffic sources including Apigee X Gateway and BIG-IP LTM Load balancers.