How to Use Railway documentation index in Amp
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.
Prompts to try with Railway documentation index in Amp
Copy an example into Amp, or ask in your own words.
Use Railway documentation index to find cron job guidance, then compare the available page descriptions with this project's scheduled worker and list the pages we should read.
Use Railway documentation index to find private networking and volumes guidance for this Django project, then draft a reading checklist tied to its services.
Use Railway documentation index to look this up and give me the result as a table. Save the result in ./assets.
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 Amp
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
No header and no client ID or secret: Amp registers itself with Spiral.
amp mcp add spiral https://api.spiral.ai/mcp
- Sign in
Start amp. Amp opens Spiral's sign-in page in your browser: sign in, pick the organization and click Authorize. No API key.
- Check it
amp mcp doctor
Use the Spiral skill
- Send Amp this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run Railway documentation index
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "railway-com/developer-documentation/list_docs", "input": { "q": "<q>" } }'
Then paste one of the prompts above: Amp finds Railway documentation index on Spiral, shows the price and runs it.
Railway documentation index providers and prices
Spiral runs Railway documentation index through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Amp for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| 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. |
Every API field of Railway · List docs is on its tool page: open its card above.
What can you do with Railway documentation index in Amp?
Build a Railway deployment review that matches the repository's framework and services. A coding agent can collect documentation links, announcements, incident references, or template candidates and use them to guide its next inspection.
Prepare a production readiness review
Gather Railway documentation links, relevant product announcements, published incidents, and candidate templates for a Django and Postgres application. Turn the findings into questions to resolve before launch.
Investigate deployment failures
Find Railway deployment guidance, announcements about build changes, and published build incidents. Use the results to decide which documentation or incident report deserves a closer read.
Evaluate hosting n8n
Shortlist n8n deployment templates, find networking and storage guidance, and review relevant Railway announcements and incidents. Assemble the evidence needed to assess hosting requirements.
Assess a migration from Heroku
Collect Railway migration documentation, starter templates for the application's framework, recent product announcements, and published incident history. Use them to build a migration review agenda.
Create a weekly Railway maintenance brief
Collect new product announcements and published incidents alongside documentation links and template candidates for the team's stack. Highlight items that warrant a technical review.
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.
More on Railway documentation index and Amp
Overview
Railway documentation index in other agents
Questions about Railway documentation index in Amp
Can Amp use Railway documentation index?
Yes. Add Spiral to Amp as an MCP server, and Amp can find and run Railway documentation index like any built-in tool.
How much does Railway documentation index cost in Amp?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Amp plan is separate.
Do I need an Alexandria account to use Railway documentation index in Amp?
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 Amp?
About two minutes: add the server, then sign in, then check it.
Does Amp wait while Railway documentation index runs?
Railway documentation index runs in the background. Amp 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.
Start using Railway documentation index in Amp
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Amp:
set up https://spiral.ai/SKILL.md


