Postmon

{
  "service_type": "platform",
  "base_url": "http://postmon.com.br",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "description": "The service is described as free, with no mention of paid tiers or subscription.",
      "monetization": "Not specified; possibly maintained as a public service."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Brazilian ZIP code (CEP) query",
    "Address lookup from CEP",
    "Order tracking (appears to be intended, but scope unclear)",
    "Public REST API",
    "Free access"
  ],
  "raw_analysis": "Postmon is a Brazilian API service focused on querying postal information, specifically Brazilian ZIP codes (CEPs). The service is free and appears to be a public utility for developers and businesses needing address validation or lookup. The official description mentions 'orders' as well, but the primary documented use case is CEP queries. The platform is relatively niche, targeting Brazilian developers and applications that require Brazilian address data. Its maturity is uncertain; the service has been around for several years, but documentation is sparse and the site itself is minimal (possibly a single landing page). No pricing information is provided, confirming it is free. There are no visible rate limits or authentication requirements, suggesting it is a simple open API. The main integration would be via HTTP calls to retrieve CEP data, but the exact endpoint structure is not documented in the provided content, so I cannot specify endpoints. Potential integrations include e-commerce platforms, logistics systems, and any app needing address verification in Brazil. Overall, this is a lightweight, free utility service, though its reliability and long-term maintenance are not guaranteed given the lack of detailed documentation or corporate backing."
}

1/3 tests passed

```json
{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.5,
    "response_parseability": 7.5,
    "error_clarity": 4.0,
    "doc_quality": 3.5,
    "auth_simplicity": 7.0,
    "latency": 8.5,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "type": "completely_free",
    "price_per_request": 0,
    "cost_per_1000_requests": 0,
    "monetization": "free_public_service"
  },
  "issues": [
    "No robots.txt or llms.txt, indicating poor machine-readable documentation coverage",
    "Order tracking capability mentioned in capabilities but scope unclear — misleading for agents",
    "No security headers on the website, raising reliability concerns for production use",
    "GitHub Pages hosting suggests minimal maintenance resources, potential stability risk",
    "No structured API spec (OpenAPI/Swagger) appears readily discoverable on the main page"
  ],
  "recommendations": [
    "Add an llms.txt file to explicitly document API endpoints, parameters, and response formats for AI agents",
    "Publish an OpenAPI/Swagger specification to improve response parseability and enable client generation",
    "Clarify and scope the order tracking feature — is it a full-featured API or informational only?",
    "Add a status page or uptime transparency section to build trust in consistency",
    "Include code examples and a clear getting-started guide in the README/docs"
  ]
}
```