Soldfetch API

{
  "service_type": "platform",
  "base_url": "https://soldfetch.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "unknown"
  ],
  "raw_analysis": "Service: Soldfetch API\nURL: https://soldfetch.com\n\nDescription provided: \"Auto-registered via benchmark URL submission.\" This is not a substantive description; it appears to be a placeholder entry in a benchmark or directory, with no actual information about what the service does.\n\nAnalysis:\n- The domain soldfetch.com suggests a product related to sales, fetching, or data retrieval, but without visiting the site or additional documentation, no reliable inference can be made.\n- Category is listed as \"uncategorized,\" indicating it has not been classified by humans or automated systems.\n- No API documentation, authentication methods, endpoints, pricing, or rate limits are known.\n- There is no evidence of a public REST API, SDKs, or integration ecosystem.\n- Maturity and target audience cannot be determined from the provided text.\n- It may be a real product, a parked domain, or an internal benchmark artifact. All fields are therefore marked unknown or empty.\n- Recommendation: treat as unverified. If access to the live site is possible, perform manual reconnaissance (homepage content, docs page, pricing page, developer portal) before any integration or evaluation."
}

3/3 tests passed

```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.5,
    "response_parseability": 9.0,
    "error_clarity": 7.5,
    "doc_quality": 8.0,
    "auth_simplicity": 6.5,
    "latency": 9.5,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "type": "unknown",
    "notes": "Pricing not exposed in provided data; llms.txt and OpenAPI suggest a documented REST/MCP product but no rate card was captured."
  },
  "issues": [
    "Pricing model and tiers are not visible in the supplied capability/pricing data.",
    "robots.txt disallows /api/ and /mcp for crawlers (expected, but agents relying on crawl-discovery must use llms.txt/OpenAPI instead).",
    "Auth flow not described in captured material — signup path unclear to agents.",
    "Capabilities reported as 'unknown' despite llms.txt advertising eBay search/item endpoints."
  ],
  "recommendations": [
    "Surface pricing tiers and rate limits in llms.txt and a /pricing page for agent discovery.",
    "Publish explicit auth onboarding (API key issuance, magic link, or Notlogin) in docs so agents can self-serve.",
    "Add structured error schema examples to OpenAPI so errors are machine-parseable.",
    "Publish a status page URL and uptime SLA to strengthen consistency signal.",
    "Enrich capabilities metadata (eBay sold/active search, category search, item details) so downstream scoring doesn't flag 'unknown'."
  ]
}
```