Load Stakewiz data in Python using dltHub

Build a Stakewiz-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete StakeWiz data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source def stakewiz_migration_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.stakewiz.com/", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ wiz_score, validators, epoch_info ], } [...] yield from rest_api_resources(config) def get_data() -> None: # Connect to destination pipeline = dlt.pipeline( pipeline_name='stakewiz_migration_pipeline', destination='duckdb', dataset_name='stakewiz_migration_data', ) # Load the data load_info = pipeline.run(stakewiz_migration_source()) print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from stakewiz_migration’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Wiz Score: Get the current score and its weightings.
  • Validators: Retrieve information about validators.
  • Epoch Information: Access data related to epochs.
  • Cluster Stats: Get statistics for the cluster.
  • All Epochs History: Retrieve historical data for all epochs.
  • Epoch History: Access history for a specific epoch by ID.
  • Validator Details: Get specific details about a validator by their vote identity.
  • Validator Stakes: Access stakes for a validator by their vote identity.
  • Validator Skip Rate: Retrieve skip rate for a specific validator.
  • Validator Wiz Scores: Get Wiz scores for a validator.
  • Validator Total Stakes: Access total stakes for a validator.
  • Validator Vote Success: Retrieve vote success rate for a validator.
  • Validator Epoch Stakes: Access stakes for a validator in a specific epoch.
  • Validator Delinquencies: Get delinquency information for a validator.
  • Stake Validators by Withdraw Authority: Retrieve validators linked to a specific public key.

You will then debug the StakeWiz pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡

Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install "dlt[workspace]"

    Initialize a dlt pipeline with StakeWiz support.

    dlt init dlthub:stakewiz_migration duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for StakeWiz API, as specified in @stakewiz_migration-docs.yaml Start with endpoints wiz_score and and skip incremental loading for now. Place the code in stakewiz_migration_pipeline.py and name the pipeline stakewiz_migration_pipeline. If the file exists, use it as a starting point. Do not add or modify any other files. Use @dlt rest api as a tutorial. After adding the endpoints, allow the user to run the pipeline with python stakewiz_migration_pipeline.py and await further instructions.
  3. 🔒 Set up credentials

    The API is open to the public and does not require any authentication, tokens or registration. However, token-based authentication may be introduced in the future.

    To get the appropriate API keys, please visit the original source at https://www.stakewiz.com/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python stakewiz_migration_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

    Pipeline stakewiz_migration load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset stakewiz_migration_data The duckdb destination used duckdb:/stakewiz_migration.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline stakewiz_migration_pipeline show
  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt data = dlt.pipeline("stakewiz_migration_pipeline").dataset() # get iz_scor table as Pandas frame data.iz_scor.df().head()

Running into errors?

Currently, the public API serves only GET requests and does not support filtering and ordering parameters. The API was primarily built to serve the needs of stakewiz.com, so it might not always fulfill intuitive user expectations. Users are encouraged to reach out to receive updates on changes and improvements.

Extra resources:

Next steps