TSAPI

{
  "service_type": "platform",
  "base_url": "https://www.tsapi.net",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "Listed as 'Free Forever', non-profit initiative, Creative Commons licensed specification"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "industry-standard specification for transferring survey data",
    "API specification/documentation (see /docs/)",
    "open source specification",
    "Creative Commons licensing",
    "non-profit governance",
    "news and community updates (/news/)",
    "sponsor/support program",
    "contact/inquiry channel"
  ],
  "raw_analysis": "TSAPI (tsapi.net) is NOT a conventional API service provider — it is a non-profit standards body. Its stated mission is 'to define, distribute & maintain an API standard for Transferring Survey data.' The site is a Next.js marketing/documentation site for a specification, not a hosted API with endpoints and keys.\n\nNature of the organization:\n- Non-profit initiative (not a commercial SaaS or data provider).\n- Publishes and maintains an open industry standard, licensed under Creative Commons and Open Source.\n- Badges and site copy emphasize: 'Free Forever', 'Open Source', 'Industry Standard', 'Creative Commons', 'Non-Profit'.\n\nWho it's for:\n- Survey/market research platforms, panel providers, data processors, and vendors who need a common format/interface for exchanging survey data between systems.\n- Implementers (developers at survey tool vendors) who would adopt the TSAPI spec in their own products.\n\nMaturity:\n- Positioning strongly suggests an established initiative (sponsors, news section, formal docs site at /docs/, explicit 'industry standard' claim).\n- However, from the landing page alone there is no verifiable evidence of adoption scale, published version numbers, governance committee, or release cadence — those would need to be confirmed from /docs/ and /news/.\n\nIntegrations / API surface:\n- No public REST API with endpoints, keys, or rate limits was discoverable from the landing page.\n- The deliverable is a specification + documentation (/docs/), intended to be implemented by third parties rather than called directly.\n- No authentication, no pricing tiers, no rate limits apply.\n\nPractical interpretation for a platform analyzer:\n- Treat as a reference/documentation platform, not an API to be crawled for live data.\n- Integration would mean conforming one's own survey data exchange to the TSAPI spec, not calling tsapi.net.\n\nRecommendation:\n- If a caller wants to consume live data, tsapi.net is not the right target.\n- If a caller wants to adopt a survey-data interchange standard, evaluate /docs/ for spec version, schema, and conformance details.\n- Confirm maturity (versions, adopters, sponsors) via the /docs/ and /news/ pages before treating it as a de facto standard."
}

3/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 6.0,
    "error_clarity": 5.0,
    "doc_quality": 6.0,
    "auth_simplicity": 9.0,
    "latency": 5.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Free Forever, non-profit, Creative Commons licensed specification"
  },
  "issues": [
    "robots_txt and llms_txt checks returned the HTML doctype instead of expected plain-text/markdown content, indicating these endpoints are not actually implemented (likely SPA catch-all fallbacks)",
    "No security headers detected on responses",
    "No public API endpoint exposed for querying the specification programmatically",
    "Onboarding complexity unknown — no signup flow described (may be intentional for a spec project)",
    "Latency ~500-570ms per request is acceptable but not fast"
  ],
  "recommendations": [
    "Serve a real /llms.txt so agents can quickly ingest the spec summary",
    "Expose a machine-readable schema (JSON Schema or OpenAPI) endpoint separate from HTML docs",
    "Return proper robots.txt plain text rather than the SPA fallback",
    "Add security headers (HSTS, CSP, X-Content-Type-Options)",
    "Provide a versioned, parseable endpoint (e.g. /spec/v1.json) for agent consumption"
  ]
}