AstroWay API Docs

AstroWay API documentation search and endpoint lookup with credit prices. No API key needed.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~729Tokens (tool definitions)
~1.1 KBTypical response size
Moderate attention impact (0.57% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "docs": {
      "url": "https://mcp.astroway.info/mcp/docs"
    }
  }
}

Remote endpoints

https://mcp.astroway.info/mcp/docsstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_docs(query, lang, limit)

Search the AstroWay guides: authentication, credits, error codes, field formats, agent setup and every product page. Returns title, URL, section list and the argument to pass to read_doc. No API key needed. For "which endpoint do I call" use find_endpoint instead, which also gives the price.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "What you want to know, e.g. \"rate limits\", \"timezone format\", \"webhook signature\"."
    },
    "lang": {
      "description": "Page language. Default \"any\"; the guides are written in Ukrainian and mirrored in English.",
      "type": "string",
      "enum": [
        "uk",
        "en",
        "any"
      ]
    },
    "limit": {
      "description": "How many pages to return, 1 to 25. Default 5.",
      "type": "integer",
      "minimum": 1,
      "maximum": 25
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_endpoint(query, keyless_only, limit)

Find endpoints by subject and get, for each, the method, the URL, the credit cost, the required body fields and a link to its reference page. Covers all 770 operations. No API key needed, so you can price a workflow before you have one.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "Subject or path fragment, e.g. \"natal chart\", \"bazi\", \"solar return\", \"/transits\"."
    },
    "keyless_only": {
      "description": "Only endpoints that answer without a key. Default false.",
      "type": "boolean"
    },
    "limit": {
      "description": "How many endpoints to return, 1 to 25. Default 8.",
      "type": "integer",
      "minimum": 1,
      "maximum": 25
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢read_doc(url)

Fetch one guide as markdown. Takes the `url` that search_docs printed, for example "/api-conventions/". Only pages in the index can be read.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "minLength": 1,
      "description": "Page path as search_docs printed it, e.g. \"/credits/\" or \"/en/errors/\"."
    }
  },
  "required": [
    "url"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_docs(lang)

The whole guide index grouped by section, so you can see what exists before searching for it. Pair with find_endpoint for the API reference, which is listed by subject rather than here.

Input Schema

{
  "type": "object",
  "properties": {
    "lang": {
      "description": "Page language. Default \"uk\", which is where the guides are written.",
      "type": "string",
      "enum": [
        "uk",
        "en",
        "any"
      ]
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools