63
/100
prowl
Benchmarked Apr 25, 2026

keycdn IP Location Finder

Get the IP geolocation data through the simple REST API. All the responses are JSON encoded

hrapidata platform_profile
Benchmark Your API

Score Breakdown

Parseability 8/10
Token Efficiency 7/10
Latency 6/10
Consistency 6/10
Auth Simplicity 6/10
First-Try Success 6/10
Documentation 5/10
Error Clarity 5/10

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
```json
{
  "service_type": "platform",
  "base_url": "https://tools.keycdn.com/geo",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "unknown", "details": {}},
  "rate_limits": {},
  "capabilities": ["IP geolocation data retrieval", "JSON encoded responses"],
  "raw_analysis": "The KeyCDN IP Location Finder is a tool designed to provide users with geolocation data based on IP addresses. It operates through a simple REST API, where all responses are formatted in JSON. This makes it accessible for integration into various applications that require geographic information regarding IP addresses. While the service is categorized under hr, api, and data, there is no publicly detailed pricing model or specific rate limiting information for the service. This suggests a possible integration with other KeyCDN tools or services oriented towards businesses needing geolocation data. The platform is mature enough to provide straightforward and useful geolocation data without requiring authentication, indicating ease of access for users interested in basic IP location services."
}
```
Execute

1/3 tests passed

TestEndpointStatusLatency
website_uptimeGET /200781ms
robots_txtGET /robots.txt404131ms
llms_txtGET /llms.txt404247ms
Interpret
```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 6.0,
    "response_parseability": 8.0,
    "error_clarity": 5.0,
    "doc_quality": 5.0,
    "auth_simplicity": 6.0,
    "latency": 6.0,
    "consistency": 6.0
  },
  "pricing_normalized": {},
  "issues": [
    "Robots.txt and llms.txt return 404 status code, indicating potential areas not well covered in documentation or security protocols.",
    "Latency above 500ms could indicate possible delays in data retrieval.",
    "Unknown pricing model, making it difficult for users to anticipate usage costs."
  ],
  "recommendations": [
    "Improve and complete the documentation for robots.txt and other security or protocol files to provide clearer guidance.",
    "Optimize website and API latency to improve user experience and data retrieval speed.",
    "Clearly outline the pricing model and options available to users for better cost predictability and management."
  ]
}
```

Agent Readiness

x402 Payments
Not supported
Streaming
No
Sandbox
None
Agent Auth
Unknown
SDKs
None listed
MCP Support
No

Want the full interactive view?

See operational metrics, LLM evaluations, agent readiness, and more.

Open in Dashboard