API Documentation Generator (from OpenAPI Spec or Plain Description)

omnial/x402-docs-generate

Given either a full OpenAPI/Swagger JSON spec or a plain-language description of a single REST endpoint, returns ready-to-use markdown API documentation (description, authentication section, per-endpoint parameter tables, request/response examples, error-code tables) plus a structured summary of every endpoint documented (HTTP method, path, one-line summary, parameter count, whether it requires authentication). Your input is sent to an outside service for processing; remove secrets and personal data first.

activeper callv4

Price

Up to $0.325 per call; you pay what the call used

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.00.

Data source

Anthropic

Generated by Anthropic's Claude from the inputs you provide.

Use it

Your AI assistant does the work: it finds this tool, shows you the price first, runs it, and you are charged when the run finishes. There is nothing to set up for this tool in particular.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

For developers: the calls your assistant makes

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/x402-docs-generate" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/x402-docs-generate" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/x402-docs-generate", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/x402-docs-generate", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.325

Updated: Oct 27, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "anyOf": [
    {
      "required": [
        "openapi_spec"
      ]
    },
    {
      "required": [
        "endpoint_description"
      ]
    }
  ],
  "properties": {
    "openapi_spec": {
      "type": "string",
      "description": "A full OpenAPI/Swagger spec as a JSON string. Provide this OR endpoint_description."
    },
    "endpoint_description": {
      "type": "string",
      "description": "A plain-language description of a single endpoint (method, path, what it does, parameters, auth). Provide this OR openapi_spec."
    }
  },
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "properties": {
    "markdown": {
      "type": "string",
      "description": "The full generated API documentation in markdown: a description, an authentication section, one subsection per documented endpoint with a parameter table, a request example, a response example, and an error-code table. Observed as a single-endpoint doc on a natural-language input and as a two-endpoint doc (sections separated by '---') on a two-path OpenAPI spec input -- length and section count scale with the number of endpoints described."
    },
    "source_type": {
      "type": "string",
      "description": "Which input field drove generation. Observed as 'natural_language' (endpoint_description was supplied) and 'openapi' (openapi_spec was supplied)."
    },
    "total_endpoints": {
      "type": "number",
      "description": "Typically equal to endpoints_documented.length."
    },
    "authentication_type": {
      "type": "string",
      "description": "Observed as 'api-key' (natural-language input describing an Authorization header) and 'none' (OpenAPI spec with no security scheme) -- other values are plausible but unconfirmed."
    },
    "endpoints_documented": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "path": {
            "type": "string",
            "description": "The endpoint's path, e.g. '/users/{id}'."
          },
          "method": {
            "type": "string",
            "description": "HTTP method, e.g. 'GET', 'POST'."
          },
          "summary": {
            "type": "string",
            "description": "One-line summary of what the endpoint does."
          },
          "requires_auth": {
            "type": "boolean"
          },
          "parameters_count": {
            "type": "number",
            "description": "Observed 1 (a path parameter) and 0 (no parameters) in testing."
          }
        },
        "additionalProperties": true
      },
      "description": "One entry per endpoint the markdown covers. Observed as a single entry for a natural-language endpoint_description input and as two entries (GET and POST on the same path) for a two-path OpenAPI spec input."
    }
  },
  "description": "The generated documentation result.",
  "additionalProperties": true
}