[Integrations](https://spiral.ai/integrations) › [Muse Code](https://spiral.ai/integrations/muse-code) › [CER pipeline incidents](https://spiral.ai/integrations/muse-code/cer-pipeline-incidents)

# How to Use CER pipeline incidents in Muse Code

Returns reported incidents at federally regulated pipelines and facilities, including incident details and review status. Use it to examine safety history since 2008 and distinguish preliminary reports from reviewed records.

|  |  |
| --- | --- |
| Model | CER pipeline incidents |
| Available through | Alexandria |
| Category | Industry Data |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with CER pipeline incidents in Muse Code

- Use CER pipeline incidents to create a Trans Mountain incident timeline for 2020 through 2025, showing incident details and review status.
- Use CER pipeline incidents to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from CER pipeline incidents and tell me what changed since last week.
- Check CER pipeline incidents and summarize what you find in three bullet points.
- Pull the newest data from CER pipeline incidents and give me the result as a table.

## How to set up CER pipeline incidents in Muse Code

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Install Muse Code**

```bash
curl -fsSL https://dev.meta.ai/install.sh | bash
```

2. **Ask Muse to add the server**: Start `muse` and ask:

```text
Add the Spiral MCP server at https://api.spiral.ai/mcp
```

3. **Sign in**: In your terminal, run:

```bash
muse mcp login spiral
```

### Use the Spiral skill

1. **Send Muse Code this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run CER pipeline incidents**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "cer-rec-gc-ca/energy-data/incidents",
    "input": {
      "to": "<to>"
    }
  }'
```

Then paste one of the prompts above: Muse Code finds CER pipeline incidents on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/muse-code

## CER pipeline incidents tools and prices

- [Canada Energy Regulator (CER) open data · Incidents](https://spiral.ai/tools/alexandria/cer-rec-gc-ca/energy-data/incidents) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| to |  | — | Latest date: `YYYY`, `YYYY-MM` or `YYYY-MM-DD` (a year or month means its last day). Pattern: ^\d{4}(-\d{2}(-\d{2})?)?$. |
| from |  | — | Earliest date: `YYYY`, `YYYY-MM` or `YYYY-MM-DD`. Pattern: ^\d{4}(-\d{2}(-\d{2})?)?$. |
| limit | 1 to 100 | 25 | Rows per page. |
| query |  | — | Words that must all appear in what or why it happened, nearest town, pipeline or facility name. |
| offset | 0 to … | 0 | `next_offset` from the previous page; repeat the other inputs with it. |
| status |  | — | status |

## What can you do with CER pipeline incidents in Muse Code?

Build a Canadian energy research view that brings CER observations, scenarios, or regulatory records into your project. Add comparisons for named provinces or pipeline systems while preserving the source’s units and dates.

### Trans Mountain oversight briefing

Prepare a pipeline briefing combining system context, throughput, benchmark tolls, reported incidents, and issued regulatory instruments. Keep each timeline separate so coincident events are not presented as proven causes.

### Energy outlook evidence pack

Build a Canadian energy outlook with scenario comparisons and reported trade, accompanied by incident and regulatory timelines for the infrastructure discussed.

### Pipeline safety research

Compare reported incident histories for selected federally regulated systems, using pipeline profiles and throughput for operating context and regulatory instruments for related documentary research.

### Quarterly Canadian energy research update

Refresh a research brief with trade observations, pipeline flows, toll records, incidents, and regulatory instruments. Revisit system profiles and energy scenarios when the source publishes changes.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Muse Code guides](https://spiral.ai/integrations/muse-code)

## CER pipeline incidents in other agents

- [Amp](https://spiral.ai/integrations/amp/cer-pipeline-incidents)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/cer-pipeline-incidents)
- [Claude](https://spiral.ai/integrations/claude-desktop/cer-pipeline-incidents)
- [Claude Code](https://spiral.ai/integrations/claude-code/cer-pipeline-incidents)
- [Cline](https://spiral.ai/integrations/cline/cer-pipeline-incidents)
- [Codex](https://spiral.ai/integrations/codex/cer-pipeline-incidents)
- [Cursor](https://spiral.ai/integrations/cursor/cer-pipeline-incidents)
- [Devin](https://spiral.ai/integrations/devin/cer-pipeline-incidents)
- [dots](https://spiral.ai/integrations/dots/cer-pipeline-incidents)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/cer-pipeline-incidents)
- [Gemini](https://spiral.ai/integrations/gemini/cer-pipeline-incidents)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/cer-pipeline-incidents)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/cer-pipeline-incidents)
- [goose](https://spiral.ai/integrations/goose/cer-pipeline-incidents)
- [Grok](https://spiral.ai/integrations/grok/cer-pipeline-incidents)
- [Grok Build](https://spiral.ai/integrations/grok-build/cer-pipeline-incidents)
- [Hermes](https://spiral.ai/integrations/hermes/cer-pipeline-incidents)
- [Instinct](https://spiral.ai/integrations/instinct/cer-pipeline-incidents)
- [Manus](https://spiral.ai/integrations/manus/cer-pipeline-incidents)
- [Muse](https://spiral.ai/integrations/muse/cer-pipeline-incidents)
- [n8n](https://spiral.ai/integrations/n8n/cer-pipeline-incidents)
- [Notion](https://spiral.ai/integrations/notion/cer-pipeline-incidents)
- [OpenClaw](https://spiral.ai/integrations/openclaw/cer-pipeline-incidents)
- [opencode](https://spiral.ai/integrations/opencode/cer-pipeline-incidents)
- [Perplexity](https://spiral.ai/integrations/perplexity/cer-pipeline-incidents)
- [Raycast](https://spiral.ai/integrations/raycast/cer-pipeline-incidents)
- [VS Code](https://spiral.ai/integrations/vscode/cer-pipeline-incidents)
- [Windsurf](https://spiral.ai/integrations/windsurf/cer-pipeline-incidents)
- [Zapier](https://spiral.ai/integrations/zapier/cer-pipeline-incidents)

## More Muse Code guides

- [CER energy statistics](https://spiral.ai/integrations/muse-code/cer-energy-statistics)
- [CER pipeline profiles](https://spiral.ai/integrations/muse-code/cer-pipeline-profiles)
- [CER energy projections](https://spiral.ai/integrations/muse-code/cer-energy-projections)
- [CER pipeline throughput](https://spiral.ai/integrations/muse-code/cer-pipeline-throughput)
- [CCEL work table of contents](https://spiral.ai/integrations/muse-code/ccel-work-table-of-contents)
- [CER pipeline tolls](https://spiral.ai/integrations/muse-code/cer-pipeline-tolls)

## Questions about CER pipeline incidents in Muse Code

**Can Muse Code use CER pipeline incidents?**

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run CER pipeline incidents like any built-in tool.

**How much does CER pipeline incidents cost in Muse Code?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.

**Do I need an Alexandria account to use CER pipeline incidents in Muse Code?**

No. Spiral runs CER pipeline incidents on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up CER pipeline incidents in Muse Code?**

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

**Does Muse Code wait while CER pipeline incidents runs?**

CER pipeline incidents runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

**Does CER pipeline data cover every pipeline in Canada?**

CER regulates pipelines crossing provincial boundaries or the Canada-U.S. border. Its pipeline records therefore have a federal coverage boundary and should not be treated as a complete inventory of Canadian pipelines.

**How often does CER update its pipeline flow information?**

Pipeline Profiles schedule throughput updates quarterly, in March, May, August, and November. Daily natural gas observations describe the measurement frequency, so they do not imply daily publication.

**Are Energy Future results predictions?**

CER describes the results as scenarios for testing assumptions rather than forecasts or predictions. The 2026 edition contains four scenarios, so comparisons should identify which scenario produced each result.

**What geographic coverage does Energy Future provide?**

Energy Future scenarios cover every Canadian province and territory and all energy commodities. The 2026 outlook projects supply and demand through 2050.

**Do CER toll charts include every shipping route?**

CER displays major or benchmark toll paths for illustration. A review of all available paths requires the pipeline’s tariff filing.

