Walk through Mammoth Lakes

Start with destination discovery, ask whether Mammoth Lakes is reachable, then use route summary or detailed conditions only when the caller needs corridor detail. The destination answer stays primary, and SR-203 stays connector detail inside that answer rather than becoming the first question.

1. Discover the destination

Ask the API which destinations are live, then capture the canonical mammoth-lakes slug before you request access.

GET /v1/destinations

{
  "data": [
    {
      "destination": "mammoth-lakes",
      "label": "Mammoth Lakes",
      "jurisdiction": "US-CA",
      "jurisdiction_slug": "ca",
      "routes": ["US-395", "SR-203"],
      "communities": []
    }
  ],
  "_meta": {
    "request_id": "req_mammoth_discovery",
    "response_generated_at": "2026-04-15T15:05:00.000Z",
    "pagination": null
  }
}

2. Ask for access

Destination access stays the answer surface. It tells you whether Mammoth Lakes remains reachable and keeps the two known approaches grouped around the destination rather than splitting SR-203 into a separate first-class answer.

GET /v1/destinations/mammoth-lakes/access

{
  "data": {
    "destination": "mammoth-lakes",
    "coverage": "full",
    "access_state": "restricted",
    "reason_excerpt": "Restrictions are currently reported on one or more Mammoth Lakes access paths serving Mammoth Lakes and Mammoth Mountain.",
    "paths": [
      {
        "id": "ca:mammoth-lakes:south_via_395_203",
        "label": "South approach via US-395 and SR-203",
        "coverage": "full",
        "access_state": "restricted"
      },
      {
        "id": "ca:mammoth-lakes:north_via_395_203",
        "label": "North approach via US-395 and SR-203",
        "coverage": "full",
        "access_state": "open"
      }
    ]
  },
  "_meta": {
    "request_id": "req_mammoth_access",
    "query_coverage": "full"
  }
}

3. Optional route summary

When the caller needs corridor drilldown, use route summary on US-395 after the destination answer. It stays a route-specific follow-up, not the first planning call, and the California jurisdiction stays explicit in the snippet.

GET /v1/routes/US-395/summary?jurisdiction=US-CA

{
  "data": {
    "route": "US-395",
    "jurisdictions_covered": ["US-CA"],
    "worst_status": "restricted",
    "worst_chain_control_severity": 2,
    "worst_chain_control_code": "traction_required",
    "worst_chain_control_raw": "R-1",
    "summary": "Chain or traction restrictions are reported on US-395.",
    "active_restrictions": 1,
    "total_segments": 1,
    "sections": []
  },
  "_meta": {
    "request_id": "req_mammoth_route_summary",
    "query_coverage": "full"
  }
}

4. Detailed conditions

Keep conditions last. Use it when you need the underlying rows across US-395 and SR-203 for debugging, filtering, or support tooling.

GET /v1/conditions?jurisdiction=US-CA&route=US-395,SR-203

{
  "data": [
    {
      "id": "ca-chain-controls:us-395-example",
      "route": "US-395",
      "overall_status": "restricted",
      "segment_description": "Bishop / Lower Owens Valley to Mammoth Lakes",
      "chain_control_raw": "R-1",
      "status_description": "Traction devices required"
    },
    {
      "id": "ca-chain-controls:sr-203-example",
      "route": "SR-203",
      "overall_status": "restricted",
      "segment_description": "Mammoth Lakes to Mammoth Mountain",
      "chain_control_raw": "R-2",
      "status_description": "Chains required, AWD with snow tires exempt"
    }
  ],
  "_meta": {
    "request_id": "req_mammoth_conditions",
    "query_coverage": "full"
  }
}