Active Documentation for /v1

{
  "service_type": "platform",
  "base_url": "https://idtbeyond.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "RESTful API",
    "HTTPS/TLS secured transport",
    "Standard HTTP methods",
    "Active/interactive documentation",
    "Sandbox account testing",
    "Query response inspection"
  ],
  "raw_analysis": "IDT Beyond (idtbeyond.com) presents a RESTful API surface documented via an 'Active Documentation' page hosted under a /v1 versioned path. The description indicates the docs are interactive — users can test their account and observe live responses to queries, which is characteristic of an API explorer (e.g., Swagger/OpenAPI UI or a similar self-service developer console).\n\nService nature: The platform is API-first and targets developers integrating programmatic services. The mention of 'your account' implies account-based authentication, but the auth scheme (API key, OAuth, Bearer token) is not disclosed in the provided content. No explicit endpoints, payload schemas, or example calls were included, so the endpoint list is empty.\n\nTransport & conventions: Standard HTTP methods over HTTPS/TLS, REST architecture, and versioned base path (/v1) — indicating a mature, conventional API design appropriate for production integration.\n\nMaturity signals: Versioned API (v1) plus interactive documentation suggest a reasonably mature developer platform rather than an early prototype. However, absence of public pricing, rate-limit figures, and endpoint specifications in the supplied text limits deeper assessment.\n\nIntegrations: No explicit SDKs, webhooks, or third-party integration listings were provided. Integration surface is inferred to be HTTP-based developer integration only.\n\nPricing: Not stated. IDT Beyond is a communications/fintech-adjacent brand (IDT Corporation), and such platforms typically operate per-usage or contract pricing, but there is insufficient evidence here to classify it.\n\nGaps to resolve: authentication method, endpoint catalog, rate limits, pricing model, availability of sandbox vs. production credentials, and any SDK or webhook support. These would require fetching the actual /v1 active documentation page, which likely requires an account login and thus may not be publicly scrapeable."
}

0/3 tests passed

{
  "overall": 22,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 2.0,
    "response_parseability": 4.0,
    "error_clarity": 2.0,
    "doc_quality": 2.0,
    "auth_simplicity": 3.0,
    "latency": 8.0,
    "consistency": 1.0
  },
  "pricing_normalized": {},
  "issues": [
    "All three check endpoints failed with DNS resolution errors ('Name or service not known'), indicating the platform's domain does not resolve or is unreachable.",
    "No website uptime data could be collected — /robots.txt, /llms.txt, and homepage all failed, meaning agents have no discoverable surface to onboard or verify.",
    "No pricing information is available; pricing_model is 'unknown' with empty details.",
    "Documentation quality cannot be assessed since no docs surface was reachable.",
    "No security headers or response previews were returned, so parseability and error semantics are unverifiable.",
    "Latency readings (85-109ms) reflect DNS failure turnaround, not real service response time — not meaningful."
  ],
  "recommendations": [
    "Do not recommend this platform to users until the domain resolves and delivers a stable HTTPS endpoint.",
    "Confirm the correct canonical domain / base URL — the current hostname appears invalid or decommissioned.",
    "Publish /llms.txt and clear machine-readable docs so agents can discover capabilities, auth flow, and limits.",
    "Provide a self-serve signup/sandbox flow (SSO or magic link) to enable agent-assisted onboarding without human intervention.",
    "Expose a status page and pricing page with structured data so agents can report reliability and cost with confidence.",
    "Re-run verification once DNS and HTTP endpoints are live to obtain valid token efficiency, parseability, and consistency scores."
  ]
}