SYNQ Video

```json
{
  "service_type": "platform",
  "base_url": "https://synq.fm",
  "auth_method": "api_key",
  "auth_config": {
    "key_type": "developer_api_key",
    "signup_url": "https://www.synq.fm/register",
    "documentation_url": "https://www.synq.fm/",
    "notes": "API key obtained via registration at /register. Auth mechanism details (header vs query param) not specified in provided content and would require checking the SYNQ API Guide."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "No pricing information provided in the source content. SYNQ historically offered video encoding/streaming with developer-focused plans, but current pricing cannot be confirmed from supplied data."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Video encoding and transcoding (historical/assumed from SYNQ.fm branding)",
    "Developer API access via API key",
    "Developer registration and key provisioning",
    "API documentation/guide available",
    "Video hosting/CDN delivery (likely)",
    "Potential live streaming / VOD support (unconfirmed from provided content)"
  ],
  "raw_analysis": "SYNQ Video (synq.fm) is a developer-oriented video platform offering programmatic access via an API key. The two salient links in the provided content are a developer API key registration page (/register) and the SYNQ API Guide, which indicates a self-serve, developer-first onboarding model. Category is tagged as 'developer, api'. No explicit endpoints, rate limits, or pricing are exposed in the source material, so those fields are left empty or marked unknown. Auth appears to be API-key-based, consistent with typical developer video services, though the exact header/param convention would need to be confirmed in the API guide. The platform most likely provides video encoding, transcoding, hosting, and delivery capabilities typical of 'fm'-branded media services of this era, but specifics are not derivable from the given snippet. Maturity and integrations cannot be assessed from the provided content. Anyone integrating should consult the /register flow and the API guide directly to obtain a key and learn endpoint semantics, rate limits, and pricing tiers."
}
```

0/3 tests passed

{
  "overall": 28,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 2.0,
    "response_parseability": 3.0,
    "error_clarity": 2.0,
    "doc_quality": 2.0,
    "auth_simplicity": 3.0,
    "latency": 1.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information retrievable from source content; cannot normalize."
  },
  "issues": [
    "All three checks (website uptime, robots.txt, llms.txt) returned null status codes with ~30s timeouts — platform appears unreachable or non-responsive.",
    "No pricing data provided — agents cannot advise users on cost.",
    "No verifiable feature set; capabilities are inferred from historical SYNQ.fm branding, not confirmed.",
    "No llms.txt means poor agent-discovery/ingestion surface.",
    "No security headers detected and no working HTTP response — reliability is unknown at best.",
    "Latency exceeds 30 seconds per request — unusable for agent-driven workflows."
  ],
  "recommendations": [
    "Verify the domain is live and returns HTTP 200 before recommending to users.",
    "Publish an llms.txt and clear robots.txt to support agent ingestion.",
    "Surface a public pricing page with structured, machine-readable tiers.",
    "Provide stable uptime metrics and a status page to establish consistency.",
    "Ensure API docs are accessible without JS-gated SPA rendering so agents can parse them.",
    "Do not recommend this platform to users until basic reachability and documentation are confirmed."
  ]
}