# Matter Certification Tracker (`firedanceio/matter-certification-tracker`) Actor

Every new, updated and revoked Matter smart home certification from the official CSA ledger, with maker, Matter version and certificate ID. Product name and device type appear once the maker registers the model, often weeks after certification.

- **URL**: https://apify.com/firedanceio/matter-certification-tracker.md
- **Developed by:** [Firedance](https://apify.com/firedanceio) (community)
- **Categories:** Automation, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 certification reporteds

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

## Matter Certification Tracker

See every Matter smart home product that was certified, updated or revoked, straight from the
**CSA Distributed Compliance Ledger** (DCL), the official registry of Matter certifications. Schedule
it weekly and get a clean table of what the market shipped: who made it, which Matter version and
transport it uses, and its certificate ID. The product name and device type appear once the maker
registers the model in the ledger, often weeks after certification.

In a typical week the ledger records around 70 new certifications: lights, plugs, locks, sensors,
thermostats, robot vacuums and more.

### Who it's for

- **Product and market teams** watching competitors and new entrants in Matter
- **Retail and distribution buyers** looking for newly certified products to stock
- **Smart home app and platform developers** keeping device support lists current
- **Analysts and journalists** covering the smart home market

### Input

- **Look back (days)** or **since a date**: the reporting window. 7 days suits a weekly schedule.
- **Statuses:** certified, provisional and revoked (all three by default).
- **Only these makers:** optional company names or Vendor IDs (`Signify`, `Aqara`, `0x100B`).
- **Only these device types:** optional (`Light`, `Plug`, `Lock`, `Thermostat`). Only rows whose model
  is registered have a device type, so this filter leaves out certifications that don't have one yet.
- **Maximum results:** an optional cap per run.

### Output

One row per certification record, newest first: date, status, maker (preferred and legal name,
Vendor ID), Product ID, software version, Matter version, transport (Wi-Fi, Thread, Ethernet,
Bluetooth), certificate ID, certification route, family ID and revocation reason.

The product name, label, part number, device type and the maker's support and product links come
from the model record, so they appear once the maker registers the model in the ledger, often weeks
after certification, and some makers never register theirs. Until then those fields are empty; in a
weekly run that's often most rows. The Vendor ID and Product ID are always there.

### Schedule it

In Apify Console, open **Schedules**, create one (for example every Monday at 9:00), and add this
Actor with `Look back (days)` = 7. Connect the dataset to Slack, email, Google Sheets or a webhook
with Apify's integrations.

### Pricing

**$0.003 per certification reported** ($3 per 1,000), charged per certification row, whether or not
the model is registered yet. A weekly run usually costs under $0.50. Platform usage is included.

### Notes

- Data is read live from the public DCL (`on.dcl.csa-iot.org`). Nothing is stored beyond your run's dataset.
- Not affiliated with the Connectivity Standards Alliance.
- Need one device looked up instead? Use [Matter Device Lookup](https://apify.com/firedanceio/matter-device-lookup).
  For AI assistants, there's the [Matter DCL MCP Server](https://apify.com/firedanceio/matter-dcl-mcp).
- Built by [Firedance](https://firedance.io), who make FirePod, a speaker that syncs smart lights to music.
  The ledger client is open source: [matter_dcl](https://github.com/firedanceio/matter_dcl) and
  [matter-dcl-mcp](https://github.com/firedanceio/matter-dcl-mcp).

# Actor input Schema

## `sinceDays` (type: `integer`):

Report certifications dated in the last N days. 7 suits a weekly schedule.

## `sinceDate` (type: `string`):

Report everything dated on or after this day instead (YYYY-MM-DD). Overrides the look-back.

## `statuses` (type: `array`):

Which certification statuses to report. Leave empty for all three.

## `vendors` (type: `array`):

Optional. Company names or Vendor IDs to keep, e.g. Signify, Aqara or 0x100B. Matches part of the name.

## `deviceTypes` (type: `array`):

Optional. Device types to keep, e.g. Light, Plug, Lock, Thermostat. Matches part of the type name.

## `maxItems` (type: `integer`):

Optional cap on the number of rows (and charges) per run. 0 means no cap.

## `network` (type: `string`):

The production ledger (mainnet) or the test ledger (testnet).

## Actor input object example

```json
{
  "sinceDays": 7,
  "statuses": [
    "certified",
    "provisional",
    "revoked"
  ],
  "maxItems": 0,
  "network": "mainnet"
}
```

# Actor output Schema

## `certifications` (type: `string`):

No description

## `allFields` (type: `string`):

No description

# 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 = {
    "sinceDays": 7
};

// Run the Actor and wait for it to finish
const run = await client.actor("firedanceio/matter-certification-tracker").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 = { "sinceDays": 7 }

# Run the Actor and wait for it to finish
run = client.actor("firedanceio/matter-certification-tracker").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 '{
  "sinceDays": 7
}' |
apify call firedanceio/matter-certification-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,firedanceio/matter-certification-tracker"
        }
    }
}
```

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/4R0hyG3GWc6e3bC10/builds/t760fA4PZbdvQBY5M/openapi.json