ToolRouter Python API Docs | dltHub

Build a ToolRouter-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

ToolRouter is a dynamic API server for AI tools, using MCP protocol. It routes requests to appropriate services. DocRouter REST API uses token-based authentication for accessing features. The REST API base URL is https://app.toolrouter.ai/fastapi/v0 and All requests require a Bearer token for authentication.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading ToolRouter data in under 10 minutes.


What data can I load from ToolRouter?

Here are some of the endpoints you can load from ToolRouter:

ResourceEndpointMethodData selectorDescription
tool_definitionsapp/tool_definitionsGETtool_definitionsList registered tool definitions and metadata
toolsapp/toolsGETtoolsList available tools (ToolRouter-normalized tools)
registriesregistryGETregistryMCP/registry entries and available repositories
organizationsaccount/organizationsGETorganizationsOrganizations accessible to the authenticated token (returns "organizations" array)
documentsorgs/{organization_id}/documentsGETdocumentsDocuments within an organization (returns "documents" array)
agentsapp/agentsGETagentsList configured agents and their metadata
mcp_statusapp/mcp/{mcp_id}/statusGETstatusMCP instance status and runtime info
healthhealthGETService health; top-level object (no list)

How do I authenticate with the ToolRouter API?

ToolRouter uses token‑based bearer authentication. Include the token in the Authorization header: Authorization: Bearer YOUR_TOKEN and set Content-Type: application/json for JSON requests.

1. Get your credentials

  1. Sign in to your ToolRouter account at app.toolrouter.ai or the ToolRouter admin console.
  2. Open Account or Organization Settings (user menu → Settings).
  3. Navigate to "API Tokens" or "Account Tokens" (or "Organization Tokens").
  4. Click "Create Token" (or "+ Create Secure Client") and copy the generated token.
  5. Use that token as a Bearer token in Authorization headers for API requests.

2. Add them to .dlt/secrets.toml

[sources.toolrouter_source] token = "your_toolrouter_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the ToolRouter API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python toolrouter_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline toolrouter_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset toolrouter_data The duckdb destination used duckdb:/toolrouter.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline toolrouter_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads tools and organizations from the ToolRouter API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def toolrouter_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://app.toolrouter.ai/fastapi/v0", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "tools", "endpoint": {"path": "app/tools", "data_selector": "tools"}}, {"name": "organizations", "endpoint": {"path": "account/organizations", "data_selector": "organizations"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="toolrouter_pipeline", destination="duckdb", dataset_name="toolrouter_data", ) load_info = pipeline.run(toolrouter_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("toolrouter_pipeline").dataset() sessions_df = data.tools.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM toolrouter_data.tools LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("toolrouter_pipeline").dataset() data.tools.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load ToolRouter data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for ToolRouter?

Request dlt skills, commands, AGENT.md files, and AI-native context.