TruAnon Private API

{
  "service_type": "platform",
  "base_url": "https://truanon.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Public pricing page references comparisons with Stripe/Veriff/Persona/Jumio, but no specific API pricing is stated. The platform appears to operate on a subscription or freemium model for platforms integrating the identity system, but details are not public."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Decentralized digital identity verification",
    "Account anchoring across multiple platforms (e.g., Bluesky, GitHub)",
    "Grant/revoke access control for identity visibility",
    "Continuous trust rank (not binary checkmark)",
    "No government ID or document collection",
    "Public and private service modes",
    "Developer integration via APIs (reference implementation in GitHub repo jtayler/trusted)"
  ],
  "raw_analysis": "TruAnon is a digital identity platform that emphasizes privacy and user control. It allows individuals to 'anchor' their accounts across different networks and grant or revoke visibility of their identity to others. Trust is represented as a continuous rank rather than a simple verification checkmark. The system avoids collecting government IDs or creating a central dossier, positioning itself as an 'inherently safe' identity solution. It is aimed at platforms and services that need to verify user identity without invasive document uploads. The service is mature enough to have a public website, detailed about page, developer documentation on GitHub (jtayler/trusted), and thought-leadership essays. However, there is no public REST API documentation available on the main site; the API integration guide is hosted on GitHub. Authentication methods, endpoints, rate limits, and pricing are not publicly disclosed. The platform appears to be in an early adopter or beta phase, with a focus on decentralized identity and Web3 concepts (DIDs, AT Protocol). The GitHub repository 'trusted' likely contains the reference implementation and API details, but without accessing it, only high-level capabilities are known. The service does not seem to offer a traditional REST API with standard endpoints; instead, it may provide SDKs or integration patterns for platforms to embed the identity verification flow. Overall, TruAnon is a niche identity platform targeting privacy-conscious platforms and users, with a unique continuous trust model."
}

3/3 tests passed

```json
{
  "overall": 71,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 6.5,
    "response_parseability": 7.5,
    "error_clarity": 7.0,
    "doc_quality": 8.0,
    "auth_simplicity": 6.5,
    "latency": 9.5,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "unknown",
    "public_tiers": false,
    "api_pricing_disclosed": false,
    "notes": "Public site compares against Stripe/Veriff/Persona/Jumio but discloses no actual API or platform pricing. Cannot compute per-call or per-member cost normalization."
  },
  "issues": [
    "No public pricing — cannot be normalized or forecast for users evaluating cost.",
    "API/dashboard paths (/api/, /dash/, /truanon/) are blocked to crawlers; agents cannot self-discover usage patterns or endpoints from robots.txt-visible surfaces.",
    "Reference implementation is a single GitHub repo (jtayler/trusted); no public API reference, OpenAPI spec, or SDK surfaced in checks.",
    "Value prop ('continuous trust rank, no gov ID') is clear conceptually but the integration contract is opaque without repo digging.",
    "Pricing section is comparative marketing rather than structured commercial terms — hard for agents to quote."
  ],
  "recommendations": [
    "Publish machine-readable pricing (llms.txt or /pricing.json) so agents can quote cost without human interpretation.",
    "Ship an OpenAPI/SDK spec at a crawlable path (e.g., /openapi.json) to boost parseability and first-try success.",
    "Add a quickstart with copy-paste auth flow (magic link or API key issuance) to reduce onboarding friction.",
    "Keep the explicit AI-crawler welcome in robots.txt — it is a strong signal; extend Allow to cover /docs/ and /api-reference/.",
    "Surface a status page URL in llms.txt to substantiate the consistency score with evidence."
  ]
}
```