Hubhopper Partner Integration API(s) - Production

{
  "service_type": "platform",
  "base_url": "https://hubhopper.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "x-api-key",
    "notes": "API key is provided to partners and passed via the x-api-key header. Exact key provisioning flow is not publicly documented."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Hubhopper offers a free consumer podcast app plus creator monetization/hosting plans. Partner API pricing is not publicly listed and appears to be negotiated."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "podcast discovery and catalog access",
    "podcast metadata retrieval",
    "data fetching for partner integrations",
    "API key authenticated access",
    "interactive API documentation/testing"
  ],
  "raw_analysis": "Hubhopper is an India-based podcast platform that operates as both a consumer podcast discovery/listening app and a podcast hosting, distribution, and monetization service for creators. The service described here is a partner-facing integration API (Production) exposed at https://hubhopper.com and documented via an interactive doc where partners supply an API key in the x-api-key header to authorize requests and test endpoints.\n\nWhat the platform does: Provides podcast content, metadata, and distribution data. The Partner Integration API appears intended to let third-party partners fetch Hubhopper data (e.g., catalog, shows, episodes, or analytics) programmatically.\n\nWho it's for: Podcast creators, publishers, and third-party partners (apps, analytics tools, distributors) seeking to integrate with Hubhopper's podcast ecosystem.\n\nMaturity: Hubhopper is an established Indian podcast platform but not a top-tier global player. Its developer/partner API surface is not broadly documented publicly — access appears gated behind partner agreements and provisioning of API keys, which suggests a private or semi-private integration rather than an open public developer platform.\n\nIntegrations: No public REST API documentation, endpoint list, rate limits, or SDKs are exposed in the provided material. The description indicates an interactive doc where the API key is tested, but the actual endpoint definitions were not included in the input.\n\nCaveats: Because the source content is truncated and endpoint details are absent, base_url, auth method, and capabilities are inferred. Rate limits, endpoint paths, and response schemas should be confirmed directly from the partner documentation or by contacting Hubhopper. The provided data does not confirm whether the API is read-only (fetching data) or supports writes."
}

2/3 tests passed

{
  "overall": 48,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 3.0,
    "response_parseability": 5.0,
    "error_clarity": 3.0,
    "doc_quality": 3.0,
    "auth_simplicity": 4.0,
    "latency": 9.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "type": "custom_enterprise",
    "free_tier": false,
    "self_serve": false,
    "public_pricing": false,
    "notes": "Consumer app is free; creator plans have tiers. Partner API pricing is negotiated/undisclosed — a blocker for agent-driven adoption."
  },
  "issues": [
    "No public API pricing — agents cannot quote or compare costs; requires human sales negotiation.",
    "No LLM-readable doc file (llms.txt returns 404), so agents cannot quickly ingest capability surface.",
    "API endpoints (/api/) are blocked in robots.txt, signaling closed/proprietary access.",
    "Docs are not surfaced in checks; getting-started path for the partner API is unclear from public web.",
    "No visible SSO/magic-link; API key flow appears gated behind partner approval.",
    "No security headers present on responses (minor trust signal)."
  ],
  "recommendations": [
    "Publish a public API pricing tier (even a usage-based free tier) so agents can size cost before recommending.",
    "Ship an llms.txt / agent-friendly capability manifest summarizing endpoints, auth, rate limits, and example calls.",
    "Provide instant self-serve API key issuance (or 'Sign in with Notlogin'-style verified identity onboarding) instead of manual partner onboarding.",
    "Surface OpenAPI/Swagger with example requests/responses on a crawlable page (allowlist /docs in robots.txt).",
    "Add a status page link and uptime SLA to the docs to increase reliability confidence for agent recommendations.",
    "Clarify in docs the difference between consumer, creator, and partner-API tiers so agents can route the right users."
  ]
}