[Integrations](https://spiral.ai/integrations) › [Muse Code](https://spiral.ai/integrations/muse-code) › [Railway documentation page](https://spiral.ai/integrations/muse-code/railway-documentation-page)

# How to Use Railway documentation page in Muse Code

Read a Railway documentation page covering deployment behavior, databases, networking, or development tools. Use it for technical requirements and documented behavior rather than announcement summaries.

|  |  |
| --- | --- |
| Model | Railway documentation page |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Railway documentation page in Muse Code

- Use Railway documentation page to read https://docs.railway.com/cron-jobs and compare the documented job behavior with the scheduled worker in this repository.
- Use Railway documentation page to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from Railway documentation page and tell me what changed since last week.
- Check Railway documentation page and summarize what you find in three bullet points.
- Pull the newest data from Railway documentation page and give me the result as a table.

## How to set up Railway documentation page 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 Railway documentation page**: 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": "railway-com/developer-documentation/get_doc_page",
    "input": {
      "path": "<path>"
    }
  }'
```

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

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

## Railway documentation page tools and prices

- [Railway · Get doc page](https://spiral.ai/tools/alexandria/railway-com/developer-documentation/get_doc_page) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | Alternatively a docs URL, e.g. https://docs.railway.com/cron-jobs. Pattern: ^https?://. |
| path |  | — | Page path such as `cron-jobs` or `guides/rails`; a leading slash and `.md` are accepted. |
| max_chars | 200 to 2000000 | — | Cut `content` to this many characters. The whole document is returned when omitted. |

## What can you do with Railway documentation page in Muse Code?

Produce a Railway deployment review tied to your application's requirements. Use retrieved Railway material to check hosting assumptions, template choices, published changes, or operational risks against the project.

### Plan a migration to Railway

Build a migration brief from technical requirements, relevant engineering articles, recent product changes, deployment candidates, plan limits, and applicable policies.

### Review deployment readiness

Check the proposed template, documented behavior, resource ceilings, policies, and recent announcements. Add current platform status and relevant incident timelines to the release review.

### Prepare a platform review

Evaluate Railway against a team's hosting requirements using public technical guidance, plan limits, policies, template options, product updates, and reliability reports.

### Create an internal Railway reading guide

Select technical docs, engineering explanations, recent updates, policies, plan comparisons, and example templates for developers learning how their team uses Railway.

### Reconstruct a public outage

Find the engineering write-up, compare it with the status timeline, and explain the affected components using Railway's documentation and uptime methodology.

### Improve an incident runbook

Use reported platform status, incident updates, past engineering reports, technical docs, and announced fixes to identify which checks belong in a Railway troubleshooting runbook.

### Choose a deployment template

Compare category listings, inspect the services packaged in promising templates, and check their requirements against documentation, plan limits, and applicable policies.

### Prepare a Railway change briefing

Summarize relevant engineering articles and product updates, then identify documentation, template choices, plan assumptions, or policy references the team should review.

## Overview

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

## Railway documentation page in other agents

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

## More Muse Code guides

- [Railway documentation index](https://spiral.ai/integrations/muse-code/railway-documentation-index)
- [Railway incident history](https://spiral.ai/integrations/muse-code/railway-incident-history)
- [Railway deployment templates](https://spiral.ai/integrations/muse-code/railway-deployment-templates)
- [Railway incident report](https://spiral.ai/integrations/muse-code/railway-incident-report)
- [Railway deployment template](https://spiral.ai/integrations/muse-code/railway-deployment-template)
- [Railway plans and resource limits](https://spiral.ai/integrations/muse-code/railway-plans-and-resource-limits)

## Questions about Railway documentation page in Muse Code

**Can Muse Code use Railway documentation page?**

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

**How much does Railway documentation page 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 documentation page in Muse Code?**

No. Spiral runs Railway documentation page 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 documentation page 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 documentation page runs?**

Railway documentation page 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 docs, blog articles, changelog entries, status reports, deployment templates, and company and legal pages. Template coverage includes machine-readable deployment manifests.

**Does Railway report every outage?**

No. Railway explicitly limits its status page to incidents with significant, widespread user impact and says smaller or isolated issues will not appear.

**What period do Railway's uptime figures cover?**

Component uptime covers the last 90 days plus today. Major outages count fully as downtime, while partial outages count at 30%.

**How often does Railway publish product updates?**

Railway labels its changelog as weekly product updates since 2021. Individual entries carry dates and include feature announcements and fixes.

**What does an individual incident report contain?**

Railway status reports identify affected components and show timestamped updates. For example, incident IFBXJTGG records monitoring and resolution updates for public networking across four regions.

