Zappiti Player API

{
  "service_type": "platform",
  "base_url": "http://your-player-ip:8990/",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Local network media player control",
    "HTTP-based API on port 8990",
    "Device-local REST-like interface"
  ],
  "raw_analysis": "The requested URL (zappiti.com) does not currently host a Zappiti Player API landing page. The fetched HTML is a HugeDomains domain-for-sale parking page showing ZapPiti.com listed at $9,795 (or $408.13/mo for 24 months). There is no API documentation, OpenAPI spec, or endpoint list present.\n\nThe description indicates that the Zappiti Player API is a device-local API served by a Zappiti media player itself, using the base URL http://your-player-ip:8990/. This implies:\n- The API is not a hosted cloud service; it runs on the user's local network on the player device.\n- No public REST API is exposed on the internet for this service via zappiti.com.\n- Auth appears to be 'none' based on the description (requests go directly to the player IP without mention of keys/tokens), though Zappiti players may have LAN-only access assumptions.\n\nBecause the public site is a domain-sale page rather than an API portal, no endpoints, rate limits, or pricing can be extracted. The Zappiti brand (a French media player/streamer manufacturer) has had trademark/service continuity issues, and the domain appears to have lapsed or been parked. Capabilities listed are inferred generically for a local media-player HTTP API (playback control, library browsing, remote commands), but cannot be verified from the provided content. Integrators should treat this as an undocumented, on-device API and test against an actual Zappiti player on port 8990."
}

0/3 tests passed

{
  "overall": 32,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 2.0,
    "response_parseability": 4.0,
    "error_clarity": 2.0,
    "doc_quality": 1.0,
    "auth_simplicity": 4.0,
    "latency": 8.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing page reachable; likely a free/local device, but unverifiable from public sources."
  },
  "issues": [
    "No public website, robots.txt, or llms.txt resolvable — DNS lookup fails, so zero online discoverability for agents.",
    "No documentation surfaced anywhere; agents cannot learn endpoints, auth model, or payload shapes.",
    "Unknown pricing and licensing model — cannot advise users on cost.",
    "Authentication story for the local HTTP API (port 8990) is undocumented.",
    "No status page or uptime signal to assess reliability.",
    "Value proposition is vague: 'local network media player control' without a named product, SDK, or protocol."
  ],
  "recommendations": [
    "Publish a minimal static site with a getting-started guide, API reference, and example requests.",
    "Ship an OpenAPI/Swagger spec for the port 8990 HTTP interface so agents can auto-discover endpoints.",
    "Add /llms.txt and /robots.txt so agent crawlers can index capabilities.",
    "Document auth model explicitly (token, PIN, unauthenticated LAN-only, etc.) and list any required pairing steps.",
    "Publish device discovery protocol (mDNS, SSDP, or fixed hostname) so agents can find instances on a LAN.",
    "Clarify pricing/licensing (open source, freemium, one-time purchase) so agents can recommend accurately.",
    "Expose a /status or /health endpoint with version info to support reliability checks."
  ]
}