Telegraph

{
  "service_type": "platform",
  "base_url": "https://telegra.ph",
  "auth_method": "token",
  "auth_config": {
    "token": "optional, for authenticated access"
  },
  "endpoints": [
    {
      "path": "/api/createAccount",
      "method": "POST",
      "description": "Create a Telegraph account (returns access token)"
    },
    {
      "path": "/api/createPage",
      "method": "POST",
      "description": "Create a new Telegraph page (blog post)"
    },
    {
      "path": "/api/getPage",
      "method": "GET",
      "description": "Fetch a single page content"
    },
    {
      "path": "/api/getPageList",
      "method": "GET",
      "description": "Get list of pages for a specific account"
    },
    {
      "path": "/api/editPage",
      "method": "POST",
      "description": "Edit an existing page"
    },
    {
      "path": "/api/getViews",
      "method": "GET",
      "description": "Get number of views for a page"
    },
    {
      "path": "/api/revokeAccessToken",
      "method": "POST",
      "description": "Revoke an existing access token"
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "usage": "Completely free to use for hosting blogs and pages. No paid tiers or subscription fees."
    }
  },
  "rate_limits": {
    "limits": "No explicit rate limits documented, but there may be practical limits. Recommended to make requests at reasonable intervals. Limits may apply to login/creation and view counting."
  },
  "capabilities": [
    "Create and host anonymous blogs/pages",
    "Markdown-like formatting through Node content",
    "RESTful API for creating, editing, fetching pages",
    "Token-based authentication for managing own content",
    "Simple page structure with title, author, content",
    "Return content in HTML or Node format",
    "View counting for pages",
    "Media embedding through URLs (images, videos, etc.)",
    "Short URL generation for pages"
  ],
  "raw_analysis": "Telegraph is a minimalistic blogging platform by Telegram (the messaging app creator). It allows users to create and share posts (called 'pages') anonymously or with an optional account. The platform is built for simplicity—its API is straightforward and well-documented, allowing developers to programmatically create, retrieve, edit, and measure posts. No database setup or static site generation is required for basic usage. It uses a token-based authentication system that is optional for public viewing but required for managing your own pages. The content format is a JSON-based node tree (similar to Telegram's Bot API), which gives flexibility in structuring text, images, videos, and embedded content. It's widely used for publishing articles, guides, and ephemeral content without any hosting overhead. The platform is fully free, with no pricing tiers or rate limit documentation, though heavy usage may be subject to fair-use policies. Integrations are limited to HTTP REST calls, but it's popular for automated content distribution from bots and scripts. Maturity: The API has been stable for years and is reliable, though feature set is intentionally minimal (no comments, likes, search, or custom domains). Ideal for developers looking for a simple content publishing endpoint, or for Telegram bot developers who need to create rich shared content. It lacks typical CMS features like tags, categories, or user management beyond single account tokens. Overall, it's a robust and reliable free tool for quick publishing and sharing."
}

1/3 tests passed

```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 8.0,
    "response_parseability": 6.0,
    "error_clarity": 5.5,
    "doc_quality": 7.0,
    "auth_simplicity": 8.5,
    "latency": 8.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "free",
    "note": "Completely free with no tiers or subscription fees; very agent-friendly for cost estimation."
  },
  "issues": [
    "No robots.txt or llms.txt files (404s) — hinders agent discovery and structured documentation access.",
    "No structured API schema or OpenAPI spec visible in initial checks; requires manual endpoint discovery.",
    "Limited error documentation — no explicit error code references found in public materials.",
    "No rate limit documentation — agents may encounter unannounced throttling.",
    "Missing content format specification beyond HTML/Node — parsing requires trial and error."
  ],
  "recommendations": [
    "Add an llms.txt or /llms.txt endpoint with API schema, endpoint descriptions, and example requests/responses.",
    "Provide a machine-readable OpenAPI/Swagger specification for direct agent parsing.",
    "Document rate limits, error codes, and response header semantics explicitly in a dedicated API guide.",
    "Publish a robots.txt that allows agent access and lists key API paths.",
    "Add structured examples for Node format and media embedding to reduce integration trial-and-error."
  ]
}
```