Initial commit

commands/billing-updates.md

@@ -0,0 +1,50 @@
+---
+description: Get billing increment updates and changes for telecom destinations
+---
+
+# Billing Updates Command
+
+You are helping the user track billing increment changes in the telecommunications industry. Follow these steps:
+
+1. **Parse the user's query** to identify:
+   - Year filter (e.g., 2024, 2025)
+   - Country filter (e.g., "CAMBODIA")
+   - Change type filter (increase, decrease, improved, mixed)
+   - Timeframe (recent days)
+
+2. **Determine the appropriate endpoint:**
+   - `/updates/` - for filtered historical updates (year, country, change_type)
+   - `/updates/recent` - for updates in last N days (1-365 days)
+   - `/updates/summary` - for aggregated statistics
+
+3. **Construct the API request** to `https://destinations-api.telecomsxchange.com` with parameters:
+   - `year` - filter by year
+   - `country` - filter by country name
+   - `change_type` - filter by change type
+   - `days` - for recent endpoint (default 30)
+   - `limit` - default to 100, max 500 for updates
+
+4. **Use the WebFetch tool** to query the API
+
+5. **Present the results** showing:
+   - Date of change
+   - Country
+   - Prefix/Network
+   - Old billing increment
+   - New billing increment
+   - Change type (improvement/deterioration)
+
+6. **Analyze the impact:**
+   - Highlight favorable changes (better billing increments)
+   - Note unfavorable changes (worse billing increments)
+   - Summarize trends if multiple updates shown
+
+7. **Provide context** about what billing changes mean:
+   - Improved: Better for cost control (e.g., 60/60 → 60/1)
+   - Deteriorated: Worse for cost control (e.g., 60/1 → 60/60)
+
+**Example queries to handle:**
+- "Show billing updates for 2025"
+- "What changed in the last 30 days?"
+- "Show billing improvements for Cambodia"
+- "Get update summary"

commands/compare-billing.md

@@ -0,0 +1,54 @@
+---
+description: Compare billing increments across countries, networks, or operators
+---
+
+# Compare Billing Command
+
+You are helping the user compare billing increments across different telecommunications destinations. Follow these steps:
+
+1. **Parse comparison request** to identify:
+   - Countries to compare
+   - Network types to compare (Mobile vs Fixed)
+   - Specific operators to compare
+   - Regions to analyze
+
+2. **Gather data for each target:**
+   - Use `/search/` endpoint for each country/network
+   - Collect all relevant destinations
+   - Note billing increments for each
+
+3. **Organize results by billing favorability:**
+   - Best: 1/1 (per-second billing throughout)
+   - Better: X/1 (per-second after initial interval)
+   - Standard: 60/60 (per-minute billing)
+   - Less favorable: Higher initial intervals
+
+4. **Create comparison table showing:**
+   - Country/Network
+   - MCC/MNC
+   - Billing increment
+   - Favorability rating (★★★★★ scale)
+   - Cost impact estimate
+
+5. **Provide analysis:**
+   - Identify best options for cost efficiency
+   - Highlight outliers (unusually good or bad)
+   - Note regional patterns
+   - Suggest routing preferences based on billing
+
+6. **Calculate cost scenarios** if requested:
+   - Show cost for typical call durations (1min, 5min, 10min)
+   - Compare total costs across destinations
+   - Highlight savings potential
+
+**Use cases:**
+- Routing optimization (choose best billing)
+- Cost forecasting across markets
+- Vendor/carrier selection
+- Rate negotiation insights
+
+**Example queries to handle:**
+- "Compare billing for Cambodia vs Thailand mobile"
+- "Show me the best billing increments in Southeast Asia"
+- "Compare all US mobile carriers"
+- "Which countries have per-second billing?"

commands/destinations-search.md

@@ -0,0 +1,45 @@
+---
+description: Search telecom destinations by prefix, country, network, or MCC/MNC
+---
+
+# Destinations Search Command
+
+You are helping the user search the Destinations API for telecommunications data. Follow these steps:
+
+1. **Parse the user's query** to identify:
+   - Phone number prefix (e.g., "1", "44", "855")
+   - Country name (e.g., "UNITED STATES", "CAMBODIA")
+   - Network description (e.g., "Mobile", "Fixed")
+   - MCC/MNC code (e.g., 45601)
+
+2. **Construct the API request** to `https://destinations-api.telecomsxchange.com/search/` with appropriate query parameters:
+   - `prefix` - for phone number prefixes
+   - `country_name` - for country searches
+   - `description` - for network type searches
+   - `mccmnc` - for MCC/MNC lookups
+   - `limit` - default to 100, max 1000
+
+3. **Use the WebFetch tool** to query the API with a prompt like:
+   "Extract and return all destination records with their prefix, country_name, description, mccmnc, interval_1, and interval_n fields in a clear table format"
+
+4. **Present the results** in a well-formatted table showing:
+   - Prefix
+   - Country
+   - Network/Operator
+   - MCC/MNC
+   - Billing (interval_1/interval_n)
+
+5. **Explain billing increments** when relevant:
+   - 60/60 = 60s minimum, then per-minute
+   - 60/1 = 60s minimum, then per-second (better)
+   - 1/1 = per-second from start (best)
+
+6. **Handle pagination** if results exceed limit - inform user they can specify a page number
+
+**Rate Limit:** Remember the API allows 100 requests per minute.
+
+**Example queries to handle:**
+- "Search for Cambodia mobile networks"
+- "Find prefix +1"
+- "Look up MCC/MNC 45601"
+- "Show all destinations in United States"

commands/lookup-number.md

@@ -0,0 +1,46 @@
+---
+description: Look up telecom information for a specific phone number
+---
+
+# Phone Number Lookup Command
+
+You are helping the user identify carrier and billing information for a specific phone number. Follow these steps:
+
+1. **Parse the phone number:**
+   - Remove any formatting characters (+, -, spaces, parentheses)
+   - Extract the prefix (country code and initial digits)
+   - Validate it looks like a valid E.164 format
+
+2. **Perform progressive prefix matching:**
+   - Start with the full number (excluding the last few digits for privacy)
+   - If no match, try shorter prefixes
+   - E.g., for "+855123456789" try: "855123", "85512", "8551", "855"
+
+3. **Query the API** using the WebFetch tool:
+   - Endpoint: `https://destinations-api.telecomsxchange.com/search/?prefix=<prefix>`
+   - Try from most specific to least specific prefix
+
+4. **Present comprehensive results:**
+   - Country identified
+   - Network/Carrier name
+   - MCC/MNC code
+   - Network type (Mobile/Fixed/Other)
+   - Billing increment (interval_1/interval_n)
+
+5. **Calculate estimated costs** if the user asks:
+   - Show billing structure clearly
+   - Explain minimum charge (interval_1)
+   - Explain per-unit charge after minimum (interval_n)
+
+6. **Provide use case context:**
+   - Routing decision support
+   - Fraud detection (verify country/carrier match)
+   - Cost estimation for calls/SMS
+
+**Privacy note:** Never require or request the full phone number - work with prefixes only.
+
+**Example queries to handle:**
+- "Look up +855 12 345 6789"
+- "What carrier is +1-212-555-0100?"
+- "Identify network for 447700900123"
+- "Find billing for Cambodia number starting with 855"