Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Developer

How to Use Railway incident history in Muse Code

Find published Railway incident reports to investigate platform disruptions. Use the results to identify relevant incidents, keeping in mind that the status page says smaller or isolated issues may be omitted.

Prompts to try with Railway incident history in Muse Code

Copy an example into Muse Code, or ask in your own words.

Use Railway incident history to find published build incidents and compare the returned reports with the deployment failure dates in this project's troubleshooting notes.

Railway incident historyMuse Code
Try asking
  • Use Railway incident history to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from Railway incident history and tell me what changed since last week.

  • Check Railway incident history and summarize what you find in three bullet points.

  • Pull the newest data from Railway incident history and give me the result as a table.

How to set up Railway incident history in Muse Code

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

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    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.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run Railway incident history

    One request; the result comes back by polling or a webhook.

    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": "railway-com/developer-documentation/list_incidents",
        "input": {
          "q": "<q>"
        }
      }'

Then paste one of the prompts above: Muse Code finds Railway incident history on Spiral, shows the price and runs it.

Railway incident history providers and prices

Spiral runs Railway incident history through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
Railway · List incidents
railway-com/developer-documentation/list_incidents

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Limit1 to 30

Maximum records, 1-30. Defaults to 30.

Stateall, active, or resolved

Which incidents to keep. Defaults to all.

Every API field of Railway · List incidents is on its tool page: open its card above.

What can you do with Railway incident history in Muse Code?

Build a Railway deployment review that matches the repository's framework and services. A coding agent can collect documentation links, announcements, incident references, or template candidates and use them to guide its next inspection.

Prepare a production readiness review

Gather Railway documentation links, relevant product announcements, published incidents, and candidate templates for a Django and Postgres application. Turn the findings into questions to resolve before launch.

Investigate deployment failures

Find Railway deployment guidance, announcements about build changes, and published build incidents. Use the results to decide which documentation or incident report deserves a closer read.

Evaluate hosting n8n

Shortlist n8n deployment templates, find networking and storage guidance, and review relevant Railway announcements and incidents. Assemble the evidence needed to assess hosting requirements.

Assess a migration from Heroku

Collect Railway migration documentation, starter templates for the application's framework, recent product announcements, and published incident history. Use them to build a migration review agenda.

Create a weekly Railway maintenance brief

Collect new product announcements and published incidents alongside documentation links and template candidates for the team's stack. Highlight items that warrant a technical review.

Prepare platform incident triage

Identify published Railway incidents and locate documentation for the affected service area. Add relevant product announcements as investigation leads without assuming they caused the disruption.

Questions about Railway incident history in Muse Code

Can Muse Code use Railway incident history?

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run Railway incident history like any built-in tool.

How much does Railway incident history 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 Railway incident history in Muse Code?

No. Spiral runs Railway incident history on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up Railway incident history in Muse Code?

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

Does Muse Code wait while Railway incident history runs?

Railway incident history runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

What Railway information does this source cover?

It covers public Railway content, including documentation, product announcements, published incidents, and deployment templates. The documentation spans deployment, service configuration, data, networking, observability, and the CLI.

How often does Railway publish product updates?

Railway describes its changelog as weekly product updates, with coverage dating back to 2021. Entries are dated, so you can identify the announcement period for a feature.

Does Railway's incident history include every service problem?

The status page says it covers significant, widespread user impact and excludes smaller or isolated issues. An empty incident search therefore cannot establish that a particular application had no problems.

When does Railway's reported incident duration begin?

Railway counts an incident from when it publishes the incident to when it resolves it. That interval should not be treated as a measurement of when every affected application's symptoms began.

What does a Railway deployment template represent?

A template packages a service or set of services into a reusable configuration. Marketplace results include named software templates with descriptions, such as n8n with workers.

Get started

Start using Railway incident history in Muse Code

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse Code:

Set up Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options