It Tools

{
  "service_type": "platform",
  "base_url": "https://it-tools.tech",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "description": "Free and open-source. No account or payment required. Self-hostable via Docker."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Online developer utility collection (100+ tools)",
    "Browser-based, client-side processing",
    "No account required",
    "Open source (self-hostable)",
    "PWA installable (web manifest present)",
    "Tool categories: converters, crypto/token tools, network/web tools, hashing, encoding, text, date/time, math, images, generators"
  ],
  "raw_analysis": "IT Tools (it-tools.tech) is a developer utility platform — a curated collection of 100+ single-purpose online tools (JSON formatters, hash generators, UUID/ULID generators, JWT decoders, base64/URL encoders, cron parsers, IP/cidr calculators, color converters, Lorem ipsum, etc.). It is a static Vue.js SPA: the served HTML is a shell loading `/assets/index-*.js` and does not expose any documented API surface. Processing is done client-side in the browser, so there is no server-side REST/GraphQL endpoint to programmatically call.\n\nAudience: developers, sysadmins, DevOps, and IT professionals needing quick one-off utilities without installing software. Maturity: mature and well-known in the dev community, trending on GitHub, with an active Twitter presence (@ittoolsdottech) and a documented self-hosting path (Docker image `corentinth/it-tools`). Licensing: MIT open source.\n\nAuth: none — no accounts, no tokens, no API keys.\nIntegrations: no native API or webhooks. Consumption is via the web UI, the installable PWA, or self-hosted deployment. Automation-minded users could theoretically scrape the SPA or fork the open-source repo to add their own API, but the public site does not provide one.\n\nPricing: completely free and open source.\n\nConclusion: This is a platform/tool-suite rather than an API service. It has no public programmatic interface, so any integration would be UI-driven, PWA-driven, or via self-hosting the open-source codebase."
}

3/3 tests passed

```json
{
  "overall": 74,
  "dimensions": {
    "token_efficiency": 9.0,
    "first_try_success": 9.5,
    "response_parseability": 4.0,
    "error_clarity": 7.0,
    "doc_quality": 7.0,
    "auth_simplicity": 10.0,
    "latency": 9.5,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "free",
    "free_tier": true,
    "entry_price_usd": 0,
    "self_hostable": true,
    "notes": "Fully free and open source; no account, no payment. Docker self-host option."
  },
  "issues": [
    "No API — all processing is client-side browser UI, so agents cannot programmatically call tools",
    "llms.txt request returns the HTML homepage instead of a plain-text LLM description, indicating no agent-oriented manifest",
    "No structured/machine-readable output (no JSON endpoints, no OpenAPI spec) — parseability is limited to scraping the UI",
    "robots.txt is permissive but there is no agent guidance file for programmatic use"
  ],
  "recommendations": [
    "Recommend for human-facing use: quick developer utilities with zero friction and strong privacy (client-side processing)",
    "For agent-driven workflows, avoid recommending as a tool-invocation target; instead point users to CLI equivalents or self-hostable containers",
    "If the user wants an agent-consumable utility API, suggest alternatives with JSON endpoints rather than this UI-first platform"
  ]
}
```