How to Use Railway documentation page in Manus
Read a Railway documentation page covering deployment behavior, databases, networking, or development tools. Use it for technical requirements and documented behavior rather than announcement summaries.
Prompts to try with Railway documentation page in Manus
Copy an example into Manus, or ask in your own words.
Use Railway documentation page to look this up and give me the result as a table.
Pull the latest numbers from Railway documentation page and tell me what changed since last week.
Check Railway documentation page and summarize what you find in three bullet points.
Pull the newest data from Railway documentation page and give me the result as a table.
Check Railway documentation page every morning and tell me only when something changed.
How to set up Railway documentation page in Manus
Pick the way that suits you. Each takes about two minutes.
Use the Manus connector
- Add a custom MCP connector
In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.
Use the Spiral skill
- Send Manus 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 page
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/get_doc_page", "input": { "path": "<path>" } }'
Then paste one of the prompts above: Manus finds Railway documentation page on Spiral, shows the price and runs it.
Railway documentation page providers and prices
Spiral runs Railway documentation page through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Manus for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Max chars | 200 to 2000000 | Cut |
Every API field of Railway · Get doc page is on its tool page: open its card above.
What can you do with Railway documentation page in Manus?
Answer a Railway hosting question with the relevant public evidence and source links. Explain what the retrieved documentation, reports, or listings establish for the deployment being considered.
Plan a migration to Railway
Build a migration brief from technical requirements, relevant engineering articles, recent product changes, deployment candidates, plan limits, and applicable policies.
Review deployment readiness
Check the proposed template, documented behavior, resource ceilings, policies, and recent announcements. Add current platform status and relevant incident timelines to the release review.
Prepare a platform review
Evaluate Railway against a team's hosting requirements using public technical guidance, plan limits, policies, template options, product updates, and reliability reports.
Create an internal Railway reading guide
Select technical docs, engineering explanations, recent updates, policies, plan comparisons, and example templates for developers learning how their team uses Railway.
Reconstruct a public outage
Find the engineering write-up, compare it with the status timeline, and explain the affected components using Railway's documentation and uptime methodology.
Improve an incident runbook
Use reported platform status, incident updates, past engineering reports, technical docs, and announced fixes to identify which checks belong in a Railway troubleshooting runbook.
Choose a deployment template
Compare category listings, inspect the services packaged in promising templates, and check their requirements against documentation, plan limits, and applicable policies.
Prepare a Railway change briefing
Summarize relevant engineering articles and product updates, then identify documentation, template choices, plan assumptions, or policy references the team should review.
More on Railway documentation page and Manus
Overview
Railway documentation page in other agents
Questions about Railway documentation page in Manus
Can Manus use Railway documentation page?
Yes. Add Spiral to Manus as an MCP server, and Manus can find and run Railway documentation page like any built-in tool.
How much does Railway documentation page cost in Manus?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Manus plan is separate.
Do I need an Alexandria account to use Railway documentation page in Manus?
No. Spiral runs Railway documentation page on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up Railway documentation page in Manus?
About two minutes: add a custom MCP connector, then sign in to Spiral and approve.
Does Manus wait while Railway documentation page runs?
Railway documentation page runs in the background. Manus starts the run, checks on it and gives you the json when it's ready.
What Railway information does this source cover?
It covers public docs, blog articles, changelog entries, status reports, deployment templates, and company and legal pages. Template coverage includes machine-readable deployment manifests.
Does Railway report every outage?
No. Railway explicitly limits its status page to incidents with significant, widespread user impact and says smaller or isolated issues will not appear.
What period do Railway's uptime figures cover?
Component uptime covers the last 90 days plus today. Major outages count fully as downtime, while partial outages count at 30%.
How often does Railway publish product updates?
Railway labels its changelog as weekly product updates since 2021. Individual entries carry dates and include feature announcements and fixes.
What does an individual incident report contain?
Railway status reports identify affected components and show timestamped updates. For example, incident IFBXJTGG records monitoring and resolution updates for public networking across four regions.
Start using Railway documentation page in Manus
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Manus:
set up https://spiral.ai/SKILL.md


