# OpenAPI Spec Summary: Operations, Auth and Servers > OpenAPI Spec Summary: Operations, Auth and Servers is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-25). Fetches and summarizes an OpenAPI 3 or Swagger 2 document from a URL, returning title, version, servers, auth schemes, operation counts, tags, and up to 150 operations with their metadata. ## Facts - Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/openapi/summary?utm_source=zero.xyz - Price: $0.01/call - Payment: x402 - Status: unknown - Last checked: 2026-10-25 - Activations on Zero: 0 - Provider: agent-data-tools.revmesh2074.workers.dev - Website: https://agent-data-tools.revmesh2074.workers.dev - Tags: x402 - Canonical page: https://www.zero.xyz/c/agent-data-tools-revmesh2074-workers-dev-openapi-spec-summary-20b07210 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eNUDD2SWecYOsPFA3xlnT 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 agent-data-tools-revmesh2074-workers-dev-openapi-spec-summary-20b07210 ``` Example prompt: Can you summarize the OpenAPI spec at https://petstore3.swagger.io/api/v3/openapi.json — I want to know what endpoints it has, what auth it requires, and which operations might be paid or deprecated? ## When to prefer this Use this endpoint when an AI agent needs to understand an unfamiliar API before calling it, select the right endpoint from a large spec, or quickly compare two APIs. It is the right choice when you have an OpenAPI 3 or Swagger 2 document URL and need structured metadata about its capabilities, auth, and operations — especially before making live API calls. Prefer it over reading raw spec files directly since it normalizes both JSON and YAML formats and highlights paid and deprecated operations automatically. ## Known failure modes - URL is not reachable or returns non-200 — fetch fails with an error - Document exceeds 2 MB limit — rejected with size error - URL points to a non-OpenAPI/Swagger document — parse error returned - Invalid or malformed YAML/JSON — parse error returned - More than 150 operations — list is truncated and truncated flag is set to true ## How this service works OpenAPI spec summary. Read an OpenAPI 3 or Swagger 2 document (JSON or YAML, up to 2 MB) from a URL and summarise it for an agent: title, version, description, servers, auth schemes, operation count by method, tags, which operations are paid (402 or x-payment-info) or deprecated, and up to 150 operations with method, path, summary and operationId. Use before calling an unfamiliar API, to pick an endpoint, or to compare APIs. ## Output Returns a structured JSON object with the API title, version, description, server URLs, auth schemes (type, location, name), operation count broken down by HTTP method, all tag names, total paid and deprecated operation counts, and a list of up to 150 operations each with method, path, summary, operationId, and flags for paid and deprecated status. Also indicates whether the operation list was truncated. ## 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" ], "properties": { "type": { "type": "string", "const": "http" }, "method": { "enum": [ "GET" ], "type": "string" }, "queryParams": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "examples": [ "https://petstore3.swagger.io/api/v3/openapi.json" ], "description": "URL of the OpenAPI or Swagger document" } } } }, "additionalProperties": false }, "output": { "type": "object", "required": [ "type" ], "properties": { "type": { "type": "string" }, "example": { "type": "object", "properties": { "url": { "type": "string" }, "auth": { "type": "array", "items": { "type": "object", "properties": { "in": {}, "name": { "type": "string" }, "type": { "type": "string" }, "scheme": {} } } }, "tags": { "type": "array", "items": { "type": "string" } }, "title": { "type": "string" }, "format": { "type": "string" }, "servers": { "type": "array", "items": { "type": "string" } }, "version": { "type": "string" }, "byMethod": { "type": "object", "properties": { "GET": { "type": "number" }, "POST": { "type": "number" } } }, "truncated": { "type": "boolean" }, "operations": { "type": "array", "items": { "type": "object", "properties": { "paid": { "type": "boolean" }, "path": { "type": "string" }, "method": { "type": "string" }, "summary": { "type": "string" }, "deprecated": { "type": "boolean" }, "operationId": { "type": "string" } } } }, "description": { "type": "string" }, "operationCount": { "type": "number" }, … (truncated) ``` ## Response schema (JSON Schema) ```json { "type": "json", "example": { "url": "https://petstore3.swagger.io/api/v3/openapi.json", "auth": [ { "in": null, "name": "petstore_auth", "type": "oauth2", "scheme": null } ], "tags": [ "pet", "store", "user" ], "title": "Swagger Petstore - OpenAPI 3.0", "format": "OpenAPI 3.0.4", "servers": [ "/api/v3" ], "version": "1.0.27", "byMethod": { "GET": 8, "POST": 5 }, "truncated": false, "operations": [ { "paid": false, "path": "/pet", "method": "PUT", "summary": "Update an existing pet.", "deprecated": false, "operationId": "updatePet" } ], "description": "This is a sample Pet Store Server…", "operationCount": 19, "paidOperations": 0, "deprecatedOperations": 0 } } ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-data-tools-revmesh2074-workers-dev-openapi-spec-summary-20b07210/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from agent-data-tools.revmesh2074.workers.dev](https://www.zero.xyz/host/agent-data-tools.revmesh2074.workers.dev/llms.txt)