---
type: "firecrawl-provider"
description: "Railway's public content through the sources Railway publishes for agents: the docs index and any docs page as Markdown (docs.railway.com), blog posts (blog.railway.com), live platform status and incident history from the status page's documented JSON API (api.railwaystatus.com, behind status.railway.com), pricing, company and legal pages, the product changelog, and one-click deploy templates with their machine-readable manifests (railway.com). No login or key."
use_when: "Railway's public content through the sources Railway publishes for agents: the docs index and any docs page as Markdown (docs.railway.com), blog posts (blog.railway.com), live platform status and incident history from the status page's documented JSON API (api.railwaystatus.com, behind status.railway.com), pricing, company and legal pages, the product changelog, and one-click deploy templates with their machine-readable manifests (railway.com). No login or key."
categories: "Developer"
capabilities: 14
credits_per_call: 5
---
# Railway on Firecrawl Alexandria

Railway's public content through the sources Railway publishes for agents: the docs index and any docs page as Markdown (docs.railway.com), blog posts (blog.railway.com), live platform status and incident history from the status page's documented JSON API (api.railwaystatus.com, behind status.railway.com), pricing, company and legal pages, the product changelog, and one-click deploy templates with their machine-readable manifests (railway.com). No login or key.

- Categories: Developer
- Category index: [Developer category](https://firecrawl.dev/alexandria/agents/categories/developer)
- Provider key: `railway-com`
- Access: Firecrawl credits
- Cost: 5 credits per call

## More

- [Human guide](https://firecrawl.dev/app/alexandria/railway-com)
- [OpenAPI spec](https://firecrawl.dev/alexandria/agents/providers/railway-com/openapi.json)

## Capabilities

- [Get blog post](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_blog_post): One Railway blog post as Markdown (GET blog.railway.com/p/{slug}.md) with title, description, publication date, authors, category, an outline and the content. Accepts a slug or a post URL. Unknown posts are `not_found`.
- [Get changelog entry](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_changelog_entry): One Railway changelog entry as Markdown (GET railway.com/changelog/{slug}.md) with title, date, entry number, the feature section headings and the content. Accepts a slug or a changelog URL. Unknown entries are `not_found`.
- [Get doc page](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_doc_page): One Railway docs page as clean Markdown (GET docs.railway.com/{path}.md, the docs' agent-facing rendering) with title, description, an outline of headings and the content. Accepts a page path or a docs URL; URLs shared with or without a `reference/` or `guides/` prefix both resolve (the prefixed form is tried first). Unknown pages are `not_found`.
- [Get incident](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_incident): One Railway incident from api.railwaystatus.com/status/incidents/{slug}: title, state, worst impact, timestamps, affected components and every update newest first. Accepts the incident code or a status.railway.com/incident URL. Unknown codes are `not_found`.
- [Get pricing](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_pricing): Railway's current pricing from railway.com/pricing.md (the agent-facing twin of railway.com/pricing): plans with monthly fee, included usage, per-service limits, replicas and log history; per-second usage rates for memory, CPU, volumes, egress and object storage; sandbox VM rates; platform limits by plan; every pricing table as published; and the pricing FAQ.
- [Get site page](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_site_page): One railway.com page as Markdown (GET railway.com/{path}.md): careers, about, free-vm, enterprise, sandboxes, features, customers, mcp, agents and the legal pages (terms, privacy, dpa, acceptable-use, fair-use). The `.md` legal pages are Railway's own navigational summaries; the binding text is the HTML page. Paths disallowed by railway.com's robots.txt (dashboard, project, account and similar) are refused. Unknown pages are `not_found`.
- [Get status](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_status): Current Railway platform status from the status page's documented JSON API (api.railwaystatus.com/status, which backs status.railway.com): every component with its group (platform area or region) and status, the overall worst status, active incidents with affected components and the latest update, and scheduled maintenances.
- [Get template](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_template): One Railway deploy template from its published manifest (railway.com/deploy/{code}/manifest.json): name, description, validation status and 30-day success rate, services with image or repo, volumes and ports, the variables it needs (strategy, default, generated, Railway-provided), the CLI and MCP deploy commands and the latest validation checks. Accepts a code or a railway.com/deploy URL. Unknown codes are `not_found`.
- [List blog posts](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_blog_posts): The Railway blog post index from blog.railway.com/llms.txt: every post with title, slug, URL, Markdown URL, description and category (Engineering, Guide, News, Company, AI, User Stories, Scaling Railway), newest first within each category. Filter by `q` or `category`, page with `limit`/`offset`. Dates and authors come from get_blog_post.
- [List category templates](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_category_templates): Railway deploy templates in one marketplace category (railway.com/deploy/category/{category}.md, e.g. ai, analytics, authentication, automation, blogs, bots, cms, observability, queues, starters, storage), in Railway's listed order: code, name, description, page and manifest URLs, plus the category's stated template count. Filter by `q`, page with `limit`/`offset`. Unknown categories are `not_found`.
- [List changelog](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_changelog): The Railway product changelog index from railway.com/changelog.md: every weekly entry since 2020 with title, date, slug, URL and Markdown URL, newest first. Filter by `q` (title), `since` and `until` (YYYY-MM-DD, inclusive), page with `limit`/`offset`.
- [List docs](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_docs): The Railway docs page index from docs.railway.com/llms.txt: every page with title, path, URL, Markdown URL, description and its navigation section and subsection. Filter by `q` (title, path or description, case-insensitive) or `section` (a section or subsection name such as `Networking` or `Databases`), page with `limit`/`offset`.
- [List incidents](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_incidents): Recent Railway incidents from api.railwaystatus.com/status/incidents (the 30 most recent, newest first; the endpoint takes no paging parameters): code, title, state, worst impact, timestamps, affected components, update count and the latest update. Filter by `state` (active, resolved, all) and `q` (title).
- [Search templates](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/search_templates): Search Railway's one-click deploy templates through the machine-readable template index (railway.com/deploy/llms.txt, about 7,000 templates): code, name, description, validation status (validated, degraded, unvalidated by Railway's validation fleet), page URL and manifest URL. All `q` words must match the name, description or code; exact and prefix name matches rank first. Filter by `status`, page with `limit`/`offset`.

## 1. Choose this provider when

Railway's public content through the sources Railway publishes for agents: the docs index and any docs page as Markdown (docs.railway.com), blog posts (blog.railway.com), live platform status and incident history from the status page's documented JSON API (api.railwaystatus.com, behind status.railway.com), pricing, company and legal pages, the product changelog, and one-click deploy templates with their machine-readable manifests (railway.com). No login or key.

## 2. Minimal request

Call `POST https://api.firecrawl.dev/v2/scrape` with `{ alexandria: { provider, capability, options } }`. For a batch, send `{ alexandria: [...] }` with up to 10 calls.

```json
{
  "provider": "railway-com",
  "capability": "developer-documentation/get_blog_post",
  "options": {
    "max_chars": 1500,
    "slug": "incident-report-sept-30-2026-routing-disruption"
  }
}
```

## 3. Add provider options

Use only the options needed for the task:

- `max_chars` (number): Cut `content` to this many characters. The whole document is returned when omitted. Example: `200`
- `slug` (string): Post slug, e.g. `railway-cdn`. Example: `railway-cdn`
- `url` (string): Alternatively a post URL, e.g. https://blog.railway.com/p/railway-cdn. Pattern: ^https?://. Example: `<url>`

## 4. Request through your preferred interface

### JavaScript

```javascript
const result = await firecrawl.scrape({
  alexandria: {
    provider: "railway-com",
    capability: "developer-documentation/get_blog_post",
    options: {
      max_chars: 1500,
      slug: "incident-report-sept-30-2026-routing-disruption",
    },
  },
});
```

### Python

```python
result = firecrawl.scrape_alexandria({
  "provider": "railway-com",
  "capability": "developer-documentation/get_blog_post",
  "options": {
    "max_chars": 1500,
    "slug": "incident-report-sept-30-2026-routing-disruption"
  }
})
```

### cURL

```sh
curl https://api.firecrawl.dev/v2/scrape \
  -H "Authorization: Bearer $FIRECRAWL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "alexandria": {
    "provider": "railway-com",
    "capability": "developer-documentation/get_blog_post",
    "options": {
      "max_chars": 1500,
      "slug": "incident-report-sept-30-2026-routing-disruption"
    }
  }
}'
```

### CLI

```sh
firecrawl scrape 'railway-com/developer-documentation/get_blog_post' \
  --options '{"max_chars":1500,"slug":"incident-report-sept-30-2026-routing-disruption"}'
```


### MCP

Call the FCX MCP retrieve tool with this object:

```json
{
  "provider": "railway-com",
  "capability": "developer-documentation/get_blog_post",
  "options": {
    "max_chars": 1500,
    "slug": "incident-report-sept-30-2026-routing-disruption"
  }
}
```

Ask for only the returned fields needed by the task.

## 5. Full request shape

```json
{
  "provider": "railway-com",
  "capability": "developer-documentation/get_blog_post",
  "options": {
    "max_chars": 1500,
    "slug": "incident-report-sept-30-2026-routing-disruption"
  }
}
```

## 6. Response data

The response includes `success`, `provider`, `capability`, `creditsCost` and `data`. This example shows the provider payload in `data`:

```json
{
  "authors": [
    "Angelo Saraceno"
  ],
  "category": "Engineering",
  "chars": 7541,
  "content": "# Incident Report: September 30, 2026: Domain Routing Disruption\n\nOn September 30, 2026, domains hosted on Railway returned 404 not found errors for new connections for a five minute period for all customers.\n\nWhile rolling out a change to our distributed routing control plane, the new deployment didn’t wait for the schema updates needed to support new functionality. Our distributed routing control plane is the system that tells our origin proxies how to route user requests to the workloads behind every domain.\n\nBecause of this mismatch, route lookups failed, and any attempt to reach a domain served by Railway-hosted workloads returned an error. During the incident period, our origin proxies treated each failed lookup as if \"this domain doesn't exist\" instead of falling back to the last route it knew.\n\nAfter five minutes of the system automatically reconciling to the intended working state - it restored most traffic; then routing recovered on its own as soon as the schema update finished.\n\n## Impact\n\nOn September 30, 2026, between roughly 07:35 and 07:40 UTC, new connections to domains hosted on Railway (which include custom domains and `*.up.railway.app` domains) returned HTTP 404 in all regions.\n\nPublic access and some private networking lookups between services failed during this window. User service uptime was not impacted, only access as workloads kept running throughout we are able to confirm that no data was lost.\n\n## Incident Timeline\n\n*All times are UTC on September ",
  "date": "2026-09-30T22:42:12.172Z",
  "description": "Railway experienced a platform-wide disruption to domain routing on September 30, 2026. For roughly five minutes, between about 07:35 and 07:40 UTC, new connections to domains hosted on Railway returned 404 errors.",
  "markdown_url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption.md",
  "observed_at_ms": 1792695886426,
  "outline": [
    {
      "level": 2,
      "text": "Impact"
    },
    {
      "level": 2,
      "text": "Incident Timeline"
    },
    {
      "level": 2,
      "text": "What Happened?"
    },
    {
      "level": 3,
      "text": "1) A schema update and a binary rollout in the wrong order"
    },
    {
      "level": 3,
      "text": "2) Joint impact and blast radius"
    },
    {
      "level": 2,
      "text": "Preventative Measures"
    },
    {
      "level": 2,
      "text": "Our Incident Procedure"
    }
  ],
  "slug": "incident-report-sept-30-2026-routing-disruption",
  "title": "Incident Report: September 30, 2026: Domain Routing Disruption",
  "truncated": true,
  "url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption"
}
```

## API reference-derived contract

The following capability contract is generated from the same normalized Alexandria API reference exposed in the API spec.

### Get blog post

- Capability: `developer-documentation/get_blog_post`
- Description: One Railway blog post as Markdown (GET blog.railway.com/p/{slug}.md) with title, description, publication date, authors, category, an outline and the content. Accepts a slug or a post URL. Unknown posts are `not_found`.
- Instructions: To read a Railway blog post in full, such as an incident report, an engineering deep dive or a launch announcement.
- Cost: 5 credits per call
- Capability file: [Get blog post](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_blog_post)

Accepted options:
- `max_chars` (number): Cut `content` to this many characters. The whole document is returned when omitted. Example: `200`
- `slug` (string): Post slug, e.g. `railway-cdn`. Example: `railway-cdn`
- `url` (string): Alternatively a post URL, e.g. https://blog.railway.com/p/railway-cdn. Pattern: ^https?://. Example: `<url>`

Response schema example:
```json
{
  "authors": [
    "Angelo Saraceno"
  ],
  "category": "Engineering",
  "chars": 7541,
  "content": "# Incident Report: September 30, 2026: Domain Routing Disruption\n\nOn September 30, 2026, domains hosted on Railway returned 404 not found errors for new connections for a five minute period for all customers.\n\nWhile rolling out a change to our distributed routing control plane, the new deployment didn’t wait for the schema updates needed to support new functionality. Our distributed routing control plane is the system that tells our origin proxies how to route user requests to the workloads behind every domain.\n\nBecause of this mismatch, route lookups failed, and any attempt to reach a domain served by Railway-hosted workloads returned an error. During the incident period, our origin proxies treated each failed lookup as if \"this domain doesn't exist\" instead of falling back to the last route it knew.\n\nAfter five minutes of the system automatically reconciling to the intended working state - it restored most traffic; then routing recovered on its own as soon as the schema update finished.\n\n## Impact\n\nOn September 30, 2026, between roughly 07:35 and 07:40 UTC, new connections to domains hosted on Railway (which include custom domains and `*.up.railway.app` domains) returned HTTP 404 in all regions.\n\nPublic access and some private networking lookups between services failed during this window. User service uptime was not impacted, only access as workloads kept running throughout we are able to confirm that no data was lost.\n\n## Incident Timeline\n\n*All times are UTC on September ",
  "date": "2026-09-30T22:42:12.172Z",
  "description": "Railway experienced a platform-wide disruption to domain routing on September 30, 2026. For roughly five minutes, between about 07:35 and 07:40 UTC, new connections to domains hosted on Railway returned 404 errors.",
  "markdown_url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption.md",
  "observed_at_ms": 1792695886426,
  "outline": [
    {
      "level": 2,
      "text": "Impact"
    },
    {
      "level": 2,
      "text": "Incident Timeline"
    },
    {
      "level": 2,
      "text": "What Happened?"
    },
    {
      "level": 3,
      "text": "1) A schema update and a binary rollout in the wrong order"
    },
    {
      "level": 3,
      "text": "2) Joint impact and blast radius"
    },
    {
      "level": 2,
      "text": "Preventative Measures"
    },
    {
      "level": 2,
      "text": "Our Incident Procedure"
    }
  ],
  "slug": "incident-report-sept-30-2026-routing-disruption",
  "title": "Incident Report: September 30, 2026: Domain Routing Disruption",
  "truncated": true,
  "url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption"
}
```

### Get changelog entry

- Capability: `developer-documentation/get_changelog_entry`
- Description: One Railway changelog entry as Markdown (GET railway.com/changelog/{slug}.md) with title, date, entry number, the feature section headings and the content. Accepts a slug or a changelog URL. Unknown entries are `not_found`.
- Instructions: To read the details of a Railway changelog entry: the features announced that week and the fixes and improvements list.
- Cost: 5 credits per call
- Capability file: [Get changelog entry](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_changelog_entry)

Accepted options:
- `max_chars` (number): Cut `content` to this many characters. The whole document is returned when omitted. Example: `200`
- `slug` (string): Entry slug, e.g. `2020-10-23` or `2026-09-25-free-vms-without-an-account`. Example: `2020-10-23`
- `url` (string): Alternatively an entry URL, e.g. https://railway.com/changelog/2020-10-23. Pattern: ^https?://. Example: `<url>`

Response schema example:
```json
{
  "chars": 1545,
  "content": "# Vercel Integration, Codespaces, and CLI\n\n# Vercel Integration\n\nRailway can now hook into Vercel to provide your production and preview deploys with access to your railway environments.\n\nThis means that if you add the Postgres plugin to your Railway project, we'll update Vercel with a `DATABASE_URL` connection string, accessible via envvars.\n\nJust tell us which Railway environment to sync, and we'll do the rest.\n\n![](https://cms.railway.com/media/c224041b2f3444b2770b7fa21911062e99f140851a49dd7607f8fa38a13958da.gif)\n\nThis is the first of many integrations to come. We already have a few more\nplanned, but if you'd like a specific integration, please join the\n[Discord](https://discord.gg/xAm2w6g) and let us know.\n\n# Codespaces\n\nRailway is now fully compatible with [Github Codespaces](https://github.com/features/codespaces).\n\nCodespaces allows you to\ndevelop entirely in the cloud. Use Railway to connect to your favorite infrastructure, and deploy straight from codespaces with `railway up`.\n\n![](https://cms.railway.com/media/f2ea452147b015e892a12a9fa43299edca98aa702cb0001aff55c641bb4b5fb9.png)\n\nAbove is our [Railway Images](https://github.com/railwayapp/railway-images) starter, which uses Prisma and Railway to host a simple image grid, using Railway's Postgres as a backend. Live now on [Vercel](https://railway-images-vercel.vercel.app/)\n\n# Improved UI/UX of CLI\n\nThe CLI comes new and improved in this update, featuring:\n\n- 🌈 Added colours\n- 🚨 Better error messages\n- 🌍 Support for `railway login` in SSH or codespaces terminals",
  "date": "2020-10-23T00:00:00.000Z",
  "markdown_url": "https://railway.com/changelog/2020-10-23.md",
  "number": 2,
  "observed_at_ms": 1792695886440,
  "sections": [
    "Vercel Integration",
    "Codespaces",
    "Improved UI/UX of CLI"
  ],
  "slug": "2020-10-23",
  "title": "Vercel Integration, Codespaces, and CLI",
  "truncated": false,
  "url": "https://railway.com/changelog/2020-10-23"
}
```

### Get doc page

- Capability: `developer-documentation/get_doc_page`
- Description: One Railway docs page as clean Markdown (GET docs.railway.com/{path}.md, the docs' agent-facing rendering) with title, description, an outline of headings and the content. Accepts a page path or a docs URL; URLs shared with or without a `reference/` or `guides/` prefix both resolve (the prefixed form is tried first). Unknown pages are `not_found`.
- Instructions: To read primary Railway documentation: deployments, builds, variables, volumes, databases, networking, domains, the CLI, pricing and the public API.
- Cost: 5 credits per call
- Capability file: [Get doc page](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_doc_page)

Accepted options:
- `max_chars` (number): Cut `content` to this many characters. The whole document is returned when omitted. Example: `200`
- `path` (string): Page path such as `cron-jobs` or `guides/rails`; a leading slash and `.md` are accepted. Example: `cron-jobs`
- `url` (string): Alternatively a docs URL, e.g. https://docs.railway.com/cron-jobs. Pattern: ^https?://. Example: `<url>`

Response schema example:
```json
{
  "chars": 12382,
  "content": "Railway plans and pricing are designed to give you maximum resources while only charging you for your usage. We charge a base subscription price, which goes towards your resources and usage.\n\n## Plans\n\nRailway offers four plans in addition to a [Trial](/pricing/free-trial):\n\n|                |                                                                                                                                                    |\n| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Free**       | For running small apps with $1 of free credit per month                                                                                             |\n| **Hobby**      | For indie hackers and developers to build and deploy personal projects                                                                             |\n| **Pro**        | For professional developers and their teams shipping to production                                                                                 |\n| **Enterprise** | For teams building and deploying production applications with the need for enterprise features related to compliance, SLAs, and account management |\n\n### Subscription pricing\n\nEach Railway account needs an active subscription. The base subscription fee allows you to use the Railway platform and features included in the tier of your subscription. The subscription",
  "description": "Learn about Railway's plans and pricing.",
  "markdown_url": "https://docs.railway.com/pricing/plans.md",
  "observed_at_ms": 1792695886414,
  "outline": [
    {
      "level": 2,
      "text": "Plans"
    },
    {
      "level": 3,
      "text": "Subscription pricing"
    },
    {
      "level": 3,
      "text": "Default plan resources"
    },
    {
      "level": 3,
      "text": "Resource usage pricing"
    },
    {
      "level": 3,
      "text": "VM pricing"
    },
    {
      "level": 2,
      "text": "Included usage"
    },
    {
      "level": 3,
      "text": "Additional services"
    },
    {
      "level": 2,
      "text": "Image retention policy"
    },
    {
      "level": 2,
      "text": "One-time Grant of Credits on the Free Trial"
    },
    {
      "level": 2,
      "text": "Partial month charges"
    },
    {
      "level": 2,
      "text": "FAQs"
    },
    {
      "level": 3,
      "text": "Which plan is right for me?"
    },
    {
      "level": 3,
      "text": "Can I upgrade or downgrade at any time?"
    },
    {
      "level": 3,
      "text": "What is the difference between subscription and resource usage?"
    },
    {
      "level": 3,
      "text": "Can I add collaborators to my project?"
    },
    {
      "level": 3,
      "text": "How long does Railway keep my volume data if I am no longer on a paid plan?"
    },
    {
      "level": 3,
      "text": "Is the hobby plan free?"
    },
    {
      "level": 3,
      "text": "Can I get the hobby plan subscription fee waived?"
    },
    {
      "level": 3,
      "text": "I prefer to prepay. Is that possible?"
    },
    {
      "level": 3,
      "text": "What happens if I use credits as a payment method and my account runs out of credits?"
    },
    {
      "level": 3,
      "text": "Why was I charged for a partial month of usage?"
    }
  ],
  "path": "pricing/plans",
  "title": "Pricing Plans",
  "truncated": true,
  "url": "https://docs.railway.com/pricing/plans"
}
```

### Get incident

- Capability: `developer-documentation/get_incident`
- Description: One Railway incident from api.railwaystatus.com/status/incidents/{slug}: title, state, worst impact, timestamps, affected components and every update newest first. Accepts the incident code or a status.railway.com/incident URL. Unknown codes are `not_found`.
- Instructions: To read the full timeline of a Railway incident, e.g. what was affected, when it was identified and when it was resolved.
- Cost: 5 credits per call
- Capability file: [Get incident](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_incident)

Accepted options:
- `slug` (string): Incident code, e.g. `IFBXJTGG` (case-insensitive). Example: `<slug>`
- `url` (string): Alternatively an incident URL, e.g. https://status.railway.com/incident/IFBXJTGG. Pattern: ^https?://. Example: `<url>`

Response schema example:
```json
{
  "components": [
    {
      "group": "US East (Virginia, USA)",
      "id": "90ea440b-950e-401f-a13d-00394cb44c66",
      "impact": "MAJOR_OUTAGE",
      "name": "Networking — Public"
    },
    {
      "group": "US West (California, USA)",
      "id": "5cdc7232-4592-4485-9e6c-1727853dbcd6",
      "impact": "MAJOR_OUTAGE",
      "name": "Networking — Public"
    },
    {
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "7c64e6e4-5f08-4c90-b337-94f590ff55b5",
      "impact": "MAJOR_OUTAGE",
      "name": "Networking — Public"
    },
    {
      "group": "Southeast Asia (Singapore)",
      "id": "3dab8031-9369-40bb-b5d5-c87b8bce91eb",
      "impact": "MAJOR_OUTAGE",
      "name": "Networking — Public"
    }
  ],
  "created_at": "2026-09-30T07:34:39.721+00:00",
  "id": "f2daa9bd-6812-4fde-b8ad-5348a59824d4",
  "latest_update": {
    "created_at": "2026-09-30T08:17:53.005116+00:00",
    "id": "585ae823-bd35-47e8-ad28-fa77cae0b78a",
    "message": "The global routing service provided a `not-found` response after a rollout of a network config change. The system self healed after the config change led to errors. Unfortunately, this led to observed impact to new connections to Railway hosted workloads for 5 minutes. There is no further and ongoing impact. The Networking team will be working on a full root cause and we will update this status report with a published cause.",
    "status": "RESOLVED"
  },
  "observed_at_ms": 1792695886433,
  "resolved_at": "2026-09-30T07:57:53.005+00:00",
  "slug": "IFBXJTGG",
  "source_url": "https://api.railwaystatus.com/status/incidents/IFBXJTGG",
  "status": "RESOLVED",
  "title": "Domain routing disruption",
  "update_count": 2,
  "updated_at": "2026-09-30T08:17:53.005116+00:00",
  "updates": [
    {
      "created_at": "2026-09-30T08:17:53.005116+00:00",
      "id": "585ae823-bd35-47e8-ad28-fa77cae0b78a",
      "message": "The global routing service provided a `not-found` response after a rollout of a network config change. The system self healed after the config change led to errors. Unfortunately, this led to observed impact to new connections to Railway hosted workloads for 5 minutes. There is no further and ongoing impact. The Networking team will be working on a full root cause and we will update this status report with a published cause.",
      "status": "RESOLVED"
    },
    {
      "created_at": "2026-09-30T07:48:39.721111+00:00",
      "id": "95ca2f69-ac13-4fbf-9d8e-a8c4eb53dc5a",
      "message": "We are aware of an issue that caused domains hosted on Railway to return 404 errors. The issue lasted approximately 5 minutes and has since been mitigated, this is a post facto report. \n\nWe are investigating the root cause and will provide updates as we learn more.",
      "status": "MONITORING"
    }
  ],
  "url": "https://status.railway.com/incident/IFBXJTGG",
  "worst_impact": "MAJOR_OUTAGE"
}
```

### Get pricing

- Capability: `developer-documentation/get_pricing`
- Description: Railway's current pricing from railway.com/pricing.md (the agent-facing twin of railway.com/pricing): plans with monthly fee, included usage, per-service limits, replicas and log history; per-second usage rates for memory, CPU, volumes, egress and object storage; sandbox VM rates; platform limits by plan; every pricing table as published; and the pricing FAQ.
- Instructions: To answer what Railway costs: plan fees (Free, Hobby, Pro, Enterprise), what is included, per-GB and per-vCPU rates, and plan limits. For billing mechanics in depth read the docs page `pricing/plans` with get_doc_page.
- Cost: 5 credits per call
- Capability file: [Get pricing](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_pricing)

Accepted options:

Response schema example:
```json
{
  "description": "Pay only for what your app uses, by the second. No overprovisioning, no idle markup.",
  "faq": [
    {
      "answer": "Hobby is for indie hackers and developers to build and deploy personal projects. Pro is for professional developers and their teams shipping to production. Enterprise is for dev teams building and deploying production applications with large replica size, SLA, and/or compliance needs.",
      "question": "Which plan is right for me?"
    },
    {
      "answer": "If you do not already have a Railway account, you can sign up for a free Trial by clicking Login on railway.com.",
      "question": "How do I get started with the free Trial?"
    },
    {
      "answer": "When you sign up for the free Trial, you will receive a one-time grant of $5 in credits that you can use to try out Railway. The credits will be applied towards any usage on the platform and expire in 30 days. If you upgrade to a plan while you still have a credit balance from the trial, the remaining balance will carry over to your new plan.",
      "question": "How does the Trial work?"
    },
    {
      "answer": "Your Hobby plan subscription includes $5 of usage per month. If your total usage at the end of your billing period is $5 or less, you will not be charged extra for usage. If your total usage exceeds $5 in any given billing period, you will be charged total usage.",
      "question": "How does the Hobby plan included usage work?"
    },
    {
      "answer": "Included usage is reset at the end of every billing cycle and does not accumulate over time.",
      "question": "Does included usage on Hobby accumulate?"
    },
    {
      "answer": "Sandboxes run on Railway's VM primitive and bill on VM rates: $50 per GB of memory per month and $50 per vCPU per month, metered per second, plus $0.05 per GB of egress. You pay for the CPU a sandbox actually uses and the memory it holds while running, not for wall-clock uptime, so a sandbox waiting on a model or a user costs almost nothing. Destroyed sandboxes cost nothing, and an idle timeout destroys forgotten ones automatically. Sandbox usage draws from the same included credit as the rest of your plan.",
      "question": "How are sandboxes billed?"
    },
    {
      "answer": "When you make a payment, you will receive an email with your invoice and receipt attached. You can also find your billing history in Account > Billing.",
      "question": "How can I get a receipt?"
    },
    {
      "answer": "Head to Account > Billing and click 'Manage Subscription'. From there, you can update your billing information, including billing address and Tax ID.",
      "question": "How to add company details on my invoice?"
    },
    {
      "answer": "Railway accepts credit cards for plan subscriptions and usage. We support invoice payments for customers on the Enterprise plan.",
      "question": "What payment methods are accepted?"
    },
    {
      "answer": "Yes. As a new Railway user, you can sign up for a free Trial. You will receive a one-time grant of $5 to use on resources.",
      "question": "Can I try Railway without a credit card?"
    },
    {
      "answer": "You can upgrade any time, and when you do, you will get to the features of your new plan, as well as access to more powerful resources, immediately. When you downgrade, the changes will take effect at the beginning of your next billing cycle.",
      "question": "Can I upgrade or downgrade at any time?"
    },
    {
      "answer": "When you cancel your subscription, if you're on Hobby or Pro, your plan will remain active through the end of your current billing period, and any usage will be charged at the end of the period. If you are on the Hobby plan and using prepaid credits as your payment method, your subscription will be canceled immediately and any credit balance you may have will be forfeited.",
      "question": "What happens when I cancel my subscription?"
    }
  ],
  "observed_at_ms": 1792695886490,
  "plans": [
    {
      "included_usage": "$5 one-time credit (30 days)",
      "log_history": "7 days",
      "max_per_service": "2 vCPU / 1 GB",
      "monthly_fee": "$0",
      "plan": "Free Trial",
      "replicas": "2"
    },
    {
      "included_usage": "$1/month",
      "log_history": "3 days",
      "max_per_service": "1 vCPU / 0.5 GB",
      "monthly_fee": "$0",
      "plan": "Free",
      "replicas": "1"
    },
    {
      "included_usage": "$5/month",
      "log_history": "7 days",
      "max_per_service": "48 vCPU / 48 GB",
      "monthly_fee": "$5",
      "plan": "Hobby",
      "replicas": "6"
    },
    {
      "included_usage": "$20/month",
      "log_history": "30 days",
      "max_per_service": "1,000 vCPU / 1 TB",
      "monthly_fee": "$20",
      "plan": "Pro",
      "replicas": "42"
    },
    {
      "included_usage": "Custom",
      "log_history": "Custom",
      "max_per_service": "Custom",
      "monthly_fee": "Custom",
      "plan": "Enterprise",
      "replicas": "Custom"
    }
  ],
  "platform_limits": [
    {
      "concurrent_builds": "3",
      "custom_domains": "1",
      "max_volume_size": "500 MB",
      "members_per_project": "3",
      "plan": "Free Trial",
      "projects": "2",
      "services": "5"
    },
    {
      "concurrent_builds": "1",
      "custom_domains": "0",
      "max_volume_size": "500 MB",
      "members_per_project": "1",
      "plan": "Free",
      "projects": "1",
      "services": "3"
    },
    {
      "concurrent_builds": "3",
      "custom_domains": "2",
      "max_volume_size": "5 GB",
      "members_per_project": "3",
      "plan": "Hobby",
      "projects": "50",
      "services": "50"
    },
    {
      "concurrent_builds": "10",
      "custom_domains": "20",
      "max_volume_size": "1000 GB",
      "members_per_project": "Unlimited",
      "plan": "Pro",
      "projects": "100",
      "services": "100"
    }
  ],
  "sandbox_rates": [
    {
      "per_month": null,
      "rate": "$0.00001929 per GB/s",
      "resource": "Memory"
    },
    {
      "per_month": null,
      "rate": "$0.00001929 per vCPU/s (active use)",
      "resource": "CPU"
    },
    {
      "per_month": null,
      "rate": "$0.05 per GB",
      "resource": "Egress"
    }
  ],
  "source_url": "https://railway.com/pricing.md",
  "tables": [
    {
      "columns": [
        "Plan",
        "Monthly fee",
        "Included usage",
        "Max per service",
        "Replicas",
        "Log history"
      ],
      "rows": [
        [
          "Free Trial",
          "$0",
          "$5 one-time credit (30 days)",
          "2 vCPU / 1 GB",
          "2",
          "7 days"
        ],
        [
          "Free",
          "$0",
          "$1/month",
          "1 vCPU / 0.5 GB",
          "1",
          "3 days"
        ],
        [
          "Hobby",
          "$5",
          "$5/month",
          "48 vCPU / 48 GB",
          "6",
          "7 days"
        ],
        [
          "Pro",
          "$20",
          "$20/month",
          "1,000 vCPU / 1 TB",
          "42",
          "30 days"
        ],
        [
          "Enterprise",
          "Custom",
          "Custom",
          "Custom",
          "Custom",
          "Custom"
        ]
      ],
      "section": "Plans"
    },
    {
      "columns": [
        "Resource",
        "Rate",
        "≈ Per month"
      ],
      "rows": [
        [
          "Memory",
          "$0.00000386 per GB/s",
          "$10 per GB"
        ],
        [
          "CPU",
          "$0.00000772 per vCPU/s",
          "$20 per vCPU"
        ],
        [
          "Volumes",
          "$0.00000006 per GB/s",
          "$0.15 per GB"
        ],
        [
          "Egress",
          "$0.05 per GB (services)",
          "—"
        ],
        [
          "Object Storage",
          "$0.015 per GB-month, free egress",
          "—"
        ]
      ],
      "section": "Usage-based prices"
    },
    {
      "columns": [
        "Resource",
        "Rate",
        "≈ Per month, while running"
      ],
      "rows": [
        [
          "Memory",
          "$0.00001929 per GB/s",
          "$50 per GB"
        ],
        [
          "CPU",
          "$0.00001929 per vCPU/s (active use)",
          "$50 per vCPU"
        ],
        [
          "Egress",
          "$0.05 per GB",
          "—"
        ]
      ],
      "section": "Sandboxes and VMs"
    },
    {
      "columns": [
        "Plan",
        "Running sandboxes per environment",
        "Default size",
        "Maximum size",
        "Default idle timeout",
        "Idle timeout range"
      ],
      "rows": [
        [
          "Free Trial",
          "10",
          "2 vCPU / 2 GB",
          "2 vCPU / 2 GB",
          "5 min",
          "Up to 5 min"
        ],
        [
          "Free",
          "10",
          "2 vCPU / 2 GB",
          "2 vCPU / 2 GB",
          "5 min",
          "Up to 5 min"
        ],
        [
          "Hobby",
          "50",
          "4 vCPU / 4 GB",
          "8 vCPU / 8 GB",
          "30 min",
          "Up to 120 min, or never"
        ],
        [
          "Pro",
          "100",
          "8 vCPU / 8 GB",
          "24 vCPU / 24 GB",
          "30 min",
          "Up to 120 min, or never"
        ],
        [
          "Enterprise",
          "Custom",
          "8 vCPU / 8 GB",
          "Custom",
          "30 min",
          "Up to 120 min, or never"
        ]
      ],
      "section": "Sandboxes and VMs"
    },
    {
      "columns": [
        "Plan",
        "Projects",
        "Services",
        "Members per project",
        "Max volume size",
        "Custom domains",
        "Concurrent builds"
      ],
      "rows": [
        [
          "Free Trial",
          "2",
          "5",
          "3",
          "500 MB",
          "1",
          "3"
        ],
        [
          "Free",
          "1",
          "3",
          "1",
          "500 MB",
          "0",
          "1"
        ],
        [
          "Hobby",
          "50",
          "50",
          "3",
          "5 GB",
          "2",
          "3"
        ],
        [
          "Pro",
          "100",
          "100",
          "Unlimited",
          "1000 GB",
          "20",
          "10"
        ]
      ],
      "section": "Platform limits by plan"
    }
  ],
  "title": "Railway Pricing",
  "url": "https://railway.com/pricing",
  "usage_rates": [
    {
      "per_month": "$10 per GB",
      "rate": "$0.00000386 per GB/s",
      "resource": "Memory"
    },
    {
      "per_month": "$20 per vCPU",
      "rate": "$0.00000772 per vCPU/s",
      "resource": "CPU"
    },
    {
      "per_month": "$0.15 per GB",
      "rate": "$0.00000006 per GB/s",
      "resource": "Volumes"
    },
    {
      "per_month": null,
      "rate": "$0.05 per GB (services)",
      "resource": "Egress"
    },
    {
      "per_month": null,
      "rate": "$0.015 per GB-month, free egress",
      "resource": "Object Storage"
    }
  ]
}
```

### Get site page

- Capability: `developer-documentation/get_site_page`
- Description: One railway.com page as Markdown (GET railway.com/{path}.md): careers, about, free-vm, enterprise, sandboxes, features, customers, mcp, agents and the legal pages (terms, privacy, dpa, acceptable-use, fair-use). The `.md` legal pages are Railway's own navigational summaries; the binding text is the HTML page. Paths disallowed by railway.com's robots.txt (dashboard, project, account and similar) are refused. Unknown pages are `not_found`.
- Instructions: To read a railway.com company, product or legal page such as the careers page (values, perks, how to apply) or the acceptable use policy summary. Use get_pricing for pricing and the changelog and template functions for those sections.
- Cost: 5 credits per call
- Capability file: [Get site page](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_site_page)

Accepted options:
- `max_chars` (number): Cut `content` to this many characters. The whole document is returned when omitted. Example: `200`
- `path` (string): Page path such as `legal/terms`, `careers` or `free-vm`; `.md` is accepted. Example: `legal/terms`
- `url` (string): Alternatively a railway.com URL, e.g. https://railway.com/legal/privacy. Pattern: ^https?://. Example: `<url>`

Response schema example:
```json
{
  "chars": 2299,
  "content": "# Railway Terms of Service\n\nThis page is a navigational summary of Railway's Terms of Service. **The authoritative, binding version is the HTML page at https://railway.com/legal/terms.** Agents should consult that page (or this page rendered with `Accept: text/html`) for the full legal text before drawing any conclusion about rights and obligations.\n\n## What the Terms cover\n\n- **Acceptance.** Using Railway services means you accept these Terms and the related policies linked from them.\n- **Account & access.** Your responsibilities for the security of your Railway account, credentials, and any users you invite.\n- **Services & subscriptions.** The compute, storage, networking, and database services Railway provides, plus billing terms for hobby, pro, and enterprise plans.\n- **Acceptable use.** What you can and cannot run on Railway. See https://railway.com/legal/acceptable-use for the full list of prohibited activities.\n- **Customer content & data.** Ownership of content you upload, the license you grant Railway to host and serve it, and Railway's confidentiality and security commitments.\n- **Privacy.** How Railway handles personal data. See https://railway.com/legal/privacy.\n- **Fees, taxes, refunds.** Billing cadence, payment methods, and refund policy.\n- **Term & termination.** How either party can end the relationship and what happens to your data.\n- **Warranties & disclaimers.** Limits on warranties for the services.\n- **Limitation of liability.** Caps on damages.\n- **Inde",
  "description": null,
  "markdown_url": "https://railway.com/legal/terms.md",
  "observed_at_ms": 1792695886490,
  "outline": [
    {
      "level": 2,
      "text": "What the Terms cover"
    },
    {
      "level": 2,
      "text": "Related policies"
    },
    {
      "level": 2,
      "text": "Open the full Terms"
    }
  ],
  "path": "legal/terms",
  "title": "Terms of Service",
  "truncated": true,
  "url": "https://railway.com/legal/terms"
}
```

### Get status

- Capability: `developer-documentation/get_status`
- Description: Current Railway platform status from the status page's documented JSON API (api.railwaystatus.com/status, which backs status.railway.com): every component with its group (platform area or region) and status, the overall worst status, active incidents with affected components and the latest update, and scheduled maintenances.
- Instructions: To check whether Railway (API, dashboard, builds, deployments, networking, databases, a specific region) is operational or has an active incident right now.
- Cost: 5 credits per call
- Capability file: [Get status](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_status)

Accepted options:

Response schema example:
```json
{
  "affected_count": 6,
  "component_count": 53,
  "components": [
    {
      "description": null,
      "group": "Railway",
      "id": "3986bf05-60cf-4555-bb3d-35edcd71b2c2",
      "name": "Dashboard — railway.com",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Railway",
      "id": "2f6f64ef-7853-45d2-ad5d-ee553211249a",
      "name": "API — backboard.railway.com",
      "status": "PARTIAL_OUTAGE"
    },
    {
      "description": null,
      "group": "Railway",
      "id": "d67c1212-cdeb-4476-81ef-34fa605d5e1f",
      "name": "Support & Community — station.railway.com",
      "status": "MAJOR_OUTAGE"
    },
    {
      "description": null,
      "group": "Railway",
      "id": "c1ac25d3-6858-4b6c-92c7-b6222bb2cb9d",
      "name": "Dev Studio — dev.new",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Observability",
      "id": "75c763da-6e95-4025-a6de-00255bbe7028",
      "name": "Logs",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Observability",
      "id": "3a438799-8199-47a4-920b-93ecbdf8af75",
      "name": "Metrics",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Domains",
      "id": "2c05e271-d758-4bde-82c5-50d5aac9ff48",
      "name": "Registration",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Domains",
      "id": "c9bc57e6-1e1f-4ce4-ad7f-8065e08997e2",
      "name": "Provisioning",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Authentication",
      "id": "e1588b95-4b3d-45b6-afb4-3dfb7404af7d",
      "name": "Login — GitHub",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Authentication",
      "id": "788b0995-26a2-465b-9184-1fefccc64338",
      "name": "Login — Google",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Authentication",
      "id": "52152cd2-ff09-45e4-ab3e-f64ec7672ec8",
      "name": "Login — Emails",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Authentication",
      "id": "193cfe27-c601-4500-bc0a-560c36b09013",
      "name": "Login — Railway OAuth",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": null,
      "id": "fb7831d4-5d6b-4d74-9dc2-49cdcfa7e647",
      "name": "Payments & Billing",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "a83c1eb5-855a-46c3-af2c-da91887cffb9",
      "name": "Builds",
      "status": "MAJOR_OUTAGE"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "855ae123-f205-4228-89b9-7f38d1912f4b",
      "name": "Deployments",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "af433154-48d9-4c21-b50c-3ac8609bbb77",
      "name": "Compute",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "846bac00-2f00-4fdd-b641-31b5eaf75ce8",
      "name": "Storage Buckets",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "90ea440b-950e-401f-a13d-00394cb44c66",
      "name": "Networking — Public",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "8f48a143-8116-49c7-bf59-e320248b1eb7",
      "name": "Networking — Private",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "20518927-83f8-4086-b535-2f95eb444c01",
      "name": "Networking — Outbound Static IPs",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "18c3a264-96e5-41d0-a958-d059bff6a17a",
      "name": "Sandboxes",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US East (Virginia, USA)",
      "id": "46a861f8-ee19-4a06-ab7b-cb9eba8f109e",
      "name": "Storage",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "69b44a29-f7ea-4f65-875e-87496c4de392",
      "name": "Builds",
      "status": "MAJOR_OUTAGE"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "2d3d5456-51aa-4ab8-a83a-7e5273a58c2f",
      "name": "Deployments",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "62e90e91-bad4-4caa-b948-7585c6a6c3f3",
      "name": "Compute",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "8ebd7238-ad06-411a-9a96-11c78d60ca6b",
      "name": "Storage Buckets",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "5cdc7232-4592-4485-9e6c-1727853dbcd6",
      "name": "Networking — Public",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "a22e5c86-a06f-40e4-ab5d-34cc60f9d739",
      "name": "Networking — Private",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "53091d1a-8f31-4c19-9ad9-4b662420a010",
      "name": "Networking — Outbound Static IPs",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "7cba381e-5520-482f-b07c-d83d1b37d83f",
      "name": "Sandboxes",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "US West (California, USA)",
      "id": "9b63a7ce-3e44-412d-ace8-654a9dab6dc7",
      "name": "Storage",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "ccee9c8c-69ff-4dc2-8638-6a64bcffc7fc",
      "name": "Builds",
      "status": "MAJOR_OUTAGE"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "7fcef7e9-ca32-41c2-ba6e-181691976a2d",
      "name": "Deployments",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "936bf995-4e7c-427b-98db-8fc04619e87c",
      "name": "Compute",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "07e9cf1b-3482-43ab-8e2b-7e5acc636da2",
      "name": "Storage Buckets",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "7c64e6e4-5f08-4c90-b337-94f590ff55b5",
      "name": "Networking — Public",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "b2b33c9e-0d5b-46fe-bc36-e62d2046f348",
      "name": "Networking — Private",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "8d375956-b0f5-4ed2-821a-3dedd91b738f",
      "name": "Networking — Outbound Static IPs",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "5ad8063a-4a39-473b-870c-32ebd10e2417",
      "name": "Sandboxes",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "EU West (Amsterdam, Netherlands)",
      "id": "45ad3be1-3518-46b5-9134-5f326538b726",
      "name": "Storage",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "bd296c88-3ed3-4b2a-8889-7410aac865e1",
      "name": "Builds",
      "status": "MAJOR_OUTAGE"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "5aaa8735-8c33-4cc8-b517-abafb707c225",
      "name": "Deployments",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "2b622431-3180-467e-9ad4-e9d21fdb36b6",
      "name": "Compute",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "b073ad1b-b196-4b29-93e7-1bc33b886784",
      "name": "Storage Buckets",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "3dab8031-9369-40bb-b5d5-c87b8bce91eb",
      "name": "Networking — Public",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "ba784db8-db5f-477f-9560-49516b71d470",
      "name": "Networking — Private",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "f1371420-c54e-4960-8c9a-129e65aada9e",
      "name": "Networking — Outbound Static IPs",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "811de6d6-73de-4409-8ac6-02c77102f9a8",
      "name": "Sandboxes",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "Southeast Asia (Singapore)",
      "id": "5909f49a-da40-4053-baac-9ba698606cd4",
      "name": "Storage",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "External & Third-Party Integrations",
      "id": "781f2691-180a-4ab6-a876-33244a259913",
      "name": "GitHub — Auto-Deploys",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "External & Third-Party Integrations",
      "id": "3488ede3-6856-471a-9e1b-cec742247c1e",
      "name": "Image Registry — Dockerhub",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "External & Third-Party Integrations",
      "id": "8c563d3e-17ce-437b-8d39-b410c7e812fe",
      "name": "Image Registry — GitHub (GHCR)",
      "status": "OPERATIONAL"
    },
    {
      "description": null,
      "group": "External & Third-Party Integrations",
      "id": "c2ed9503-075d-44e7-b726-8d12ee122019",
      "name": "Package Registry — npm",
      "status": "OPERATIONAL"
    }
  ],
  "incidents": [
    {
      "components": [
        {
          "group": "US West (California, USA)",
          "id": "69b44a29-f7ea-4f65-875e-87496c4de392",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        },
        {
          "group": "EU West (Amsterdam, Netherlands)",
          "id": "ccee9c8c-69ff-4dc2-8638-6a64bcffc7fc",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        },
        {
          "group": "Southeast Asia (Singapore)",
          "id": "bd296c88-3ed3-4b2a-8889-7410aac865e1",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        },
        {
          "group": "US East (Virginia, USA)",
          "id": "a83c1eb5-855a-46c3-af2c-da91887cffb9",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        },
        {
          "group": "Railway",
          "id": "2f6f64ef-7853-45d2-ad5d-ee553211249a",
          "impact": "PARTIAL_OUTAGE",
          "name": "API — backboard.railway.com"
        },
        {
          "group": "Railway",
          "id": "d67c1212-cdeb-4476-81ef-34fa605d5e1f",
          "impact": "MAJOR_OUTAGE",
          "name": "Support & Community — station.railway.com"
        }
      ],
      "created_at": "2026-10-21T07:24:24.727677+00:00",
      "id": "9bc9a3c0-fe6b-4b95-bd09-9dc1179da308",
      "latest_update": {
        "created_at": "2026-10-22T18:49:33.601892+00:00",
        "id": "00e65636-ebf7-4a17-bf96-7730cc500c0b",
        "message": "Deployments in US West are working normally again. If a deployment in US West failed after its build completed, please redeploy the service.\n\nBuilds and deployments for Pro and Enterprise workspaces continue to run normally, and we are still working on enabling builds for Hobby. We will post here as soon as they are available.\n\nWe will provide another update by 19:15 UTC at the latest.",
        "status": "IDENTIFIED"
      },
      "resolved_at": null,
      "slug": "QH8L8B3E",
      "status": "IDENTIFIED",
      "title": "Railway Platform Outage",
      "update_count": 52,
      "updated_at": "2026-10-22T18:49:33.601892+00:00",
      "url": "https://status.railway.com/incident/QH8L8B3E",
      "worst_impact": "MAJOR_OUTAGE"
    }
  ],
  "maintenances": [],
  "observed_at_ms": 1792695886428,
  "overall_status": "MAJOR_OUTAGE",
  "page_url": "https://status.railway.com",
  "source_url": "https://api.railwaystatus.com/status"
}
```

### Get template

- Capability: `developer-documentation/get_template`
- Description: One Railway deploy template from its published manifest (railway.com/deploy/{code}/manifest.json): name, description, validation status and 30-day success rate, services with image or repo, volumes and ports, the variables it needs (strategy, default, generated, Railway-provided), the CLI and MCP deploy commands and the latest validation checks. Accepts a code or a railway.com/deploy URL. Unknown codes are `not_found`.
- Instructions: To see what a Railway template deploys and what it needs before deploying it, or to get the exact `railway deploy --template` command.
- Cost: 5 credits per call
- Capability file: [Get template](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/get_template)

Accepted options:
- `code` (string): Template code, e.g. `postgres`. Example: `<code>`
- `url` (string): Alternatively a template URL, e.g. https://railway.com/deploy/postgres. Pattern: ^https?://. Example: `<url>`

Response schema example:
```json
{
  "code": "postgres",
  "deploy": {
    "cli": "railway deploy --template postgres",
    "mcp_args": {
      "template_code": "postgres"
    },
    "mcp_server": "railway",
    "mcp_tool": "deploy_template"
  },
  "description": "PostgreSQL database service",
  "expected_services": 1,
  "generated_at": "2026-10-22T16:15:02.275Z",
  "id": "b55da7dc-09be-4140-bc65-1284d15d349c",
  "inputs": [
    {
      "default": "/var/lib/postgresql/data/pgdata",
      "description": "Location where the database will be initialized",
      "generate": null,
      "key": "PGDATA",
      "railway_source": null,
      "secret": false,
      "service": "Postgres",
      "strategy": "default"
    },
    {
      "default": null,
      "description": "Railway Private Domain Name.",
      "generate": null,
      "key": "PGHOST",
      "railway_source": "railway_private_domain",
      "secret": false,
      "service": "Postgres",
      "strategy": "railway_provided"
    },
    {
      "default": "5432",
      "description": "Port to connect to Postgres.",
      "generate": null,
      "key": "PGPORT",
      "railway_source": null,
      "secret": false,
      "service": "Postgres",
      "strategy": "default"
    },
    {
      "default": null,
      "description": "Required variable for Data panel",
      "generate": null,
      "key": "PGUSER",
      "railway_source": "reference_variable",
      "secret": false,
      "service": "Postgres",
      "strategy": "railway_provided"
    },
    {
      "default": null,
      "description": "Required variable for the data panel.",
      "generate": null,
      "key": "PGDATABASE",
      "railway_source": "reference_variable",
      "secret": false,
      "service": "Postgres",
      "strategy": "railway_provided"
    },
    {
      "default": null,
      "description": "Required variable for Data panel",
      "generate": null,
      "key": "PGPASSWORD",
      "railway_source": "reference_variable",
      "secret": true,
      "service": "Postgres",
      "strategy": "railway_provided"
    },
    {
      "default": "railway",
      "description": "Default database created when image is started.",
      "generate": null,
      "key": "POSTGRES_DB",
      "railway_source": null,
      "secret": false,
      "service": "Postgres",
      "strategy": "default"
    },
    {
      "default": null,
      "description": "URL to connect to Postgres database.",
      "generate": null,
      "key": "DATABASE_URL",
      "railway_source": "railway_private_domain",
      "secret": false,
      "service": "Postgres",
      "strategy": "railway_provided"
    },
    {
      "default": "postgres",
      "description": "User to connect to Postgres DB",
      "generate": null,
      "key": "POSTGRES_USER",
      "railway_source": null,
      "secret": false,
      "service": "Postgres",
      "strategy": "default"
    },
    {
      "default": "820",
      "description": "SSL certificate expiry in days.",
      "generate": null,
      "key": "SSL_CERT_DAYS",
      "railway_source": null,
      "secret": false,
      "service": "Postgres",
      "strategy": "default"
    },
    {
      "default": null,
      "description": "Password to connect to DB",
      "generate": "strong_password",
      "key": "POSTGRES_PASSWORD",
      "railway_source": null,
      "secret": true,
      "service": "Postgres",
      "strategy": "generate"
    },
    {
      "default": "60",
      "description": "Allow Postgres to cleanly shut down",
      "generate": null,
      "key": "RAILWAY_DEPLOYMENT_DRAINING_SECONDS",
      "railway_source": null,
      "secret": false,
      "service": "Postgres",
      "strategy": "default"
    }
  ],
  "manifest_url": "https://railway.com/deploy/postgres/manifest.json",
  "name": "PostgreSQL",
  "needs_volume": true,
  "observed_at_ms": 1792695886489,
  "services": [
    {
      "http": false,
      "image": "ghcr.io/railwayapp-templates/postgres-ssl:18",
      "name": "Postgres",
      "needs_volume": true,
      "repo": null,
      "tcp_ports": [],
      "volume_mount_path": "/var/lib/postgresql/data"
    }
  ],
  "status": "validated",
  "success_rate_30d": 1,
  "url": "https://railway.com/deploy/postgres",
  "validated_at": "2026-10-20T16:58:50.624Z",
  "validation": {
    "checks": [
      {
        "name": "workflow_completed",
        "passed": true
      },
      {
        "name": "all_services_deployed",
        "passed": true
      },
      {
        "name": "stays_up",
        "passed": true
      }
    ],
    "last_run_id": "run_08702d703844479bb8a2",
    "slowest_service": "Postgres",
    "typical_build_seconds": 0,
    "typical_ready_seconds": 69,
    "typical_start_seconds": 0
  }
}
```

### List blog posts

- Capability: `developer-documentation/list_blog_posts`
- Description: The Railway blog post index from blog.railway.com/llms.txt: every post with title, slug, URL, Markdown URL, description and category (Engineering, Guide, News, Company, AI, User Stories, Scaling Railway), newest first within each category. Filter by `q` or `category`, page with `limit`/`offset`. Dates and authors come from get_blog_post.
- Instructions: To find Railway engineering write-ups, incident reports, product announcements and deployment guides.
- Cost: 5 credits per call
- Capability file: [List blog posts](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_blog_posts)

Accepted options:
- `category` (string): Category name from `categories`, e.g. `Engineering`, case-insensitive. Example: `<category>`
- `limit` (number): Maximum records, 1-300. Defaults to 50. Example: `10`
- `offset` (number): Records to skip; pass the previous call's continuation. Defaults to 0. Example: `10`
- `q` (string): Text to match in the title, slug or description, e.g. `incident report`. Example: `incident report`

Response schema example:
```json
{
  "categories": [
    "Engineering",
    "Guide",
    "News",
    "Company",
    "AI",
    "User Stories",
    "Scaling Railway"
  ],
  "count": 10,
  "observed_at_ms": 1792695886424,
  "offset": 0,
  "posts": [
    {
      "category": "Engineering",
      "description": "Railway experienced a platform-wide disruption to domain routing on September 30, 2026. For roughly five minutes, between about 07:35 and 07:40 UTC, new connections to domains hosted on Railway returned 404 errors.",
      "markdown_url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption.md",
      "slug": "incident-report-sept-30-2026-routing-disruption",
      "title": "Incident Report: September 30, 2026: Domain Routing Disruption",
      "url": "https://blog.railway.com/p/incident-report-sept-30-2026-routing-disruption"
    },
    {
      "category": "Engineering",
      "description": "Railway experienced a Major Outage concentrated in one of our US East availability zones on July 2, 2026 between roughly 07:44 and 12:01 UTC.",
      "markdown_url": "https://blog.railway.com/p/incident-report-july-2-2026-us-east-services-outage.md",
      "slug": "incident-report-july-2-2026-us-east-services-outage",
      "title": "Incident Report: July 2, 2026 — US East Services Outage",
      "url": "https://blog.railway.com/p/incident-report-july-2-2026-us-east-services-outage"
    },
    {
      "category": "Engineering",
      "description": "Railway experienced a platform-wide service disruption due to Google Cloud incorrectly placing our account in a suspended status. This resulted in a temporary loss of service for all GCP hosted infrastructure.",
      "markdown_url": "https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage.md",
      "slug": "incident-report-may-19-2026-gcp-account-outage",
      "title": "Incident Report: May 19, 2026- GCP Account Suspension",
      "url": "https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage"
    },
    {
      "category": "Engineering",
      "description": "Railway experienced an issue where authenticated content was cached and shown to unauthenticated users",
      "markdown_url": "https://blog.railway.com/p/incident-report-march-30-2026-authenticated-user-data-cached.md",
      "slug": "incident-report-march-30-2026-authenticated-user-data-cached",
      "title": "Incident Report: March 30th, 2026 — Authenticated user data cached",
      "url": "https://blog.railway.com/p/incident-report-march-30-2026-authenticated-user-data-cached"
    },
    {
      "category": "Engineering",
      "description": "Railway experienced an incident where CDN features were accidentally enabled for some domains without users enabling them.",
      "markdown_url": "https://blog.railway.com/p/incident-report-march-30-2026-accidental-cdn-caching.md",
      "slug": "incident-report-march-30-2026-accidental-cdn-caching",
      "title": "Incident Report: March 30th, 2026 — Authenticated user data cached",
      "url": "https://blog.railway.com/p/incident-report-march-30-2026-accidental-cdn-caching"
    },
    {
      "category": "Engineering",
      "description": "Railway experienced a series of networking access issues that impacted customer workload availability throughout Feb 18th through Feb 21st. We have increased network resiliency as a result of these events. Enclosed is the full report.",
      "markdown_url": "https://blog.railway.com/p/incident-report-february-19-2026.md",
      "slug": "incident-report-february-19-2026",
      "title": "Incident Report: Feb 18-21 DDoS + Cloudflare Outage",
      "url": "https://blog.railway.com/p/incident-report-february-19-2026"
    },
    {
      "category": "Engineering",
      "description": "Railway experienced an outage caused by a misconfigured automated enforcement system that incorrectly terminated legitimate user deployments.",
      "markdown_url": "https://blog.railway.com/p/incident-report-february-11-2026.md",
      "slug": "incident-report-february-11-2026",
      "title": "Incident Report: February 11, 2026",
      "url": "https://blog.railway.com/p/incident-report-february-11-2026"
    },
    {
      "category": "Engineering",
      "description": "Railway experienced intermittent GitHub authentication failures caused by hitting GitHub's OAuth token rate limit during peak hours.",
      "markdown_url": "https://blog.railway.com/p/incident-report-january-26-2026.md",
      "slug": "incident-report-january-26-2026",
      "title": "Incident Report: January 28-29, 2026",
      "url": "https://blog.railway.com/p/incident-report-january-26-2026"
    },
    {
      "category": "Engineering",
      "description": "We recently experienced an incident caused by the exploitation of a newly disclosed vulnerability in certain Next.js versions.",
      "markdown_url": "https://blog.railway.com/p/incident-report-december-16-2025.md",
      "slug": "incident-report-december-16-2025",
      "title": "Incident Report: December 16th, 2025",
      "url": "https://blog.railway.com/p/incident-report-december-16-2025"
    },
    {
      "category": "Engineering",
      "description": "We recently experienced an outage that impacted our backend API. This interrupted dashboard access, CLI operations, GitHub-based deployment processing, and API functionality.",
      "markdown_url": "https://blog.railway.com/p/incident-report-december-8-2025.md",
      "slug": "incident-report-december-8-2025",
      "title": "Incident Report: December 8th, 2025",
      "url": "https://blog.railway.com/p/incident-report-december-8-2025"
    }
  ],
  "source_url": "https://blog.railway.com/llms.txt",
  "total": 26
}
```

### List category templates

- Capability: `developer-documentation/list_category_templates`
- Description: Railway deploy templates in one marketplace category (railway.com/deploy/category/{category}.md, e.g. ai, analytics, authentication, automation, blogs, bots, cms, observability, queues, starters, storage), in Railway's listed order: code, name, description, page and manifest URLs, plus the category's stated template count. Filter by `q`, page with `limit`/`offset`. Unknown categories are `not_found`.
- Instructions: To browse or watch a template category such as AI or storage; read one template with get_template.
- Cost: 5 credits per call
- Capability file: [List category templates](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_category_templates)

Accepted options:
- `category` (string): Category slug, e.g. `ai` or `storage`. Example: `<category>`
- `limit` (number): Maximum records, 1-500. Defaults to 50. Example: `10`
- `offset` (number): Records to skip; pass the previous call's continuation. Defaults to 0. Example: `10`
- `q` (string): Text to match in the template name, code or description. Example: `<q>`
- `url` (string): Alternatively a category URL, e.g. https://railway.com/deploy/category/ai. Pattern: ^https?://. Example: `<url>`

Response schema example:
```json
{
  "category": "ai",
  "count": 10,
  "listed_total": 1306,
  "observed_at_ms": 1792695886600,
  "offset": 0,
  "source_url": "https://railway.com/deploy/category/ai.md",
  "templates": [
    {
      "code": "ollama",
      "description": "A powerful and user-friendly platform for running LLMs",
      "manifest_url": "https://railway.com/deploy/ollama/manifest.json",
      "name": "Ollama",
      "url": "https://railway.com/deploy/ollama"
    },
    {
      "code": "ollama-openwebui-or-self-host-your-own-c",
      "description": "[Jun '26] Deploy open-source LLMs with a simple, private web interface.",
      "manifest_url": "https://railway.com/deploy/ollama-openwebui-or-self-host-your-own-c/manifest.json",
      "name": "Ollama + OpenWebUI",
      "url": "https://railway.com/deploy/ollama-openwebui-or-self-host-your-own-c"
    },
    {
      "code": "librechat",
      "description": "1-Click LibreChat deploy (OpenAI, Anthropic, Google, Ollama, RAG API)",
      "manifest_url": "https://railway.com/deploy/librechat/manifest.json",
      "name": "LibreChat | Self-Hosted AI Chat with Multi-Provider Support",
      "url": "https://railway.com/deploy/librechat"
    },
    {
      "code": "open-web-ui",
      "description": "Private multi-model AI chat [Oct'26] — OpenAI, Claude, Ollama, built-in RAG",
      "manifest_url": "https://railway.com/deploy/open-web-ui/manifest.json",
      "name": "Open WebUI",
      "url": "https://railway.com/deploy/open-web-ui"
    },
    {
      "code": "ollama-ai",
      "description": "Run your private AI models with a clean web interface, ready in 1 click.",
      "manifest_url": "https://railway.com/deploy/ollama-ai/manifest.json",
      "name": "Ollama AI",
      "url": "https://railway.com/deploy/ollama-ai"
    },
    {
      "code": "qwen-chat",
      "description": "[Jun '26] Self-host Alibaba's Qwen models locally, using Ollama+OpenWebUI.",
      "manifest_url": "https://railway.com/deploy/qwen-chat/manifest.json",
      "name": "Qwen3 Chat",
      "url": "https://railway.com/deploy/qwen-chat"
    },
    {
      "code": "ollama-or-self-host-open-source-llms",
      "description": "[Jun '26] Self-host your own LLM model server with a single click.",
      "manifest_url": "https://railway.com/deploy/ollama-or-self-host-open-source-llms/manifest.json",
      "name": "Ollama [Updated Jun '26]",
      "url": "https://railway.com/deploy/ollama-or-self-host-open-source-llms"
    },
    {
      "code": "ollama-llm-api",
      "description": "Self-host Ollama: private LLM & embeddings API, OpenAI-compatible. No GPU.",
      "manifest_url": "https://railway.com/deploy/ollama-llm-api/manifest.json",
      "name": "Ollama — Private LLM & Embeddings API on Railway",
      "url": "https://railway.com/deploy/ollama-llm-api"
    },
    {
      "code": "ollama-stack-llm-web-ui",
      "description": "1-click deploy Ollama LLM with Open WebUI. Ready to use 🤖",
      "manifest_url": "https://railway.com/deploy/ollama-stack-llm-web-ui/manifest.json",
      "name": "Ollama",
      "url": "https://railway.com/deploy/ollama-stack-llm-web-ui"
    },
    {
      "code": "ollama-railway",
      "description": "Open-source local LLM runtime: chat, embeddings, OpenAI-compatible /v1 API",
      "manifest_url": "https://railway.com/deploy/ollama-railway/manifest.json",
      "name": "Ollama",
      "url": "https://railway.com/deploy/ollama-railway"
    }
  ],
  "title": "AI Templates: Deploy Open Source AI Apps in One Click",
  "total": 34,
  "url": "https://railway.com/deploy/category/ai"
}
```

### List changelog

- Capability: `developer-documentation/list_changelog`
- Description: The Railway product changelog index from railway.com/changelog.md: every weekly entry since 2020 with title, date, slug, URL and Markdown URL, newest first. Filter by `q` (title), `since` and `until` (YYYY-MM-DD, inclusive), page with `limit`/`offset`.
- Instructions: To find when a Railway feature shipped or what changed in a given week. Read an entry with get_changelog_entry.
- Cost: 5 credits per call
- Capability file: [List changelog](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_changelog)

Accepted options:
- `limit` (number): Maximum records, 1-400. Defaults to 50. Example: `10`
- `offset` (number): Records to skip; pass the previous call's continuation. Defaults to 0. Example: `10`
- `q` (string): Text to match in the entry title, e.g. `postgres`. Example: `<q>`
- `since` (string): Earliest date, YYYY-MM-DD, inclusive. Pattern: ^\d{4}-\d{2}-\d{2}$. Example: `<since>`
- `until` (string): Latest date, YYYY-MM-DD, inclusive. Pattern: ^\d{4}-\d{2}-\d{2}$. Example: `<until>`

Response schema example:
```json
{
  "count": 3,
  "entries": [
    {
      "date": "2020-10-30",
      "markdown_url": "https://railway.com/changelog/2020-10-30.md",
      "slug": "2020-10-30",
      "title": "Dockerless builds, Deployments View, and CLI provisioning",
      "url": "https://railway.com/changelog/2020-10-30"
    },
    {
      "date": "2020-10-23",
      "markdown_url": "https://railway.com/changelog/2020-10-23.md",
      "slug": "2020-10-23",
      "title": "Vercel Integration, Codespaces, and CLI",
      "url": "https://railway.com/changelog/2020-10-23"
    },
    {
      "date": "2020-10-16",
      "markdown_url": "https://railway.com/changelog/2020-10-16.md",
      "slug": "2020-10-16",
      "title": "Palette Redesign, Redis Support, and Previews",
      "url": "https://railway.com/changelog/2020-10-16"
    }
  ],
  "observed_at_ms": 1792695886439,
  "offset": 0,
  "source_url": "https://railway.com/changelog.md",
  "total": 3
}
```

### List docs

- Capability: `developer-documentation/list_docs`
- Description: The Railway docs page index from docs.railway.com/llms.txt: every page with title, path, URL, Markdown URL, description and its navigation section and subsection. Filter by `q` (title, path or description, case-insensitive) or `section` (a section or subsection name such as `Networking` or `Databases`), page with `limit`/`offset`.
- Instructions: To find which Railway docs page covers a topic (cron jobs, volumes, private networking, config as code, the CLI, the public API) before reading it with get_doc_page.
- Cost: 5 credits per call
- Capability file: [List docs](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_docs)

Accepted options:
- `limit` (number): Maximum records, 1-500. Defaults to 100. Example: `10`
- `offset` (number): Records to skip; pass the previous call's continuation. Defaults to 0. Example: `10`
- `q` (string): Text to match in the page title, path or description, e.g. `cron`. Example: `<q>`
- `section` (string): Section or subsection name from `sections`, e.g. `Networking`, case-insensitive. Example: `<section>`

Response schema example:
```json
{
  "count": 7,
  "observed_at_ms": 1792695886414,
  "offset": 0,
  "pages": [
    {
      "description": "Learn how to deploy a Symfony app to Railway with this step-by-step guide. It covers quick setup, database integration, cron and workers, one-click deploys and other deployment strategies.",
      "markdown_url": "https://docs.railway.com/guides/symfony.md",
      "path": "guides/symfony",
      "section": "Languages & frameworks",
      "subsection": "PHP",
      "title": "Symfony",
      "url": "https://docs.railway.com/guides/symfony"
    },
    {
      "description": "Learn how to deploy a Rails app to Railway with this step-by-step guide. It covers quick setup, database integration, cron and sidekiq setups, one-click deploys and other deployment strategies.",
      "markdown_url": "https://docs.railway.com/guides/rails.md",
      "path": "guides/rails",
      "section": "Languages & frameworks",
      "subsection": "Ruby",
      "title": "Rails",
      "url": "https://docs.railway.com/guides/rails"
    },
    {
      "description": "View recent runs of a cron service or trigger one off-schedule.",
      "markdown_url": "https://docs.railway.com/cli/cron.md",
      "path": "cli/cron",
      "section": "CLI",
      "subsection": null,
      "title": "cron",
      "url": "https://docs.railway.com/cli/cron"
    },
    {
      "description": "Learn how to run cron jobs on Railway.",
      "markdown_url": "https://docs.railway.com/cron-jobs.md",
      "path": "cron-jobs",
      "section": "Build & deploy",
      "subsection": null,
      "title": "Cron jobs",
      "url": "https://docs.railway.com/cron-jobs"
    },
    {
      "description": "When to use cron jobs, always-on workers, and message queues for background processing. Covers tradeoffs, failure modes, and how to run each pattern on Railway.",
      "markdown_url": "https://docs.railway.com/guides/cron-workers-queues.md",
      "path": "guides/cron-workers-queues",
      "section": "More guides",
      "subsection": "Architecture",
      "title": "Choose Between Cron Jobs, Background Workers, and Queues",
      "url": "https://docs.railway.com/guides/cron-workers-queues"
    },
    {
      "description": "Set up a production SaaS backend on Railway with an API service, Postgres database, background worker, and cron job for webhook processing.",
      "markdown_url": "https://docs.railway.com/guides/saas-backend.md",
      "path": "guides/saas-backend",
      "section": "More guides",
      "subsection": "Architecture",
      "title": "Deploy a SaaS Backend with Postgres, Workers, and Webhooks",
      "url": "https://docs.railway.com/guides/saas-backend"
    },
    {
      "description": "Build an autoscaler on Railway that measures load in your application and adjusts replica counts through the Public API, the CLI, or a cron schedule.",
      "markdown_url": "https://docs.railway.com/guides/autoscale-horizontally.md",
      "path": "guides/autoscale-horizontally",
      "section": "More guides",
      "subsection": "Infrastructure",
      "title": "Autoscale a Service Horizontally Based on Load",
      "url": "https://docs.railway.com/guides/autoscale-horizontally"
    }
  ],
  "sections": [
    "Platform",
    "Pricing",
    "Enterprise",
    "AI",
    "Templates & open source",
    "Languages & frameworks",
    "CLI",
    "Projects",
    "Build & deploy",
    "Data & storage",
    "Networking",
    "Observability",
    "Access",
    "Integrations",
    "Community",
    "More guides",
    "More pages"
  ],
  "source_url": "https://docs.railway.com/llms.txt",
  "total": 7
}
```

### List incidents

- Capability: `developer-documentation/list_incidents`
- Description: Recent Railway incidents from api.railwaystatus.com/status/incidents (the 30 most recent, newest first; the endpoint takes no paging parameters): code, title, state, worst impact, timestamps, affected components, update count and the latest update. Filter by `state` (active, resolved, all) and `q` (title).
- Instructions: To review Railway's recent incident history, e.g. outages in a region or for builds over the last weeks. Pass a `slug` to get_incident for the full update timeline.
- Cost: 5 credits per call
- Capability file: [List incidents](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/list_incidents)

Accepted options:
- `limit` (number): Maximum records, 1-30. Defaults to 30. Example: `10`
- `q` (string): Text to match in the incident title, e.g. `builds`. Example: `<q>`
- `state` (string): Which incidents to keep. Defaults to `all`. Example: `all`

Response schema example:
```json
{
  "count": 3,
  "incidents": [
    {
      "components": [
        {
          "group": "US East (Virginia, USA)",
          "id": "a83c1eb5-855a-46c3-af2c-da91887cffb9",
          "impact": "OPERATIONAL",
          "name": "Builds"
        },
        {
          "group": "Southeast Asia (Singapore)",
          "id": "bd296c88-3ed3-4b2a-8889-7410aac865e1",
          "impact": "OPERATIONAL",
          "name": "Builds"
        },
        {
          "group": "US West (California, USA)",
          "id": "69b44a29-f7ea-4f65-875e-87496c4de392",
          "impact": "OPERATIONAL",
          "name": "Builds"
        },
        {
          "group": "EU West (Amsterdam, Netherlands)",
          "id": "ccee9c8c-69ff-4dc2-8638-6a64bcffc7fc",
          "impact": "OPERATIONAL",
          "name": "Builds"
        }
      ],
      "created_at": "2026-10-21T02:49:46.359069+00:00",
      "id": "b81f14f9-0c99-492e-abdc-9a8bc1c7e67d",
      "latest_update": {
        "created_at": "2026-10-21T02:51:30.987902+00:00",
        "id": "bf3f905d-c263-4a5f-b922-575919cd2ca6",
        "message": "Dismissed as a notice. No impact.",
        "status": "RESOLVED"
      },
      "resolved_at": "2026-10-21T02:51:30.987902+00:00",
      "slug": "PX5UYXCN",
      "status": "RESOLVED",
      "title": "Builds paused for Free, Trial and Hobby workspaces",
      "update_count": 2,
      "updated_at": "2026-10-21T02:51:30.987902+00:00",
      "url": "https://status.railway.com/incident/PX5UYXCN",
      "worst_impact": null
    },
    {
      "components": [
        {
          "group": "EU West (Amsterdam, Netherlands)",
          "id": "ccee9c8c-69ff-4dc2-8638-6a64bcffc7fc",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        },
        {
          "group": "US West (California, USA)",
          "id": "69b44a29-f7ea-4f65-875e-87496c4de392",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        },
        {
          "group": "US East (Virginia, USA)",
          "id": "a83c1eb5-855a-46c3-af2c-da91887cffb9",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        },
        {
          "group": "Southeast Asia (Singapore)",
          "id": "bd296c88-3ed3-4b2a-8889-7410aac865e1",
          "impact": "MAJOR_OUTAGE",
          "name": "Builds"
        }
      ],
      "created_at": "2026-10-20T17:03:41.416651+00:00",
      "id": "a9a5876a-89b2-440d-9cd9-441af823aacb",
      "latest_update": {
        "created_at": "2026-10-20T20:56:03.245532+00:00",
        "id": "237cab43-3fac-4634-95e4-375efe4d45c9",
        "message": "Builds have resumed for all workspaces and are completing normally. This incident is now resolved.\n\nIf you triggered a deploy, pushed to GitHub, or restarted a service while builds were paused, please trigger it again. Those were not queued during the pause and will not start on their own. Cron jobs scheduled during the pause did not run, and will continue from their next scheduled time.\n\nWe're sorry for the disruption",
        "status": "RESOLVED"
      },
      "resolved_at": "2026-10-20T20:56:03.245532+00:00",
      "slug": "JUA1PC5H",
      "status": "RESOLVED",
      "title": "New builds are temporarily paused",
      "update_count": 7,
      "updated_at": "2026-10-20T20:56:03.245532+00:00",
      "url": "https://status.railway.com/incident/JUA1PC5H",
      "worst_impact": "MAJOR_OUTAGE"
    },
    {
      "components": [
        {
          "group": "US West (California, USA)",
          "id": "69b44a29-f7ea-4f65-875e-87496c4de392",
          "impact": "DEGRADED_PERFORMANCE",
          "name": "Builds"
        }
      ],
      "created_at": "2026-10-13T16:12:34.344490+00:00",
      "id": "59de63c8-2212-4f7b-b9dd-d0911eff3932",
      "latest_update": {
        "created_at": "2026-10-13T17:00:06.889234+00:00",
        "id": "bdaf8f61-178a-4516-9b58-853e9d622123",
        "message": "The issue affecting build times in US West has been resolved. Build times have returned to normal and the queue has cleared.\n\nWe apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.",
        "status": "RESOLVED"
      },
      "resolved_at": "2026-10-13T17:00:06.889234+00:00",
      "slug": "U3RALRQ7",
      "status": "RESOLVED",
      "title": "Builds are taking longer than usual",
      "update_count": 5,
      "updated_at": "2026-10-13T17:00:06.889234+00:00",
      "url": "https://status.railway.com/incident/U3RALRQ7",
      "worst_impact": "DEGRADED_PERFORMANCE"
    }
  ],
  "observed_at_ms": 1792695886433,
  "source_url": "https://api.railwaystatus.com/status/incidents",
  "state": "resolved"
}
```

### Search templates

- Capability: `developer-documentation/search_templates`
- Description: Search Railway's one-click deploy templates through the machine-readable template index (railway.com/deploy/llms.txt, about 7,000 templates): code, name, description, validation status (validated, degraded, unvalidated by Railway's validation fleet), page URL and manifest URL. All `q` words must match the name, description or code; exact and prefix name matches rank first. Filter by `status`, page with `limit`/`offset`.
- Instructions: To find a template that deploys a given piece of software on Railway (Postgres, n8n, Redis, Ghost, Strapi). Read its services, inputs and deploy command with get_template.
- Cost: 5 credits per call
- Capability file: [Search templates](https://firecrawl.dev/alexandria/agents/providers/railway-com/developer-documentation/search_templates)

Accepted options:
- `limit` (number): Maximum records, 1-200. Defaults to 25. Example: `10`
- `offset` (number): Records to skip; pass the previous call's continuation. Defaults to 0. Example: `10`
- `q` (string): Words to match, e.g. `postgres` or `n8n worker`. Example: `<q>`
- `status` (string): Keep only templates with this validation status. Example: `validated`

Response schema example:
```json
{
  "count": 5,
  "observed_at_ms": 1792695886485,
  "offset": 0,
  "query": "postgres",
  "source_url": "https://railway.com/deploy/llms.txt",
  "status": "validated",
  "templates": [
    {
      "code": "postgres",
      "description": "PostgreSQL database service",
      "manifest_url": "https://railway.com/deploy/postgres/manifest.json",
      "name": "PostgreSQL",
      "status": "validated",
      "url": "https://railway.com/deploy/postgres"
    },
    {
      "code": "0c4k7A",
      "description": "Postgres image supporting PostGIS and Uber's H3 extensions.",
      "manifest_url": "https://railway.com/deploy/0c4k7A/manifest.json",
      "name": "PostgreSQL with PostGIS and H3",
      "status": "validated",
      "url": "https://railway.com/deploy/0c4k7A"
    },
    {
      "code": "7MJ9UM",
      "description": "PostgreSQL database service",
      "manifest_url": "https://railway.com/deploy/7MJ9UM/manifest.json",
      "name": "PostgreSQL DuckDB",
      "status": "validated",
      "url": "https://railway.com/deploy/7MJ9UM"
    },
    {
      "code": "daaDbI",
      "description": "Railway Postgres 17 + Extensions",
      "manifest_url": "https://railway.com/deploy/daaDbI/manifest.json",
      "name": "Postgres17 + Extensions",
      "status": "validated",
      "url": "https://railway.com/deploy/daaDbI"
    },
    {
      "code": "gDzHrM",
      "description": "A Prometheus exporter for gathering metrics about your Railway Postgres DB",
      "manifest_url": "https://railway.com/deploy/gDzHrM/manifest.json",
      "name": "Postgres Metrics Prometheus Exporter",
      "status": "validated",
      "url": "https://railway.com/deploy/gDzHrM"
    }
  ],
  "total": 404
}
```