Skip to content
Skills Library
Security · Analysis

api-inventory

/api-inventory

Build and maintain an API inventory — discover documented, undocumented (shadow) and deprecated (zombie) APIs from gateways, traffic, code and specs; record owner, authentication, data classification and exposure. Use when starting an API security program, after acquisitions, or when OWASP API9 (improper inventory management) risk is suspected.

Repository
Claude-Blue ↗
Licence
MIT
Last repository change
01.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build and maintain an API inventory — discover documented, undocumented (shadow) and deprecated (zombie) APIs from gateways, traffic, code and specs; record owner, authentication, data classification and exposure. Use when starting an API security program, after acquisitions, or when OWASP API9 (improper inventory management) risk is suspected.

Original author description

Build and maintain an API inventory — discover documented, undocumented (shadow) and deprecated (zombie) APIs from gateways, traffic, code and specs; record owner, authentication, data classification and exposure. Use when starting an API security program, after acquisitions, or when OWASP API9 (improper inventory management) risk is suspected.

How it works

  1. Discovery sources
  2. Inventory record
  3. Findings to flag
  4. Related skills
  5. References
Original SKILL.md headings · 43 lines, 272 words
SKILL.md preview
---
name: api-inventory
description: Build and maintain an API inventory — discover documented, undocumented (shadow) and deprecated (zombie) APIs from gateways, traffic, code and specs; record owner, authentication, data classification and exposure. Use when starting an API security program, after acquisitions, or when OWASP API9 (improper inventory management) risk is suspected.
license: MIT
metadata:
  category: api-security
  version: "2.0.0"
  verification: documented
---

# API Inventory

## Discovery sources

| Source | Finds |
|---|---|
| API gateways / ingress (Apigee, Kong, AWS API Gateway, Azure APIM, NGINX/Envoy configs) | Published routes, auth policies |
| Traffic (WAF, load balancer, CDN logs, service mesh telemetry) | Endpoints actually called, including undocumented ones |
| Code & specs (OpenAPI/Swagger files, GraphQL schemas, route definitions, gRPC protos) | Intended surface |
| Cloud inventory (Lambda URLs, API Gateway stages, App Service, Cloud Run) | Forgotten deployments |
| External ASM (`external-attack-surface-review`) | Internet-exposed hosts with `/api`, `/swagger`, `/graphql`, `/v1` paths |
| Mobile apps (`mobile-app-security-review`) | Backend endpoints embedded in apps |

Examples:
```sh
aws apigateway get-rest-apis --query 'items[].{id:id,name:name,endpoint:endpointConfiguration.types}'
aws apigatewayv2 get-apis --query 'Items[].{id:ApiId,name:Name,protocol:ProtocolType,endpoint:ApiEndpoint}'
az apim api list --resource-group RG --service-name APIM -o table
# Endpoints seen in access logs (combined log format) vs. spec
awk '{print $7}' access.log | sed -E 's/[0-9]+/{id}/g; s/\?.*//' | sort | uniq -c | sort -rn | head -50
```

## Inventory record

`API | Base URL/host | Environment | Owner | Spec link/version | AuthN (OAuth2/OIDC, API key, mTLS, none) | Data classification | Exposure (internet/partner/internal) | Rate limits | Logging | Last seen in traffic | Status (active/deprecated/retire-by)`

## Findings to flag

- Endpoints in traffic but not in any spec (shadow APIs).
- Old versions (`/v1`) still reachable after `/v2` release (zombie APIs) — often lacking newer authorization fixes.
- Non-production environments exposed to the internet with real data.
- APIs with no owner or no authentication.

## Related skills

`api-schema-security`, `api-authorization-testing`, `external-attack-surface-review`, `shadow-it-discovery`

## References

- OWASP API Security Top 10 (2023): https://owasp.org/API-Security/editions/2023/en/0x11-t10/
- OpenAPI Specification: https://spec.openapis.org/oas/latest.html

Versions

The database has no other skills named api-inventory.

Database snapshot: 13.11.2026 · package version 5990eb67f28f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100detecting-shadow-api-endpoints
    Discover and inventory shadow API endpoints that operate outside documented OpenAPI/Swagger specs, using traffic analysis against API gateways (Kong, AWS API Gateway, Envoy), cloud configuration scanning, and source code repository mining for undocumented routes. Use when…
  • 95vendor-management
    Implement vendor risk management programs. Assess third-party security and maintain vendor inventory. Use when managing supplier security.
  • 100implementing-api-security-posture-management
    Implements API Security Posture Management (API-SPM) to continuously discover, classify, and risk-score APIs -- including internal, external, partner, and shadow endpoints -- while aggregating findings from DAST, SAST, SCA, and runtime monitoring into a unified risk view. Use…
  • 100vendor-management
    Implement vendor risk management programs. Assess third-party security and maintain vendor inventory. Use when managing supplier security.
  • 100vendor-management
    Implement vendor risk management programs. Assess third-party security and maintain vendor inventory. Use when managing supplier security.
  • 100owasp-api-security-top-10-hardening
    Use this skill when harden REST and GraphQL APIs against the OWASP API Security Top 10 vulnerabilities.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.