Twitter API

{
  "service_type": "platform",
  "base_url": "https://dev.twitter.com",
  "auth_method": "oauth",
  "auth_config": {
    "oauth_versions": ["1.0a", "2.0"],
    "auth_types": ["user_context", "app_only", "bearer_token"],
    "key_management": "Twitter Developer Portal"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Basic access with limited calls (v2)",
      "paid_tiers": ["Basic", "Pro", "Enterprise"],
      "legacy": "Legacy v1.1 endpoints being deprecated"
    }
  },
  "rate_limits": {
    "free": "15 requests per 15 minutes per endpoint (varies)",
    "basic": "Higher limits",
    "pro": "Even higher",
    "enterprise": "Custom"
  },
  "capabilities": [
    "post_tweets",
    "read_tweets",
    "user_lookup",
    "followers_management",
    "direct_messages",
    "search_tweets",
    "streaming_api",
    "ads_api"
  ],
  "raw_analysis": "Twitter API (now X API) is a platform for programmatic access to Twitter/X data and functionality. It's used by developers, researchers, and businesses to build apps, analyze trends, automate posting, and integrate social features. The platform has evolved from the legacy v1.1 (dev.twitter.com) to the X API v2 (developer.x.com). Maturity is high, but the platform has undergone significant changes in pricing and access, moving from largely free to a tiered subscription model with strict rate limits. Integrations include numerous third-party libraries (e.g., Tweepy, Twitter4J, twurl) and official SDKs for Python, Java, Ruby, etc. The API supports OAuth 1.0a and 2.0 for authentication. Legacy v1.1 endpoints are being deprecated in favor of v2. The service is widely recognized but has faced criticism for high costs and reduced free access."
}

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 5.0,
    "response_parseability": 8.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "free_tier": "Basic access with limited calls (v2)",
    "paid_tiers": ["Basic", "Pro", "Enterprise"],
    "legacy_v1.1": "deprecated"
  },
  "issues": [
    "No llms.txt — agents cannot discover capabilities programmatically; llms_txt check returned 404",
    "Pricing tiers (Basic/Pro/Enterprise) have opaque, high-threshold dollar amounts historically ($100/$5000+/mo) that are painful to communicate as a value prop",
    "Onboarding requires developer account application + review; not self-serve-in-minutes",
    "v1.1 to v2 migration churn creates doc and endpoint inconsistency",
    "OAuth 2.0 with PKCE / OAuth 1.0a adds auth friction vs magic-link platforms",
    "Free tier rate limits are aggressive, causing first-try failures for agent prototypes"
  ],
  "recommendations": [
    "Ship llms.txt describing v2 endpoints, auth flows, and rate limits so agents can parse capabilities without scraping docs",
    "Publish clear, public, machine-readable pricing table with call quotas per tier",
    "Offer a self-serve sandbox or trial key with generous rate limits to improve first-try success",
    "Provide an OpenAPI spec and typed SDKs to strengthen structured-data story",
    "Consolidate v1.1 deprecation messaging into a single, dated migration guide with examples",
    "Expose a status/health endpoint in docs to reinforce reliability perception"
  ]
}