OpenAPI endpoint extractor · agent402.tools

Flatten an OpenAPI 3.x or Swagger 2.x spec into a structured list of…

Flatten an OpenAPI 3.x or Swagger 2.x spec into a structured list of callable endpoints - one row per operation with method, path, operationId, summary, tags, parameters (name / in / required / type), JSON-body flag, and documented response codes. Includes per-method and per-tag counts so an agent can pick what to call next without parsing the full spec. Output is sorted by path then method for stable, agent-friendly grouping. Pure CPU - deterministic, no network, no $ref dereferencing.

Ready now4 calls · 3 buyers in 30 days

Input

Request JSON

{
  "spec": {
    "openapi": "3.0.0",
    "paths": {
      "/users": {
        "get": {
          "operationId": "listUsers",
          "parameters": [
            {
              "in": "query",
              "name": "limit",
              "required": false,
              "schema": {
                "type": "integer"
              }
            }
          ],
          "responses": {
            "200": {
              "description": "ok"
            },
            "400": {
              "description": "bad"
            }
          },
          "summary": "List users",
          "tags": [
            "users"
          ]
        }
      },
      "/users/{id}": {
        "delete": {
          "operationId": "deleteUser",
          "parameters": [
            {
              "in": "path",
              "name": "id",
              "required": true,
              "schema": {
                "type": "string"
              }
            }
          ],
          "responses": {
            "204": {
              "description": "gone"
            }
          },
          "summary": "Delete user",
          "tags": [
            "users"
          ]
        }
      }
    }
  }
}

Sample response

Published by the provider. Your run returns a fresh response.

response2 keys

endpoints2 items

0{ hasJsonBody, method, operationId, … }8 keys

1{ hasJsonBody, method, operationId, … }8 keys

stats3 keys

byMethod{ DELETE, GET }2 keys

byTag{ users }1 key

total2

responseobject, 2 keys

Your agent can do this on its own

Add the MCP URL in Claude Code, Cursor or Codex. Your agent can run Tools within its spending limits, or ask for approval each time. Connect your agent

Connect your agent

Add one MCP URL and your agent can find and run this tool within its spending limits. Choose “Ask each time” if you want to approve every Call.

MCP URL

https://app.aecon.ai/mcp

Terminalbash

claude mcp add --transport http --scope user agentic-economy "https://app.aecon.ai/mcp"

In Claude Code, open /mcp, select agentic-economy, then choose Authenticate.

Track record

Paid calls, last 30 days: 4
Buyers, last 30 days: 3
Last paid call: last week

Reported by the x402 directory.

A$0.0015 per call