# OpenAPI Security Summary Resolver

> OpenAPI Security Summary Resolver is a paid API for AI agents from agent402.tools, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Parses an OpenAPI 3.x or Swagger 2.x document and returns a structured summary of all security schemes, document-level defaults, and per-operation authentication requirements

## Facts

- Endpoint: POST https://agent402.tools/api/openapi-security-summary
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/openapi-security-summary-resolver-d7d5c53d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V8MU9eb1Pr31LoB_HDA7w

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability openapi-security-summary-resolver-d7d5c53d -d '<json body>'
```

Example prompt: Can you analyze this OpenAPI spec and tell me all the security schemes it defines, what the document-level auth defaults are, and which individual operations have their own auth requirements? Here's the spec: {paste OpenAPI JSON/object here}.

## When to prefer this

Use this endpoint when you need to programmatically understand the authentication requirements of an OpenAPI or Swagger document — especially useful before generating client code, configuring API gateways, building auth middleware, or auditing APIs for security coverage. Prefer this over manual parsing when you need a structured, normalized view of all security definitions in a single call.

## Known failure modes

- Invalid or unparseable OpenAPI/Swagger document returns an error
- Missing 'spec' field in request body returns a validation error
- Malformed JSON string that cannot be parsed returns a parse error
- Document with no security schemes returns an empty catalog
- Unsupported spec version (e.g. OpenAPI 1.x) may return an error or unexpected output

## How this service works

Resolve authentication requirements across an OpenAPI 3.x or Swagger 2.x document. Returns the catalog of security schemes (`components.securitySchemes` in OpenAPI 3, `securityDefinitions` in Swagger 2) verbatim, the document-level default, and the *effective* security for each operation after layering.

## Output

Returns the full catalog of security schemes (components.securitySchemes for OpenAPI 3 or securityDefinitions for Swagger 2) verbatim, the document-level default security requirements, and per-operation authentication overrides — giving a complete picture of the API's authentication configuration.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "spec": {
   "description": "OpenAPI/Swagger document (object or JSON string)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schemes": {
   "bearerAuth": {
    "type": "http",
    "scheme": "bearer"
   }
  },
  "summary": {
   "schemes": 1,
   "operations": 3,
   "schemeUsage": {
    "bearerAuth": 2
   },
   "openOperations": 1,
   "securedOperations": 2
  },
  "operations": [
   {
    "open": true,
    "path": "/public",
    "method": "GET",
    "security": []
   },
   {
    "open": false,
    "path": "/users",
    "method": "GET",
    "security": [
     {
      "bearerAuth": []
     }
    ]
   },
   {
    "open": false,
    "path": "/admin",
    "method": "POST",
    "security": [
     {
      "bearerAuth": [
       "admin"
      ]
     }
    ]
   }
  ],
  "globalSecurity": [
   {
    "bearerAuth": []
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openapi-security-summary-resolver-d7d5c53d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)