Checks API

{
  "service_type": "platform",
  "base_url": "https://api.truora.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Truora-API-Key",
    "note": "API keys are issued via the Truora dashboard at account.truora.com. Some endpoints may also use checksum signatures or webhook secrets. Verify at dev.truora.com."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "No public per-call pricing. Enterprise/quote-based pricing; a pricing page exists but details require sales contact.",
      "pricing_page": "https://www.truora.com/precios"
    }
  },
  "rate_limits": {
    "note": "Not publicly documented; assume standard per-account limits. Confirm at dev.truora.com."
  },
  "capabilities": [
    "Digital identity verification (document + facial biometrics)",
    "Liveness detection (proof of life)",
    "Email and phone validation",
    "Proof of address verification",
    "Digital forms",
    "Electronic signature (via ZapSign)",
    "Background checks (TruChecks): criminal, judicial, legal, reputational",
    "KYC/AML compliance workflows",
    "WhatsApp engagement (chatbots, notifications, campaigns)",
    "WhatsApp Business API integration",
    "Web, mobile app, REST API, and WhatsApp integration channels",
    "Multi-language support (ES, EN, PT)",
    "Regional focus: Latin America"
  ],
  "raw_analysis": "Truora is a Latin America-focused technology platform for digital identity verification, fraud prevention, KYC/AML compliance, automated background checks, and customer engagement via WhatsApp AI chatbots. It serves regulated and digital industries: banking, fintech, e-commerce, marketplaces, proptech, insurance, and logistics.\n\nMaturity: The truora.com website presents a mature, established product suite with named enterprise customers (Rappi, Addi, Stori) and a dedicated developer portal at dev.truora.com. However, the Checks API itself is explicitly described as a PREVIEW and NOT STABLE, meaning the specific API surface referenced (the 'Checks API') is early-stage despite the broader platform being production-grade. The broader platform (identity verification, WhatsApp engagement, background checks, ZapSign e-signature) is commercially mature.\n\nAuth: API keys (Truora-API-Key header) are typical for this vendor; keys are managed in the account.truora.com dashboard. Some flows may use checksum/signature verification for webhooks. Exact scheme should be confirmed in dev.truora.com documentation.\n\nREST API: The description references a RESTful API ('Truora Check RESTful API') but no endpoint paths were provided in the source material. Developers should consult https://dev.truora.com/ for the authoritative API reference. Integration channels include Web, native App, REST API, and WhatsApp.\n\nPricing: Enterprise / quote-based subscription model. A pricing page exists (truora.com/precios) but public per-transaction pricing is not exposed; sales contact is required. There is no clearly advertised free tier for the core verification products, though some trial/preview access may exist via the developer portal.\n\nIntegrations/ecosystem: WhatsApp Business API, ZapSign e-signature (owned brand), developer portal, Intercom help center, partner/allies program, brand hub. Strong regional integrations for LatAm identity documents (e.g., cédula in Chile, SOFOMES in Mexico).\n\nRecommendation: Treat as a platform with a partially available REST API. Use dev.truora.com as the canonical source for endpoints, auth headers, rate limits, and stability guarantees. The Checks API should be considered preview/non-production until stability is announced."
}

0/3 tests passed

{
  "overall": 48,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 4.0,
    "response_parseability": 7.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 3.0,
    "latency": 2.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "model": "subscription_enterprise_quote_based",
    "public_pricing": false,
    "notes": "No public per-call pricing; pricing page requires sales contact. Hard for agents to give users concrete cost estimates."
  },
  "issues": [
    "All three automated checks (website_uptime, robots_txt, llms_txt) failed with SSLv3 handshake failure — platform not reachable via standard HTTPS probing, indicating TLS configuration issues or aggressive bot/SSL filtering",
    "No public pricing: quote-based enterprise model prevents agents from advising users on cost",
    "No documented LLM-friendly surface (llms.txt missing or unreachable)",
    "Onboarding likely requires human sales contact rather than self-serve",
    "Latency could not be verified; observed handshake failure at 30-135ms suggests connectivity problems rather than true performance"
  ],
  "recommendations": [
    "Publish a public pricing page or at least tiered starting rates so agents can quote costs",
    "Fix TLS handshake compatibility (avoid SSLV3 or deprecated ciphers) so standard HTTPS clients and agents can reach the site",
    "Provide a self-serve free tier or sandbox API keys to enable first-try success without sales contact",
    "Add llms.txt and publicly accessible REST API reference docs to improve agent parseability",
    "Publish a status page and uptime metrics for consistency signals",
    "Document API error codes and rate limits transparently to improve error clarity"
  ]
}