OWASP API Security Project

The OWASP API Security Project focuses on strategies and solutions to understand and mitigate the unique vulnerabilities and security risks of Application Programming Interfaces. The project produces and maintains the OWASP API Security Top 10, a community-driven list of the most critical API security risks for developers, architects, and security professionals.

OWASP API Security Project is listed with 1 API on the APIs.io network. Tagged areas include Security, Standards, and OWASP.

OWASP API Security Project’s developer surface includes documentation, GitHub presence, and 6 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

11.7/100 emerging ▬ flat Agent 1/100 human only Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemium

1 API

Security Standards OWASP

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 11.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.8 / 17

Access Clarity 1.1 / 17

Operational Transparency 2.4 / 11

Contract Governance 0.0 / 10

Discoverability 4.1 / 9

Regulatory Posture 1.8 / 15

Agent readiness — 1/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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/owasp-api-security-project/"><img src="https://apis.io/badge/owasp-api-security-project/card.svg" alt="OWASP API Security Project 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
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) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →

12 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points Ask about this →
Access Clarity scores 6.4 — up to +18.7 composite points Ask about this →
Developer Ergonomics scores 16.7 — up to +16.7 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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/owasp-api-security-project/apis.yml: open an issue on github.com/api-evangelist/owasp-api-security-project 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.

OWASP

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.

OWASP API Security Project

The OWASP API Security Project produces and maintains the OWASP API Security Top 10, a list of the most critical API security risks. It provides guidance, tools, and references ...

OWASP API Security Project pricing

Not yet checked against OWASP API Security Project's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against OWASP API Security Project's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

OWASP API Security Project Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

OWASP API Security Project Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

OWASP API Security Project Finops

FINOPS

Security Posture 2

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

OWASP API Security Project Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

OWASP API Security Project Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Build 1

SDKs, sample code, and the tooling you integrate with

GitHub

GitHub

Access & Security 2

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: owasp-api-security-project
name: OWASP API Security Project
description: The OWASP API Security Project focuses on strategies and solutions to understand and mitigate the unique vulnerabilities
  and security risks of Application Programming Interfaces. The project produces and maintains the OWASP API Security Top
  10, a community-driven list of the most critical API security risks for developers, architects, and security professionals.
type: Index
deliveryModel:
  model: unknown
  license_evidence:
    not_product:
    - owasp/api-security
  open_source: unknown
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-13'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/owasp-api-security-project.png
tags:
- Security
- Standards
- OWASP
created: '2025-01-08'
modified: '2026-04-28'
url: https://raw.githubusercontent.com/api-evangelist/owasp-api-security-project/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: owasp-api-security-project:owasp-api-security-project
  name: OWASP API Security Project
  description: The OWASP API Security Project produces and maintains the OWASP API Security Top 10, a list of the most critical
    API security risks. It provides guidance, tools, and references to help organizations identify and address API-specific
    vulnerabilities such as broken object level authorization, broken authentication, and excessive data exposure.
  humanURL: https://owasp.org/www-project-api-security/
  tags:
  - Security
  - Standards
  properties:
  - type: Documentation
    url: https://owasp.org/www-project-api-security/
  - type: Reference
    url: https://owasp.org/API-Security/editions/2023/en/0x00-header/
common:
- type: Plans
  url: plans/owasp-api-security-project-plans-pricing.yml
- type: RateLimits
  url: rate-limits/owasp-api-security-project-rate-limits.yml
- type: FinOps
  url: finops/owasp-api-security-project-finops.yml
- type: VulnerabilityDisclosure
  url: security/owasp-api-security-project-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/owasp-api-security-project-domain-security.yml
- type: Website
  url: https://owasp.org/www-project-api-security/
- type: Documentation
  url: https://owasp.org/www-project-api-security/
- type: GitHub
  url: https://github.com/OWASP/API-Security
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-parent: owasp
x-relationship: product

OWASP API Security Project — frequently asked questions

Does OWASP API Security Project have an API?

Yes. APIs.io lists 1 API from OWASP API Security Project, including OWASP API Security Project.

How much does the OWASP API Security Project cost?

APIs.io lists 3 pricing plans for OWASP API Security Project, with each plan's price, limits and inclusions under Pricing on this page.

Is the OWASP API Security Project ready for AI agents?

OWASP API Security Project has a Kin Score of 11.7 out of 100 (emerging) and an Agent Readiness score of 0.6 (human-only), scored by API Evangelist on 2026-11-13.

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/owasp-api-security-project"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/owasp-api-security-project/operations?limit=25"

How their score was established

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