Duffel (YC S18)

{
  "service_type": "platform",
  "base_url": "https://duffel.com/stays",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Authorization",
    "scheme": "Bearer",
    "api_key_required": true
  },
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_trial": "likely available for developers to test",
      "transaction_fees": "likely per booking based on commission",
      "subscription": "may have monthly plans for volume"
    }
  },
  "rate_limits": {
    "unknown": true,
    "notes": "Not documented in provided description; expected for API access."
  },
  "capabilities": [
    "Search and filter accommodation inventory",
    "Book hotel and stay reservations",
    "Manage bookings and availability",
    "Integrate with travel agencies and OTAs",
    "Access to global accommodation suppliers",
    "API-driven workflow for selling accommodation",
    "Support for multiple payment methods",
    "Real-time pricing and availability"
  ],
  "raw_analysis": "Duffel is a Y Combinator-backed (S18) startup focused on travel technology, originally known for flight booking APIs, and has expanded into accommodation with Duffel Stays. The platform provides a developer-friendly API to search and book hotel rooms and other stays, aiming to simplify the integration of accommodation content for travel sellers, agencies, and software platforms. The service is designed for B2B use, targeting developers and businesses that want to offer accommodation without building direct supplier connections. Maturity is moderate but credible given YC backing and prior success in flights. Pricing is likely usage-based with fees per booking, but no explicit details are given. The API likely uses bearer token authentication and offers endpoints for property search, availability, booking, and management, though specific endpoints are not provided. Integrations with major hotel chains and wholesalers are probable but unlisted. Overall, Duffel Stays is a niche but practical platform for travel tech developers." 
}

1/3 tests passed

```json
{
  "overall": 61,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 5.0,
    "response_parseability": 8.0,
    "error_clarity": 6.0,
    "doc_quality": 6.5,
    "auth_simplicity": 7.0,
    "latency": 5.5,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "freemium",
    "free_trial": true,
    "transaction_fees": "per booking commission",
    "subscription": "volume-based plans"
  },
  "issues": [
    "No robots.txt file (404) - may indicate limited SEO or crawler access for agents",
    "No llms.txt file (404) - not optimized for LLM/agent discovery and structured access",
    "API is developer-oriented, requiring significant integration effort for first booking",
    "Pricing details are not clearly documented; transaction fees and subscription tiers are vague",
    "Site latency at 517ms is above the ideal 500ms threshold, though acceptable"
  ],
  "recommendations": [
    "Add an llms.txt file to provide structured, machine-readable documentation for AI agents",
    "Create a robots.txt that allows crawl access and lists key API endpoints for automation",
    "Provide clear, tiered pricing with exact transaction fee percentages and free-tier limits",
    "Add a quick-start guide with a working example that can complete a booking in under 5 minutes",
    "Publish an API status page and uptime SLAs to improve trust and consistency perception"
  ]
}
```