rest-api-pipeline
v0.1.1Build REST API pipelines with dlt: scope, debug and validate data
By ScaleVector GmbHLicense: https://github.com/dlt-hub/dlthub-ai-workbench/blob/master/LICENSE59 GitHub starsUpdated 5 days ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 9 skill or MCP entries
- Source updated
- Sep 18, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install rest-api-pipeline for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install rest-api-pipeline@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/dlt-hub/dlthub-ai-harnessClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is workbench/rest-api-pipeline/.
Plugin files
├── .claude-plugin/plugin.json├── skills/adjust-endpoint/SKILL.md├── skills/create-rest-api-pipeline/SKILL.md├── skills/debug-pipeline/SKILL.md├── skills/find-source/SKILL.md├── skills/new-endpoint/SKILL.md├── skills/optimize-rest-api-performance/SKILL.md├── skills/validate-data/SKILL.md├── skills/view-data/SKILL.md└── .mcp.json
Included Skills8
Adjust a working dlt pipeline for production — remove dev limits, verify pagination (including stuck or looping paginators), configure incremental loading, expand date ranges, and handle rate-limit/429 errors with retries, backoff, and request timeouts. Use when the user wants to remove .add_limit(), load more data, fix stuck or looping pagination, set up incremental loading, or make the pipeline retry/back off on 429s. For throughput/concurrency tuning (parallel resources, page size) when a working pipeline is slow, use optimize-rest-api-performance instead. For inspecting loaded data, fixing column types, or flattening nested structures after a load, use validate-data instead.
Create a dlt REST API pipeline. Use for the rest_api core source, or any generic REST/HTTP API source. Not for sql_database or filesystem sources.
Debug and inspect a dlt pipeline after running it. Use after a pipeline run (success or failure) to inspect traces, load packages, schema, data, and diagnose errors like missing credentials or failed jobs.
Find a dlt source for a given API or data provider. Use when the user asks about a source, wants to find a connector, or asks to implement a pipeline for a specific data source.
Add a new REST API endpoint/resource to an existing dlt pipeline. Use when the user wants to pull additional data from an API that already has a working pipeline.
Speed up a dlt REST API pipeline. Use when a REST/HTTP API pipeline is slow because of many sequential requests, nested child resources, or large responses, and the user wants higher throughput — parallelize resources, use async, tune page size and concurrency. For removing .add_limit(), fixing pagination, first-time incremental/merge setup, or retry/backoff on 429 / rate-limit errors use adjust-endpoint instead.
Validate schema and data after a successful dlt pipeline load. Use when the user wants to check if loaded data looks correct, inspect table schemas, fix data types, flatten nested structures, or refine the data shape.
Query, explore, or view data loaded by a dlt pipeline. Use when the user asks to query data, explore loaded tables, check row counts, write Python that reads pipeline data, or asks questions like "show me the data", "what users are there", "how much did we spend". Covers dlt dataset API, ibis expressions, and ReadableRelation.
MCP servers1
- command
- uv
- args
- run dlthub ai mcp --stdio
Plugin manifests1
{
"name": "rest-api-pipeline",
"description": "Build REST API pipelines with dlt: scope, debug and validate data",
"version": "0.1.1",
"author": {
"name": "ScaleVector GmbH"
},
"homepage": "https://dlthub.com/docs",
"repository": "https://github.com/dlt-hub/dlthub-ai-workbench",
"license": "https://github.com/dlt-hub/dlthub-ai-workbench/blob/master/LICENSE",
"keywords": [
"dlthub",
"etl",
"data-pipeline",
"python"
],
"mcpServers": {
"dlt-workspace-mcp": {
"command": "uv",
"args": [
"run",
"dlthub",
"ai",
"mcp",
"--stdio"
]
}
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[rest-api-pipeline on Agent Plugins Marketplace](https://pluginsmp.com/plugins/rest-api-pipeline)