BroadbandMap Cell Coverage

Status: Preliminary skill (v0.x). This is an intentionally small first release and is expected to evolve quickly.

Use this skill to answer: “How good is cell coverage here?” for a specific location.

Quick workflow

1. 1. Resolve location to coordinates (lat/lon).
2. Run scripts/cell_coverage_lookup.py to call the coverage API.
3. Summarize key results:

1. 4. Include caveats when API fields are missing or endpoint behavior is unknown.

Run the script

CODEBLOCK0

Default endpoint used by this skill:

• - INLINECODE1
• Optional filters: network (att|verizon|t-mobile|us-cellular|dish|gci|cellcom|c-spire), tech (4g|5g)

Address mode (uses OpenStreetMap Nominatim geocoding first):

CODEBLOCK1

Optional overrides and filters:

CODEBLOCK2

Advanced endpoint overrides:

CODEBLOCK3

Output contract

The script prints JSON by default with:

• - input: address/lat/lon used
• INLINECODE7: final URL and query params
• INLINECODE8: parsed API JSON (or raw body)
• INLINECODE9: best-effort normalized fields (providers, technologies, notes)
• INLINECODE13: any recoverable errors

Use --format report for a concise human-readable output.

Example commands

CODEBLOCK4

Known limitations

• - This skill is a preliminary v0.x release and will be iterated/enhanced.
• API is alpha and may change schema/limits without notice.
• Default public limit is low (~60 requests/hour/IP).
• Coverage maps are modeled estimates and may differ from real-world signal.

Response style

When replying to users:

• - Start with a one-paragraph answer.
• Then list providers/technologies in bullets.
• End with one caveat sentence: coverage maps are estimates and real-world signal may vary.

references/

Read references/api-notes.md when endpoint details need adjustment.