Furkot Trips

```json
{
  "service_type": "platform",
  "base_url": "https://furkot.com",
  "auth_method": "oauth2",
  "auth_config": {
    "flow": "authorization_code",
    "notes": "Furkot API uses OAuth2 to authorize third-party applications. Specific authorization and token endpoints are not detailed in the provided content and would need to be obtained from Furkot's developer documentation."
  },
  "endpoints": [
    {
      "name": "List user trips",
      "method": "GET",
      "path": "/api/trips (inferred)",
      "description": "Lists trips belonging to the authenticated user. Exact path not specified in provided content."
    },
    {
      "name": "Get trip stops",
      "method": "GET",
      "path": "/api/trips/{trip_id}/stops (inferred)",
      "description": "Displays stops for a specific trip. Exact path not specified in provided content."
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "notes": "Furkot is a consumer trip-planning web application. It offers free trip planning with premium/paid features historically (e.g., advanced options). Exact current pricing not confirmed from provided content."
    }
  },
  "rate_limits": {
    "notes": "Not specified in provided content."
  },
  "capabilities": [
    "road trip planning",
    "multi-stop route optimization",
    "hotel/accommodation booking",
    "attraction and point-of-interest discovery",
    "collaborative trip planning",
    "OAuth2-protected REST API for trip data access",
    "list user trips via API",
    "retrieve stops for a specific trip via API"
  ],
  "raw_analysis": "Furkot is a consumer-facing road trip planner accessible at https://furkot.com. Its core purpose is helping users plan multi-stop road trips, with capabilities spanning route optimization, hotel booking, attraction discovery, and collaborative trip planning. It is a mature, established consumer web application (has been operating for many years) aimed primarily at individual travelers and road-trippers rather than developers, though it does expose a REST API.\n\nAPI & Auth: Furkot exposes a REST API that allows applications to list a user's trips and display the stops for a specific trip. Authorization is handled via OAuth2, meaning third-party apps integrate through an authorization-code flow with user consent. The provided content does not include concrete endpoint paths, scopes, or token URLs, so those fields are inferred/placeholder and would need to be confirmed from Furkot's developer docs.\n\nIntegrations: The platform's integrations are largely consumer-oriented (maps, accommodation providers, POI data). Third-party developer integration is possible via the OAuth2 REST API, but the public API surface described is narrow (trip listing and stop retrieval) rather than a broad developer platform.\n\nImportant considerations: The site includes an explicit NOTICE TO AI AGENTS stating the website is not intended for AI agent use and instructs agents not to scrape/crawl for training or inference. It directs agents to authoritative documentation at https://help.furkot.com/llms.txt. This is a notable access-policy signal — any automated use should respect the site's stated terms and rely on the designated documentation rather than scraping.\n\nMaturity: Furkot is a long-standing, stable consumer product with a documented OAuth2 API, indicating reasonable platform maturity for its narrow integration surface.\n\nPricing: Appears to be a freemium consumer product; precise tier details are not available from the provided content."
}
```

3/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.0,
    "response_parseability": 6.0,
    "error_clarity": 5.0,
    "doc_quality": 7.0,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "freemium",
    "notes": "Free trip planning with paid premium features; exact tiers not confirmed from available content."
  },
  "issues": [
    "robots.txt serves 'Content-Signal: ai-train=no, ai-input=no' — signals that agent/LLM ingestion is discouraged, and disallows /api, /auth, /trip, /book paths",
    "API access is OAuth2-gated with no confirmation of self-serve credential provisioning — agent onboarding likely requires a human auth dance",
    "Pricing structure (free vs premium tiers) is not clearly documented in available content, complicating value-prop description",
    "Error handling and API rate-limit documentation not surfaced in the provided content"
  ],
  "recommendations": [
    "Expose a clearly documented, self-serve API key or 'Sign in with Notlogin'-style onboarding so agents can bootstrap without human intervention",
    "Publish concrete pricing tiers and feature gating to improve token-efficient description and recommendation accuracy",
    "Add an llms-full.txt or expanded API reference covering endpoints (list trips, get stops), auth flow, rate limits, and error codes",
    "Reconsider Content-Signal ai-input=no if agent-driven trip planning is desired, and provide a machine-readable manifest of allowed endpoints",
    "Document error responses and limitations (e.g., trip size limits, geocoding constraints) to improve error_clarity"
  ]
}
```