Geocoder REST API

{
  "service_type": "platform",
  "base_url": "https://dpdd.atlassian.net",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "address cleaning",
    "address correction",
    "address completion",
    "geocoding",
    "reverse geocoding",
    "proximity search",
    "intersection address resolution",
    "physical address resolution",
    "occupant data (British Columbia)"
  ],
  "raw_analysis": "The provided URL (https://dpdd.atlassian.net/servicedesk/customer/portal/1/group/7) resolves to a Jira Service Management customer portal page, not an actual Geocoder REST API. The additional content is the HTML source of an Atlassian Jira Service Management web application (title 'Jira Service Management', with sdPluginVersion 3.3.0-OD, region prod-cacentral). This is a help-desk/support portal used to submit and track service requests, not a documented API endpoint.\n\nService intent: The described service is an 'address cleaning, correction, completion, geocoding, reverse geocoding, and proximity' API for intersection and physical addresses and their occupants in British Columbia. This strongly resembles the BC Address Geocoder / DataBC geocoding services. The actual REST API documentation would live at a different domain (e.g., geocoder.api.gov.bc.ca or similar DataBC endpoints), and this Atlassian portal URL appears to be used for support requests (Service Desk) related to that API — i.e., a place where users file tickets to request API access or report issues.\n\nPlatform characteristics of the observed page (Jira Service Management customer portal):\n- Purpose: Customer-facing service desk for submitting and tracking support requests.\n- Maturity: Atlassian Jira Service Management is an established, widely adopted ITSM/helpdesk platform (plugin version 3.3.0-OD indicates a cloud-hosted instance).\n- Authentication: The portal is typically accessible with or without login depending on configuration; anonymous ticket creation is often allowed, but account login (Atlassian account / SSO) may be required to view existing requests. Exact auth for the underlying Geocoder API is not determinable from this page (likely an API key or subscription key for DataBC services).\n- Integrations: Jira Service Management supports REST APIs of its own, email intake, Slack, Teams, webhooks, and automation rules. However, these are Jira's platform capabilities, not the Geocoder API's.\n\nMaturity of the described Geocoder service: Based on the description referencing British Columbia addresses and occupant data, this is likely a government-run geocoding service (DataBC / BC Address Geocoder). Such services are generally mature, authoritative, and free or low-cost for the public sector, but precise terms, auth model, rate limits, and endpoints cannot be inferred from the provided URL or HTML.\n\nConclusion: The URL does not represent the Geocoder REST API itself. It is a Jira Service Management service desk portal, presumably used to manage access requests or support for the Geocoder API. Accurate API details (base URL, endpoints, auth, rate limits, pricing) would require consulting the official BC Address Geocoder / DataBC API documentation rather than this Atlassian portal page."
}

2/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 5.0,
    "response_parseability": 7.0,
    "error_clarity": 5.0,
    "doc_quality": 5.0,
    "auth_simplicity": 5.0,
    "latency": 6.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "notes": "No public pricing data available; pricing model unknown"
  },
  "issues": [
    "Root domain returned 202 (likely a queue/JS-gated page) rather than a simple 200",
    "No llms.txt — 404 redirects to JIRA dead-link page, hurting agent discoverability",
    "robots.txt appears to be a JIRA/Atlassian-generated page; does not clearly describe the address API",
    "Pricing model is unspecified, blocking cost estimation for agent recommendations",
    "Documentation discovery is poor — no clear getting-started artifact surfaced in checks",
    "Website latency 617ms is acceptable but not fast"
  ],
  "recommendations": [
    "Publish a public pricing page with tiers so agents can compare cost/value",
    "Add an llms.txt or llms-full.txt describing endpoints, auth, and capabilities",
    "Expose a clean REST API docs page (OpenAPI spec preferred) for parseability",
    "Clarify robots.txt to reflect actual product surface, not JIRA internals",
    "Provide a simple API key or magic-link onboarding flow to reduce signup friction",
    "Add a status page / uptime indication to boost consistency score",
    "Trim homepage to a concise value prop (address cleaning + geocoding + occupant data) so agents can summarize in one sentence"
  ]
}