ATM Locator API

```json
{
  "service_type": "platform",
  "base_url": "https://hsbc.com:atm",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "No public pricing information available from the provided data. HSBC is a retail/commercial bank, so any ATM locator is likely a consumer-facing tool, not a paid API product."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "ATM location lookup (claimed)",
    "Consumer banking service discovery",
    "No verifiable API capabilities from supplied data"
  ],
  "raw_analysis": "The submitted entry is highly suspect and almost certainly malformed. The 'URL' https://hsbc.com:atm is not a valid URL — there is no such scheme/host combination. When a colon appears after a hostname, it introduces a port number or scheme separator, and the literal string 'atm' is not a valid port. More likely this is an artifact of an internal naming convention (e.g., 'hsbc.com:atm' used as a service key) that got mistakenly parsed as a URL. There is no evidence of an actual ATM Locator API at this address, no documented endpoints, no authentication scheme, no rate limits, and no pricing. HSBC itself is a major global bank (founded 1865, headquartered in London, one of the largest banking groups worldwide). HSBC does operate consumer-facing ATM/branch finder tools via its websites and mobile apps, and historically HSBC has had some developer/Open Banking APIs (particularly under PSD2 in the UK for account information and payment initiation). However, an 'ATM Locator API' as described here is not a known public HSBC product. Assessment: treat this as unverified/spurious metadata. Maturity: unknown. Intended audience: likely consumers seeking ATM locations, if it exists at all — not developers. Integrations: none identified. Recommendation: reject or re-verify at source; likely a data-quality error rather than a real platform."
}
```

0/3 tests passed

{
  "overall": 18,
  "dimensions": {
    "token_efficiency": 2.0,
    "first_try_success": 1.0,
    "response_parseability": 1.0,
    "error_clarity": 1.0,
    "doc_quality": 1.0,
    "auth_simplicity": 2.0,
    "latency": 2.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "transparent": false,
    "note": "No public pricing or API product info available from supplied data"
  },
  "issues": [
    "All three checks failed with 'Invalid port: atm' — the target appeared to be an ATM locator URL segment, not an API endpoint",
    "No verifiable API surface: no base URL, auth scheme, or response schema documented",
    "No public pricing or developer documentation in the supplied data",
    "robots.txt and llms.txt checks failed, indicating no agent-discoverable metadata at the probed host",
    "No status page or uptime data surfaced from the provided evidence"
  ],
  "recommendations": [
    "Do not recommend this platform to agents until a real developer API endpoint and docs are identified",
    "If HSBC does expose an API, re-probe with the correct developer portal host (e.g., developer.hsbc.com) rather than the ATM locator path",
    "Require documented base URL, auth method, and sample response before inclusion in any agent toolchain",
    "Provide an llms.txt or OpenAPI spec to enable agent-side discovery and parsing",
    "Once valid, add a public status page and clear rate-limit/error documentation"
  ]
}