# OpenAPI/Swagger Spec Summarizer

> OpenAPI/Swagger Spec Summarizer is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-10).

Fetches an OpenAPI/Swagger spec (JSON or YAML) from a URL and returns a structured summary including title, version, servers, authentication schemes, and all endpoints with method, path, summary, and required parameters.

## Facts

- Endpoint: POST https://api.vextorium.com/openapi-resumen-pago?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/openapi-swagger-spec-summarizer-f8a1c38e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r435FeWaULxkYDsGYcPCC

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-swagger-spec-summarizer-f8a1c38e -d '<json body>'
```

Example prompt: Can you fetch the OpenAPI spec at https://petstore3.swagger.io/api/v3/openapi.json and give me a summary of all its endpoints, what authentication it uses, and the server URLs?

## When to prefer this

Use this endpoint when you need a machine-readable, agent-friendly summary of any OpenAPI or Swagger spec without writing your own parser. It is ideal for API discovery workflows, pre-integration audits, building dynamic API clients, or when an agent needs to understand what routes an unfamiliar API exposes before deciding which to call.

## Known failure modes

- URL is unreachable or returns non-2xx HTTP status — spec cannot be fetched
- URL points to an HTML page or non-spec content instead of JSON/YAML — parsing fails
- Malformed or invalid OpenAPI/Swagger document — incomplete or empty summary returned
- Rate limiting or authentication required on the spec URL — fetch blocked
- Very large spec with many endpoints may be truncated if 'limite' parameter is not set high enough

## How this service works

Fetch an OpenAPI/Swagger spec (JSON or YAML) and summarize it for an agent: title, version, servers, authentication schemes and every endpoint with method, path, summary and required parameters.

## Output

Returns a JSON object with: API title, OpenAPI version string, list of server base URLs, authentication schemes (type and location), total endpoint count, and an array of endpoints each containing an ID, route path, HTTP method, summary description, tags, whether a request body is required, whether it is deprecated, and list of required parameters.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string"
      },
      "limite": {
       "type": "integer"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": [
      "object",
      "null"
     ],
     "properties": {
      "titulo": {
       "type": [
        "string",
        "null"
       ]
      },
      "openapi": {
       "type": [
        "string",
        "null"
       ]
      },
      "endpoints": {
       "type": [
        "array",
        "null"
       ],
       "items": {
        "type": [
         "null",
         "object"
        ],
        "properties": {
         "id": {
          "type": [
           "null",
           "string"
          ]
         },
         "ruta": {
          "type": [
           "null",
           "string"
          ]
         },
         "cuerpo": {
          "type": [
           "boolean",
           "null"
          ]
         },
         "metodo": {
          "type": [
           "null",
           "string"
          ]
         },
         "resumen": {
          "type": [
           "null",
           "string"
          ]
         },
         "obsoleto": {
          "type": [
           "boolean",
           "null"
          ]
         },
         "etiquetas": {
          "type": [
           "array",
           "null"
          ],
          "items": {
           "type": [
            "null",
            "string"
           ]
          }
         },
         "obligatorios": {
          "type": [
           "array",
           "null"
          ],
          "items": {}
         }
        }
       }
      },
      "servidores": {
       "type": [
        "array",
        "null"
       ],
       "items": {
        "type": [
         "null",
         "string"
        ]
       }
    
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "titulo": "Swagger Petstore - OpenAPI 3.0",
  "openapi": "3.0.4",
  "endpoints": [
   {
    "id": "updatePet",
    "ruta": "/pet",
    "cuerpo": true,
    "metodo": "PUT",
    "resumen": "Update an existing pet.",
    "obsoleto": false,
    "etiquetas": [
     "pet"
    ],
    "obligatorios": []
   },
   {
    "id": "addPet",
    "ruta": "/pet",
    "cuerpo": true,
    "metodo": "POST",
    "resumen": "Add a new pet to the store.",
    "obsoleto": false,
    "etiquetas": [
     "pet"
    ],
    "obligatorios": []
   }
  ],
  "servidores": [
   "/api/v3"
  ],
  "descripcion": "This is a sample Pet Store Server based on the OpenAPI 3.0 specification.  You can find out more about\nSwagger at [https://swagger.io](https://swagger.io). In the third iteration of the pet store, we've switched to the design first approach!\nYou can now help us improve the API whether it's by making…",
  "version_api": "1.0.27",
  "autenticacion": {
   "api_key": "apiKey (header)",
   "petstore_auth": "oauth2"
  },
  "endpoints_total": 19
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openapi-swagger-spec-summarizer-f8a1c38e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)