Poemist API

{
  "service_type": "platform",
  "base_url": "https://www.poemist.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/api/randompoems",
      "method": "GET",
      "description": "Returns a random poem from the Poemist collection. Likely returns JSON with poem text, title, and author.",
      "parameters": []
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "No visible pricing. The API appears to be freely accessible without authentication. Likely a small hobbyist service."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Random poem retrieval",
    "Poetry content delivery",
    "Potential search or filtering (unconfirmed)",
    "JSON response format"
  ],
  "raw_analysis": "Poemist is a small, lightweight web service that provides a public API for retrieving random poems. It appears to be a hobbyist or side project rather than a mature commercial platform, with no visible pricing, authentication, or documentation. The API is likely free to use and returns JSON data. There is no evidence of official SDKs, OAuth, rate limiting policies, or enterprise features. The platform is aimed at developers who need a simple source of random poem content for applications, bots, or demos. Integration is straightforward via HTTP GET requests. The overall maturity is low, and the service may be unreliable or subject to changes without notice. No public API keys are required based on available information."
}

2/3 tests passed

```json
{
  "overall": 46,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 6.5,
    "response_parseability": 6.0,
    "error_clarity": 3.0,
    "doc_quality": 3.0,
    "auth_simplicity": 9.0,
    "latency": 8.0,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "No visible pricing; appears freely accessible without authentication. Likely a small hobbyist service — sustainability and future availability are uncertain."
  },
  "issues": [
    "No llms.txt (404) — no machine-readable guidance for agents to understand or use the platform.",
    "No security headers detected on any endpoint; unclear production hardening.",
    "Docs, error clarity, and limitation disclosures appear minimal or absent — 'potential search or filtering' is unconfirmed, signaling undocumented capability surface.",
    "Response format is 'JSON' supposed, but no documented schema, versioning, or error contract is evident.",
    "Aggressive bot blocking in robots.txt (Semrush, Ahrefs, MJ12) — indicates a small operator, and consistency/uptime stability is unproven.",
    "Latency ~565ms on root is borderline; fine for humans but adds up for agent loops.",
    "No auth path implies no rate-limit or quota documentation — risk of silent throttling."
  ],
  "recommendations": [
    "Publish an llms.txt and/or OpenAPI spec describing the poem endpoint, params, and JSON schema — biggest single upgrade for agent-friendliness.",
    "Document error responses (status codes, error body shape) so agents can self-correct instead of guessing.",
    "Add a clear feature list: does it support search? filter by author/genre/length? This resolves the biggest ambiguity in the current capability set.",
    "Add basic security headers and a status page so consistency and reliability can be assessed.",
    "If possible, expose a documented rate limit (even generous) to prevent agents from accidentally triggering blocks.",
    "Consider the platform's sustainability story — 'free, no auth, hobbyist' is great for onboarding but a risk for anything in an agent's long-term toolkit."
  ]
}
```