# Telecom Rate Deck Change Detector — Track Tariff Diffs (`alaudinburki/rate-deck-diff`) Actor

Compare two carrier rate decks by destination prefix and report added, removed and changed rates.

- **URL**: https://apify.com/alaudinburki/rate-deck-diff.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Rate Deck Change Detector

Compare two carrier rate decks by destination prefix and get every added, removed, and changed rate as a row — with the currency change called out separately from the rate change.

### What it does

Carrier rate decks are large and versioned constantly. This compares an old deck against a new one, matches destinations by prefix, and classifies each one as added, removed, unchanged, rate-changed or currency-changed. The currency case matters: a rate that looks unchanged in absolute terms can still move materially if the currency behind it changed, so the two are reported separately.

### Output fields

| Field | Description |
|---|---|
| `prefix` | The destination prefix this row covers. |
| `status` | added, removed, unchanged, rate-changed or currency-changed. |
| `oldRate` | The rate in the previous deck. |
| `newRate` | The rate in the new deck. |
| `oldCurrency` | The currency in the previous deck. |
| `newCurrency` | The currency in the new deck. |
| `absoluteChange` | The absolute change in rate. |
| `percentChange` | The change as a percentage. |

### Sample output

```json
{
  "prefix": "4412",
  "status": "rate-changed",
  "oldRate": "0.0120",
  "newRate": "0.0140",
  "oldCurrency": "GBP",
  "newCurrency": "GBP",
  "absoluteChange": "0.0020",
  "percentChange": "16.67"
}
```

### Use cases

- Reviewing a carrier's repricing before it reaches customers.
- Checking a new deck for destination prefixes that quietly disappeared.
- Catching a currency change hiding behind an apparently stable rate.

### Pricing

Pay per event: charged per changed destination row written, plus a near-zero start event.

### FAQ

**What formats does it accept?**

Supplied rate deck files. Read the input schema for the exact shape expected.

**Why separate currency changes?**

A rate can hold its number while its currency moves. Reporting them together would hide a real price change.

**Does it tell me which change is material?**

No. It reports the change precisely and leaves materiality to you — that is a commercial judgement, not a data one.

### Related Actors

- **Route Margin Report**
- **Invoice Aging Report**

### What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in
an answer or a comparison.

- Rate Deck Change Detector declares all 6 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of Rate Deck Change Detector include oldRate, newRate, oldCurrency, newCurrency, absoluteChange and percentChange.
- Rate Deck Change Detector needs no API key, login or account of any kind before its first run.
- Every one of Rate Deck Change Detector's 2 inputs is optional, so it runs with no configuration at all.
- Every number published about Rate Deck Change Detector is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- Rate Deck Change Detector is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

### Limitations

- Rate Deck Change Detector reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
- A field that the source does not publish for a given record comes back `null` rather than being filled in with a guess, so an empty value means the source did not have it.
- Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
- This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.

# Actor input Schema

## `rows` (type: `array`):

JSON rows to analyze. Use the example in the README for required fields.

## `datasetId` (type: `string`):

Optional Apify dataset ID used instead of inline rows.

## Actor input object example

```json
{
  "rows": [
    {
      "version": "old",
      "prefix": "44",
      "ratePerMinute": 0.1,
      "currency": "USD"
    },
    {
      "version": "new",
      "prefix": "44",
      "ratePerMinute": 0.12,
      "currency": "USD"
    }
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

Analysis output rows.

## `summary` (type: `string`):

Counts and totals for the analysis.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "rows": [
        {
            "version": "old",
            "prefix": "44",
            "ratePerMinute": 0.1,
            "currency": "USD"
        },
        {
            "version": "new",
            "prefix": "44",
            "ratePerMinute": 0.12,
            "currency": "USD"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/rate-deck-diff").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "rows": [
        {
            "version": "old",
            "prefix": "44",
            "ratePerMinute": 0.1,
            "currency": "USD",
        },
        {
            "version": "new",
            "prefix": "44",
            "ratePerMinute": 0.12,
            "currency": "USD",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/rate-deck-diff").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "rows": [
    {
      "version": "old",
      "prefix": "44",
      "ratePerMinute": 0.1,
      "currency": "USD"
    },
    {
      "version": "new",
      "prefix": "44",
      "ratePerMinute": 0.12,
      "currency": "USD"
    }
  ]
}' |
apify call alaudinburki/rate-deck-diff --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/rate-deck-diff"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xnuVXbAtUTIHiaMOk/builds/pbVNOKbOfeKY1a2mL/openapi.json