APIGovernance.Dev
APIGovernance.Dev is an AI-powered API governance platform that enforces API best practices through automated reviews trained on 10,000 public APIs. It provides the API Governance Top-10 list of best practices, automated CI/CD integration, and tools to help organizations deliver consistent, industry-standard APIs. Powered by PerfAI, Inc.
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 APIGovernance.Dev the way a machine reads it — 32 machine-readable artifacts across 1 API, 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 — APIGovernance.Dev scores 27.2/100 (thin), with a separate agent-readiness read of 3/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
APIGovernance.Dev sells an AI API-governance review product as an end-user SaaS and publishes no developer surface at all: every discovery path on apigovernance.dev (/openapi.json, /swagger.json, /api-docs, /docs, /llms.txt, /robots.txt and the whole /.well-known/* set) returns a real HTTP 404, there is no docs subdomain, and the one application host the site links to, app.apigovernance.dev, does not complete a TCP connection on port 443 — while the parent company's own perfai.ai/llms.txt declares the API-governance positioning "outdated" in favour of a different product on a different domain.
This is an honest zero, not a gap in our research. APIGovernance.Dev does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://apigovernance.dev/→ HTTP 200https://apigovernance.dev/openapi.json→ HTTP 404https://apigovernance.dev/docs→ HTTP 404https://apigovernance.dev/.well-known/agent-card.json→ HTTP 404https://apigovernance.dev/pricing→ HTTP 404https://app.apigovernance.dev/home→ HTTP 0https://perfai.ai/llms.txt→ HTTP 200
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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from APIGovernance.Dev's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apigovernance-dev/"
title="APIGovernance.Dev on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apigovernance-dev.svg"
alt="APIGovernance.Dev Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/apigovernance-dev/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apigovernance-dev/"
title="APIGovernance.Dev on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apigovernance-dev/card.svg"
alt="APIGovernance.Dev Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile APIGovernance.Dev
Each block below is one kind of artifact we hold for APIGovernance.Dev. 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 1
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.
APIGovernance.Dev
APIGovernance.Dev provides automated API governance reviews using AI trained on 10,000 public APIs. It offers the API Governance Top-10 best practices list, CI/CD integration, a...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apigovernance Dev Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Apigovernance Dev Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
AI-Powered API Reviews
Automated API governance reviews trained on patterns from 10,000 public APIs.
API Governance Top-10
Curated list of the top 10 API governance best practices across security, design, and documentation.
CI/CD Integration
GitHub Actions and CI/CD pipeline integration for automated governance checks.
API Gateway Integration
Integration with popular API gateways for runtime governance enforcement.
Issue Tracking Integration
Jira and GitHub Issues integration for governance violation tracking.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Apigovernance Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
APIGovernance.Dev API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apigovernance Guideline Structure
JSON STRUCTUREApigovernance Policy Structure
JSON STRUCTUREApigovernance Review Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Apigovernance Policy Example
EXAMPLEApigovernance Review Example
EXAMPLESecurity 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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Automated API Review
Automatically review API specifications against governance guidelines before release.
Team Standards Enforcement
Enforce consistent API standards across multiple development teams.
API Design Guidance
Provide developers with actionable best practice guidance during API design.
Compliance Auditing
Audit existing APIs for compliance with organizational governance policies.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
GitHub Actions
CI/CD integration for automated governance checks on API specification changes.
Jira
Create Jira issues for governance violations found during reviews.
GitHub Issues
Create GitHub issues for governance violations.
API Gateways
Integration with API gateway platforms for runtime policy enforcement.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Free Plan
Basic API governance reviews with the API Governance Top-10 checks.
Growth Plan
$199/month with advanced governance automation and CI/CD integration.
Enterprise Plan
Custom pricing with full governance suite, SSO, and dedicated support.
Resources
Every other property we hold for APIGovernance.Dev — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 1
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
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apigovernance-dev · machine-readable index on apis.io
This is an independent, third-party profile of APIGovernance.Dev, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.