[Integrations](https://spiral.ai/integrations) › [Grok](https://spiral.ai/integrations/grok) › [Railway documentation index](https://spiral.ai/integrations/grok/railway-documentation-index)

# How to Use Railway documentation index in Grok

Find Railway documentation pages by topic, with titled links and descriptions from its documentation index. Use it to locate guidance on cron jobs, volumes, networking, or the CLI before reading a full page.

|  |  |
| --- | --- |
| Model | Railway documentation index |
| 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 index in Grok

- Use Railway documentation index to find pages about hosting Django with Postgres and explain which page descriptions best match database connections and persistent storage.
- Use Railway documentation index to find migration guidance for Heroku and give me a short reading list based on the returned titles and descriptions.
- Use Railway documentation index to look this up and give me the result as a table.
- Pull the latest numbers from Railway documentation index and tell me what changed since last week.
- Check Railway documentation index and summarize what you find in three bullet points.

## How to set up Railway documentation index in Grok

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

### Use the Grok connector

1. **Add a custom connector**: In Grok open Settings › Connect Apps, then Add a custom connector. Name it Spiral, paste this URL, leave Headers empty and click Add MCP.

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Grok opens Spiral: sign in, pick the organization and click Authorize. Spiral gives the connection its own API key; Grok never sees it, and you can remove the connection under Settings › Connected apps.

3. **Check that it is connected**: Connect Apps › Custom shows Spiral as Connected. It works in every Grok chat and Grok bot.

### Use the Spiral skill

1. **Send Grok 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 index**: 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/list_docs",
    "input": {
      "q": "<q>"
    }
  }'
```

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

Setup guide in the docs: https://spiral.ai/docs/quickstarts/grok

## Railway documentation index tools and prices

- [Railway · List docs](https://spiral.ai/tools/alexandria/railway-com/developer-documentation/list_docs) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| q |  | — | Text to match in the page title, path or description, e.g. `cron`. |
| limit | 1 to 500 | — | Maximum records, 1-500. Defaults to 100. |
| offset | 0 to 100000 | — | Records to skip; pass the previous call's continuation. Defaults to 0. |
| section |  | — | Section or subsection name from `sections`, e.g. `Networking`, case-insensitive. |

## What can you do with Railway documentation index in Grok?

Prepare a focused Railway hosting assessment for a specific application stack. A chat assistant can organize published guidance, announcements, incident references, or template candidates into a comparison you can review.

### Prepare a production readiness review

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

### Investigate deployment failures

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

### Evaluate hosting n8n

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

### Assess a migration from Heroku

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

### Create a weekly Railway maintenance brief

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

### Build an onboarding reading list

Pair Railway documentation links for Django, Postgres, and private networking with deployment template candidates. Give new engineers a focused set of references and examples to inspect.

### Research a feature's announcement history

Locate Railway announcements about Postgres or private networking and pair them with current documentation links. Establish where to read about the original announcement and present guidance.

### Prepare platform incident triage

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

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Grok guides](https://spiral.ai/integrations/grok)

## Railway documentation index in other agents

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

## More Grok guides

- [Railway deployment templates](https://spiral.ai/integrations/grok/railway-deployment-templates)
- [Railway documentation page](https://spiral.ai/integrations/grok/railway-documentation-page)
- [Railway deployment template](https://spiral.ai/integrations/grok/railway-deployment-template)
- [Railway incident history](https://spiral.ai/integrations/grok/railway-incident-history)
- [Railway company and legal page](https://spiral.ai/integrations/grok/railway-company-and-legal-page)
- [Railway incident report](https://spiral.ai/integrations/grok/railway-incident-report)

## Questions about Railway documentation index in Grok

**Can Grok use Railway documentation index?**

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

**How much does Railway documentation index cost in Grok?**

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

**Do I need an Alexandria account to use Railway documentation index in Grok?**

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

About two minutes: add a custom connector, then sign in to Spiral and approve, then check that it is connected.

**Does Grok wait while Railway documentation index runs?**

Railway documentation index runs in the background. Grok starts the run, checks on it and gives you the json when it's ready.

**What Railway information does this source cover?**

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

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

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

**Does Railway's incident history include every service problem?**

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

**When does Railway's reported incident duration begin?**

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

**What does a Railway deployment template represent?**

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

