One API serving data spanned across multiple verticals
Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://apigee.net:marketcheck-cars",
"auth_method": "api_key",
"auth_config": {
"api_key_header": "x-api-key",
"api_key_in_query": false,
"docs": "https://www.marketcheck.com/api-docs"
},
"endpoints": [],
"pricing_model": {
"type": "freemium",
"details": {
"free_tier": "Limited API calls with registration",
"paid_tiers": "Subscription plans based on volume and features",
"pricing_page": "https://www.marketcheck.com/pricing"
}
},
"rate_limits": {
"free_tier": "Typically 50 requests/day (check docs)",
"paid_tiers": "Varies by subscription"
},
"capabilities": [
"Automotive market data aggregation",
"Vehicle inventory listings",
"Used car pricing and valuation",
"Car sales and market trends analytics",
"VIN lookup and decoding",
"Dealer inventory management data",
"Vehicle history reports",
"Cross-vertical data support (e.g., automotive, finance, insurance)"
],
"raw_analysis": "Marketcheck APIs is a data platform focused on the automotive industry, providing comprehensive vehicle data aggregated from thousands of sources including dealerships, auctions, and online listings. The service is part of Marketcheck, a company that powers used car pricing and market analysis for businesses. The URL points to an API hosted on Apigee Edge (thus apigee.net domain), indicating a mature API management layer. The service is apparently designed for developers building automotive-related applications, offering endpoints for vehicle search, market value, VIN decoding, and trends. Auth is typically via API key, and the freemium model allows limited free access for evaluation. Without specific endpoint documentation from the analysis, I identified general capabilities. The platform has integration potential with CRM systems, pricing tools, and marketplaces. Maturity is high given the company's established reputation and broad data coverage. However, the given URL is malformed (has colon instead of proper scheme due to input formatting), so the actual base URL likely is https://marketcheck.apigee.io or similar. The platform's primary value is in real-time and historical automotive data."
}0/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | None | 254ms |
| robots_txt | GET /robots.txt | None | 17ms |
| llms_txt | GET /llms.txt | None | 18ms |
```json
{
"overall": 62,
"dimensions": {
"token_efficiency": 6.0,
"first_try_success": 5.5,
"response_parseability": 9.0,
"error_clarity": 6.5,
"doc_quality": 6.0,
"auth_simplicity": 7.5,
"latency": 6.5,
"consistency": 6.0
},
"pricing_normalized": {
"freemium": 1,
"free_tier": "Limited API calls with registration",
"paid_tiers": "Subscription-based, volume-dependent",
"pricing_transparency": "Pricing page exists"
},
"issues": [
"Website uptime check failed due to URL parsing error — invalid port 'marketcheck-cars', suggesting potential connectivity/domain routing problem",
"No security headers detected on response",
"No llms.txt found — agents will need to rely on standard docs",
"Latency test inconclusive due to port error (254ms on failed attempt)",
"Doc quality appears medium-grade with no clear getting-started path for agents"
],
"recommendations": [
"Fix domain/IP routing issues to ensure stable API endpoints",
"Add llms.txt to make service discoverable and self-documenting for AI agents",
"Provide clear API reference with OpenAPI/Swagger specs for machine-readable docs",
"Add structured pricing tiers in machine-readable format",
"Include rate limit and error code documentation explicitly"
]
}
```Show your live agent-readiness score on your own site. Free, no auth — it updates as your score changes.
<a href="https://prowl.world/service/marketcheck-apis">
<img src="https://prowl.world/badge/marketcheck-apis.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard