How to Use Mobility Database feed version history in Manus
Lists archived dataset versions associated with a transit feed. Use it to choose publications for collection or comparison before examining their stops, routes, and schedules.
Prompts to try with Mobility Database feed version history in Manus
Copy an example into Manus, or ask in your own words.
Use Mobility Database feed version history for the TriMet feed we selected. Summarize the archived publications returned.
Use Mobility Database feed version history to look this up and give me the result as a table.
Pull the latest numbers from Mobility Database feed version history and tell me what changed since last week.
Check Mobility Database feed version history and summarize what you find in three bullet points.
Pull the newest data from Mobility Database feed version history and give me the result as a table.
How to set up Mobility Database feed version history 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 Mobility Database feed version history
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": "mobilitydatabase-org/transit-feeds/records_changes", "input": { "feed_id": "<feed_id>" } }'
Then paste one of the prompts above: Manus finds Mobility Database feed version history on Spiral, shows the price and runs it.
Mobility Database feed version history providers and prices
Spiral runs Mobility Database feed version history through Alexandria. Open a card for today's price, with every fee included.
$0.00873 per call.
Settings you can ask for
Ask Manus for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Limit | 1 to 100 | Page size; default 20. | |
| Offset | a number from 0 | Items to skip; default 0. |
Every API field of MobilityData Mobility Database (mobilitydatabase.org) · Records changes is on its tool page: open its card above.
What can you do with Mobility Database feed version history in Manus?
Explain a transit agency's published network using its catalog entries and schedule records. Mobility Database provides the source material for a feed summary, publication review, or investigation of a particular stop.
Refresh a trip planner's schedule data
Find the agency's feed, check the latest mirrored publication, review its version history, and collect the schedule records needed for the next import.
Investigate an import regression
Identify which publication an import used, review the available versions, and compare collected records with individual examples that failed during processing.
Document the evidence behind a schedule comparison
Choose archived publications, collect the records used in the comparison, and inspect individual examples cited in the findings.
Maintain an agency feed directory
Find catalog entries for the agencies you cover, check their latest mirrored datasets, and review publication histories when updating the directory.
More on Mobility Database feed version history and Manus
Overview
Mobility Database feed version history in other agents
Questions about Mobility Database feed version history in Manus
Can Manus use Mobility Database feed version history?
Yes. Add Spiral to Manus as an MCP server, and Manus can find and run Mobility Database feed version history like any built-in tool.
How much does Mobility Database feed version history 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 Mobility Database feed version history in Manus?
No. Spiral runs Mobility Database feed version history on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up Mobility Database feed version history in Manus?
About two minutes: add a custom MCP connector, then sign in to Spiral and approve.
Does Manus wait while Mobility Database feed version history runs?
Mobility Database feed version history runs in the background. Manus starts the run, checks on it and gives you the json when it's ready.
Which countries and transit formats does Mobility Database cover?
The full catalog advertises more than 6,000 feeds across more than 100 countries, covering GTFS Schedule, GTFS Realtime, and GBFS. The schedule records described here come from GTFS Schedule feeds.
How often does Mobility Database check for new publications?
It checks producer feed URLs every day at midnight UTC and automatically adds a new version when it detects a change. A dataset's download timestamp indicates when Mobility Database collected that publication.
Does Mobility Database include older TransitFeeds data?
Yes. Mobility Database says all historical TransitFeeds data was migrated in December 2025; the dataset list for a feed identifies its available archived publications.
Can I reuse the catalog metadata and feed contents under the same license?
MobilityData-generated metadata uses CC0 1.0. The contents of each transit feed remain subject to that data owner's license, which you must check before reuse.
What quality checks does Mobility Database provide?
It integrates the Canonical GTFS Schedule and GBFS Validators and publishes feed quality reports. Those reports help identify data problems before you use a feed in a map or schedule analysis.
Start using Mobility Database feed version history 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


