Aveco API

{
  "service_type": "platform",
  "base_url": "https://aveco.app",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [],
  "raw_analysis": "Insufficient information. The provided record contains only a service name ('Aveco API'), a URL (https://aveco.app), and a description stating 'Auto-registered via benchmark URL submission.' No product documentation, feature description, pricing, authentication details, API reference, or integration list was supplied. Consequently, I cannot determine with confidence what Aveco does, who it targets, its maturity level, whether it exposes a public REST API, or what capabilities it offers. The service name includes 'API,' suggesting it may be an API-oriented product, but this is inferred, not confirmed. The base_url is taken as https://aveco.app. To produce a reliable assessment, the following are needed: (1) official docs/API reference URL, (2) authentication scheme (API key, OAuth, token, etc.), (3) available endpoints, (4) pricing page or plan details, (5) stated rate limits, and (6) list of supported integrations. Without these, all fields are returned as unknown or empty rather than guessed."
}

3/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 6.0,
    "response_parseability": 5.5,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 5.5,
    "latency": 6.5,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "transparency": "not_disclosed"
  },
  "issues": [
    "No pricing information available — users can't evaluate cost before committing",
    "No public API documented in capabilities; only a web app appears to exist",
    "Heavy JS-gated login/register routes mean agents can't onboard users programmatically",
    "No structured data (schemas, OpenAPI) detected — response parseability is limited to scraping",
    "llms.txt exists but is marketing-oriented (value prop), not agent-actionable docs"
  ],
  "recommendations": [
    "Publish transparent pricing tiers in llms.txt and on the site",
    "Expose a documented REST API with OpenAPI spec for lead enrichment and campaign management",
    "Support programmatic sign-up via magic link or agent-verified identity to remove the human onboarding dance",
    "Expand llms.txt with concrete endpoints, auth flows, and rate limits rather than positioning copy",
    "Add a status page / uptime indicator to strengthen reliability signals"
  ]
}