49
/100
prowl
Benchmarked Apr 25, 2026

PostcodeData.nl

Provide geolocation data based on postcode for Dutch addresses

data platform_profile
Benchmark Your API

Score Breakdown

Parseability 8/10
Token Efficiency 7/10
Auth Simplicity 5/10
Documentation 4/10
Error Clarity 4/10
First-Try Success 3/10
Consistency 2/10
Latency 1/10

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
```json
{
  "service_type": "platform",
  "base_url": "http://api.postcodedata.nl",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/v1/postcode/",
      "description": "Get geolocation data for a Dutch postcode and street number."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Provide geographic coordinates based on a Dutch postcode and street number",
    "Return street, city, municipality, and province information",
    "Output response in JSON format"
  ],
  "raw_analysis": "PostcodeData.nl is a specialized API service designed to provide geolocation and address details for Dutch postcodes. It is primarily used by businesses and developers needing to validate or obtain location information within the Netherlands. The service returns structured geographic data including street name, city, municipality, province, and coordinates (latitude and longitude) when a postcode and street number are provided. The service is mature and appears focused on data accuracy for Dutch addresses specifically. There is no explicit mention of API authentication requirements, suggesting ease of access, but the lack of documented endpoint rate limits or pricing model specifics limits understanding of scalability and cost."
}
```
Execute

0/3 tests passed

TestEndpointStatusLatency
website_uptimeGET /None30030ms
robots_txtGET /robots.txt404380ms
llms_txtGET /llms.txt404126ms
Interpret
```json
{
  "overall": 32,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 3.0,
    "response_parseability": 8.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 5.0,
    "latency": 1.0,
    "consistency": 2.0
  },
  "pricing_normalized": {},
  "issues": [
    "High latency detected with website uptime test (>30000ms).",
    "404 errors present when accessing /robots.txt and /llms.txt, indicating potential lack of robots instructions and documentation.",
    "Lack of clarity in documentation as determined by limited error information and help resources.",
    "Lacks security headers which may affect platform trustworthiness."
  ],
  "recommendations": [
    "Improve server response time to enhance user experience and agent interaction.",
    "Provide comprehensive error messages and clear documentation for API usage.",
    "Implement security headers to ensure secure interaction with the platform.",
    "Consider offering a clear, concise pricing model to inform potential users."
  ]
}
```

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