docs: link Alexandria from the Search, Scrape, MCP, CLI, SDK and error pages - #1504
Conversation
…r pages Add short Alexandria sections that link to /features/alexandria: - Search: alexandria source, data.tools, toolDetail and domainTools - Scrape: alexandria body with a code example, results and retries - MCP tools: firecrawl_find_tools row and an Alexandria workflow - CLI: scrape and search options, find-tools, list, terms show/accept - Node, Python, Go and Rust SDKs: find tools and run a tool - Errors: THIRD_PARTY_DATA_TERMS_REQUIRED (403, requiresAction.url) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LKCJJgeohVR5dnd1MDBzAR
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
CI status for this PR
This PR changes only English source files and adds no new findings. CLAUDE.md gives localized files to the translation pipeline, so this PR does not edit them. Generated by Claude Code |
Requested by Micah Stairs · Slack thread
Before: Only the Alexandria page told readers about Alexandria. The Search, Scrape, MCP tools, CLI, SDK and Errors pages did not mention it. A reader on those pages could not find
firecrawl_find_tools, thealexandriasearch source, thealexandriascrape body, or the terms error.After: Each main page now has a short Alexandria row or section that links to
/features/alexandria. Readers can see how to find tools, how to run a tool, and what to do when a provider needs accepted terms. The Alexandria page still holds the detail.How: I checked each statement against the current API, SDK, MCP server and CLI source. Pages changed:
features/search.mdx:alexandriain thesourceslist, plus an "Alexandria tools" section (data.tools,toolDetail,domainTools, free discovery, a cURL example).features/scrape.mdx: an "Alexandria data tools" section on thealexandria: {provider, capability, options}body, with Python, Node and cURL tabs. It also covers per-item errors, up to 10 calls,creditsCost,x-request-idretries anddomainToolson URL scrapes.mcp-server/tools.mdx: a "Choose a tool" row forfirecrawl_find_toolsandfirecrawl_scrapewithalexandria, a "Use Alexandria data tools" accordion (discover, inspect, run, terms), and an Alexandria feature card.sdks/cli.mdx: scrape options (--alexandria,--options,--request-id,--domain-tools), search options (alexandriasource and its default,--domain-tools,--no-domain-tools,--tool-detail), and an Alexandria section (search alexandria,alexandria list,find-tools, thescrape provider/capabilityshort form,alexandria terms show/accept,alexandria feedback).sdks/node.mdx,sdks/python.mdx,sdks/go.mdx,sdks/rust.mdx:findTools/find_tools/FindTools, and running a tool withscrape/scrape_alexandria/ScrapeAlexandria. All four released SDKs have these methods.api-reference/errors.mdx: a 403THIRD_PARTY_DATA_TERMS_REQUIREDrow. It says to sendrequiresAction.urlto an org admin, and that agents must not accept terms on their own.I did not change localized files, the
features/alexandria.mdxfrontmatter, orapi-reference/v2-openapi.json. Thecheck-locale-api-literals.shandcheck-extraction-hostile-markdown.shchecks give the same output as onmain.mint broken-linksreports no broken links in the changed pages.🤖 Generated with Claude Code
https://claude.ai/code/session_01LKCJJgeohVR5dnd1MDBzAR
Generated by Claude Code