Harcourtvaluations API

{
  "service_type": "platform",
  "base_url": "https://harcourtvaluations.ai",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "unknown - auto-registered via benchmark URL submission",
    "AI-related category indicated"
  ],
  "raw_analysis": "The service 'Harcourtvaluations API' at https://harcourtvaluations.ai was auto-registered via a benchmark URL submission, and the provided description contains no substantive information about the platform's functionality, target users, maturity, integrations, authentication, endpoints, pricing, or rate limits. The name suggests it may relate to valuations (possibly financial, real estate, or business valuations) combined with 'Harcourt', and the category is listed as 'ai'. However, no public REST API details, documentation, or integration information are available from the supplied content. Without additional documentation or site inspection, all technical and business attributes remain unknown. The platform appears to be an early or unpublicized offering with no verifiable integration surface at this time."
}

3/3 tests passed

{
  "overall": 78,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 8.0,
    "response_parseability": 7.5,
    "error_clarity": 7.0,
    "doc_quality": 8.5,
    "auth_simplicity": 8.0,
    "latency": 9.6,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing detected. Likely institutional subscription or consultation-based. Ambiguity lowers fit for consumer agent recommendations."
  },
  "issues": [
    "No public pricing information available; agents cannot evaluate cost-effectiveness for users.",
    "Capabilities and feature set unclear from homepage preview alone — value proposition is niche (NAV for 33 mining companies).",
    "Explicit 'no model training' policy in robots.txt limits usefulness for agent-driven extraction/training workflows.",
    "Auth flow unknown; likely institutional/enterprise, which may block quick onboarding."
  ],
  "recommendations": [
    "Publish a clear pricing page or 'contact for pricing' with tiered visibility so agents can surface cost expectations.",
    "Expand llms.txt to enumerate API endpoints, data fields, and update frequency for machine consumers.",
    "Provide a machine-readable JSON catalog of the 33 covered companies with NAV values and source citations.",
    "Add a developer sandbox or public API keys with magic-link auth so agents can onboard without human mediation.",
    "Document auth requirements and SSO support explicitly in the agent reference."
  ]
}