Article Rewriter and Article Extractor API

{
  "service_type": "platform",
  "base_url": "https://spinbot.net",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "notes": "Spinbot offers a free web-based article spinner/rewriter with character limits; API access is not publicly documented and may require contacting the vendor for pricing."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Article rewriting (spinning) via web interface",
    "Article extraction",
    "Paraphrasing text",
    "Content generation for SEO/marketing use"
  ],
  "raw_analysis": "Spinbot.net is a long-standing web-based SaaS tool primarily used for article spinning/rewriting, paraphrasing, and article extraction. It targets content marketers, SEO professionals, students, and bloggers who need to quickly generate unique variants of existing text. The platform is mature and widely known in the SEO community, though its output quality is often criticized as mechanical.\n\nRegarding API access: Spinbot does not advertise a public REST API on its site, nor does it publish API documentation, authentication methods, or endpoint details. The primary interface is a web form where users paste text and receive a rewritten result. There is no evident OAuth, API key, or token-based auth scheme exposed. Some third-party services have historically attempted to wrap Spinbot via scraping, but there is no official API product visible. Any integration would likely require reaching out to the operator directly.\n\nPricing appears to be freemium: the web tool is free with character limits (commonly cited as ~10,000 characters per submission), and no public paid API tier is listed. Rate limits are not documented.\n\nOverall, Spinbot should be treated as a web tool with no confirmed public API. If an API is needed, direct vendor contact is the only viable path, and reliability/legal status of unofficial wrappers is questionable."
}

2/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 8.0,
    "response_parseability": 2.0,
    "error_clarity": 3.0,
    "doc_quality": 5.0,
    "auth_simplicity": 7.0,
    "latency": 9.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "freemium",
    "free_tier": true,
    "api_publicly_documented": false,
    "notes": "Web-based spinner with free tier and character limits; API access not publicly documented, likely requires contacting vendor."
  },
  "issues": [
    "No public API — agents cannot programmatically invoke rewriting; only a web UI exists.",
    "No llms.txt (404), so no machine-readable agent/LLM guidance or structured capability manifest.",
    "Website responses lack security headers, a mild trust/safety signal.",
    "Documentation of API, rate limits, and programmatic access is absent.",
    "No structured data output (JSON/XML) surfaced; results are HTML UI only."
  ],
  "recommendations": [
    "Provide a documented REST API with token auth, JSON input/output, and clear rate limits — this is the single biggest lever for agent usability.",
    "Publish an llms.txt describing capabilities, endpoints, and constraints for agent consumption.",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to build trust signals.",
    "Offer machine-readable pricing and quota data instead of 'contact vendor'.",
    "Expose a simple magic-link/SSO onboarding for API keys so agents can bootstrap without human steps."
  ]
}