Capability Mapper · MAP

What could an AI agent do through this API?

Capability Mapper translates each documented OpenAPI operation into deterministic capability metadata: access type, risk tags, authentication state, permission alternatives, and sensitive-data context.

Input → output

Turn operations into a capability inventory.

The mapper reuses the canonical OpenAPI operation surface. One capability represents one documented path and HTTP method.

INPUTopenapi.yaml
Paths, methods, security requirements
MAPPERoperation → capability
Deterministic static classification
OUTPUTagent-capabilities 1.0
Terminal + JSON

Example result

See capability, context, and documented controls together.

This illustrative result shows the shape of output, not customer data or runtime proof.

POST /refunds
access write
tags [financial, privileged]
auth_state mandatory
permission_alternatives [["refunds:write"]]

Use cases

Answer the tool-access question before wiring the tool.

Use the inventory during agent tool design, AppSec review, API contract review, or as the foundation for Readiness.

Agent builders

See which documented actions become potential agent tools.

AppSec

Review destructive, privileged, financial, object-access, and sensitive-data tags.

API teams

Find missing or unclear security metadata in the contract surface.

Static scope: documented permission alternatives are descriptive metadata. Capability Mapper does not prove the agent can reach an operation or that the server enforces the declared authorization.
$99 one-time purchase.

Map the capability surface first.

Capability Mapper is a one-time Agent Security purchase with the capability_mapper entitlement.

Analyze your API