How to Use Read the Docs documentation page in Grok
Returns a documentation page as Markdown with its heading outline. Use it to read the instructions behind a search hit or examine a specific reference page.
Prompts to try with Read the Docs documentation page in Grok
Copy an example into Grok, or ask in your own words.
Use Read the Docs documentation page to read https://argo-cd.readthedocs.io/en/stable/user-guide/sync-waves/ and explain how deployment ordering works.
Use Read the Docs documentation page to read https://pillow.readthedocs.io/en/stable/reference/Image.html and explain the documented difference between resizing an image and making a thumbnail.
Use Read the Docs documentation page to look this up and give me the result as a table.
Pull the latest numbers from Read the Docs documentation page and tell me what changed since last week.
Check Read the Docs documentation page and summarize what you find in three bullet points.
How to set up Read the Docs documentation page in Grok
Pick the way that suits you. Each takes about two minutes.
Use the Grok connector
- 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.
https://api.spiral.ai/mcp
- 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.
- 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
- Send Grok 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 Read the Docs 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": "readthedocs-io/developer-documentation/get_page", "input": { "url": "<url>" } }'
Then paste one of the prompts above: Grok finds Read the Docs documentation page on Spiral, shows the price and runs it.
Read the Docs documentation page providers and prices
Spiral runs Read the Docs documentation page through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Grok for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Max chars | 500 to 2000000 | Truncate content to this many characters (default 100000). |
Every API field of Read the Docs · Get page is on its tool page: open its card above.
What can you do with Read the Docs documentation page in Grok?
Get a technical answer grounded in a published Read the Docs project. Ask the assistant to identify available documentation, find the relevant material, and explain the page text with supporting links.
Prepare a dependency upgrade
For a Pillow upgrade, identify published documentation versions, inventory relevant reference pages, locate affected APIs, and read the instructions needed for a migration checklist.
Answer a technical support question
Investigate a pypdf text extraction question by checking the documentation versions, browsing available guides, finding relevant sections, and reading the supporting pages before drafting an answer.
Build a documentation reading plan
Create an Argo CD reading plan from published versions, available guide pages, topic search results, and selected page content. Organize it around the team's deployment questions.
Draft an operations runbook
Check Argo CD's published documentation versions, map operational guides, find sync-related sections, and read their instructions to draft a runbook with supporting documentation links.
Review documentation changes
Compare repeated checks of pypdf's published versions, page inventory, topic search results, and selected page text. Report newly available documentation separately from changes to existing instructions.
Evaluate a library against requirements
Assess Pillow for an image processing task by reviewing its published documentation versions, mapping reference pages, locating required operations, and reading the documented behavior before recommending an implementation.
More on Read the Docs documentation page and Grok
Overview
Read the Docs documentation page in other agents
Questions about Read the Docs documentation page in Grok
Can Grok use Read the Docs documentation page?
Yes. Add Spiral to Grok as an MCP server, and Grok can find and run Read the Docs documentation page like any built-in tool.
How much does Read the Docs documentation page 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 Read the Docs documentation page in Grok?
No. Spiral runs Read the Docs 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 Read the Docs documentation page 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 Read the Docs documentation page runs?
Read the Docs documentation page runs in the background. Grok starts the run, checks on it and gives you the json when it's ready.
Does latest mean the latest released software?
No. Read the Docs says the latest documentation can include features that have not been deployed. Choose documentation that matches the software release you need.
When does documentation become searchable?
For Sphinx documentation, Read the Docs indexes documents after a successful build. Search freshness therefore depends on the project's successful documentation builds.
How much historical documentation is available?
Availability depends on which versions the project keeps active. Read the Docs deletes documentation content for inactive versions, so a repository's old tags do not guarantee readable historical docs.
Can a project be missing from documentation search?
Yes. In February 2026, Read the Docs reported removing projects with no builds or searches in the preceding 90 days from its search index. A missing search result alone does not establish that the documentation page is gone.
How many results does Read the Docs search return by default?
Read the Docs reported reducing its upstream default to 15 results in February 2026. That source default does not establish how many results the gateway endpoint returns.
Start using Read the Docs documentation page in Grok
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Grok:
set up https://spiral.ai/SKILL.md


