New York Times

{
  "service_type": "platform",
  "base_url": "https://developer.nytimes.com",
  "auth_method": "api_key",
  "auth_config": {
    "api_key": {
      "description": "API key required for most endpoints, typically passed as query parameter 'api-key'"
    }
  },
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Most APIs have a free tier with limited requests per day (e.g., 500 requests/day for Article Search)",
      "paid_tiers": "Higher rate limits available for enterprise customers",
      "notes": "Some APIs may require approval or have separate pricing"
    }
  },
  "rate_limits": {
    "default": "500 requests per day per API",
    "article_search": "500 requests/day",
    "top_stories": "500 requests/day",
    "movie_reviews": "500 requests/day"
  },
  "capabilities": [
    "News article search and retrieval",
    "Top story access",
    "Movie reviews",
    "Semantic API for discovery",
    "TimesTags API for tag-based querying",
    "Geographic API for geo-located articles",
    "Archive API for historical articles",
    "Most Popular API for trending content",
    "Books API for book reviews and lists",
    "School and news event APIs",
    "All APIs typically return JSON data"
  ],
  "raw_analysis": "The New York Times Developer Network provides RESTful APIs for accessing NYT content. It is a well-established platform (since 2010) targeting journalists, researchers, developers, and digital publishers. The platform offers a variety of APIs including Article Search (full-text query), Top Stories, Most Popular, Archive, and specialized APIs like Movie Reviews and Books. Authentication is via API key, which can be obtained after registration. Rate limits are per-day based (500 requests/day for most free tiers), with higher limits through enterprise agreements. The system is mature with extensive documentation and examples. The HTML page shows a modern JavaScript SPA (Angular-based) with no server-side rendered content, indicating a developer portal that requires JavaScript for full functionality. There is no direct REST endpoint listing discernible from the HTML, but the main entry points are typically at \"/svc\" subdomains (e.g., api.nytimes.com/svc/...). Integration options include SDKs for various languages, and the platform is suitable for those needing authoritative news data. Pricing is freemium, with free tiers sufficient for prototyping and small-scale use."
}

3/3 tests passed

```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.0,
    "response_parseability": 9.0,
    "error_clarity": 6.5,
    "doc_quality": 7.5,
    "auth_simplicity": 6.0,
    "latency": 8.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "free_tier_requests_per_day": 500,
    "enterprise_pricing_available": true
  },
  "issues": [
    "Some APIs may require separate approval or have distinct pricing models, creating friction for quick adoption",
    "Documentation appears HTML-based without a dedicated llms.txt file — agents may need to parse traditional docs pages",
    "Rate limits (500/day) may be restrictive for high-volume agent use cases"
  ],
  "recommendations": [
    "Add an llms.txt file with concise API summaries and structured endpoint definitions for agent-friendly parsing",
    "Clarify approval requirements and pricing for each API endpoint in a single unified pricing table",
    "Consider increasing default free tier limits to reduce iteration friction during agent testing"
  ]
}
```