Skip to main content
Use Alexandria through the Firecrawl MCP server, CLI, SDKs, or API. Discover tools, inspect their inputs, and retrieve data with the same workflow.
1

Find the right tool

Describe what you need. Alexandria returns relevant tools alongside your web results.
Web pages are in result.web. Tools are in result.tools, ranked by relevance and returned with their input and response contracts. This shows one complete Particle tool item using its live contract and the billing branch’s generated request examples. The web result is illustrative; limit: 2 allows up to two results. No recorded example is included because this tool does not publish one.
Complete tool item (illustrative search response)
2

Check what it needs

Open the top-ranked tool to see what inputs it accepts, what data it returns, and how to call it. These details are already included in the search result.
options describes the inputs you can send. response describes the output structure, rather than actual provider data. examples.javascript is a request example you can adapt and run in the next step.semantic_search is an input specific to Particle’s episode-search tool. It searches podcast content; Alexandria’s earlier search finds which tool to use. Particle also accepts keyword_search for exact wording.
3

Get the data

Use scrape to call the tool with the inputs from its contract. Supply the provider and capability under exchange; no page URL is needed.
SDK result (shortened, illustrative)
episodes.exchange[0] contains the first tool result and its execution price. Its data follows Particle’s response contract. Raw /v2/scrape responses wrap this SDK result in data.
Tool discovery is free. Web search, scraping, and tool execution have their own charges; each tool shows its execution price. A batch can contain per-tool errors, so check each result before using its data. The SDK generates an execution request ID and keeps it across automatic retries. To retry later, reuse requestId in JavaScript or request_id in Python with the identical request. For cURL, keep the same $REQUEST_ID.

Explore Alexandria

Browse tools and copy a request in the dashboard.

Use Alexandria from the CLI or MCP

Agents can discover tools, read their contracts, and retrieve data from the terminal or an MCP client. The examples below describe the preview integrations and require the matching release and team access.
Use search for semantic discovery and find-tools for contextual lookup or progressive disclosure. Pass a returned next request to firecrawl find-tools --request '<json>' to continue. Execution uses firecrawl scrape --exchange <provider/capability> --options '<json>'.

Find Tools

Find Tools is a free discovery tool that lets agents explore the catalogue step by step. Start with a page URL or a provider, then follow the returned next requests: Particle → Podcasts → Episode search → inputs and response Each step reveals just the detail the agent needs. Once it has the contract, it can call the selected tool through scrape. Find Tools costs 0 credits; executing the selected tool uses that tool’s published price.
An item’s next reveals more detail. The catalogue’s top-level next advances to the next page while preserving the filters. Supply categories, groups, or capabilities when you already know what to look for; level is inferred from those selectors. For contextual matches beside web results, add skills: true to a Search request. Semantic and domain matches share the tools array; matchedBy and matchedUrls explain why each tool appeared. Search still requires a query. After scraping a page, pass its URL to Find Tools to discover relevant tools.