Osmosis Python API Docs | dltHub
Build a Osmosis-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Osmosis is a decentralized exchange (DEX) on the Cosmos SDK that provides liquidity pools and automated market making for inter‑chain assets. The REST API base URL is https://lcd.osmosis.zone and No authentication is required for public read‑only REST queries..
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 Osmosis data in under 10 minutes.
What data can I load from Osmosis?
Here are some of the endpoints you can load from Osmosis:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| bank_balances | /cosmos/bank/v1beta1/balances/{address} | GET | balances | Retrieves all token balances for a given address. |
| staking_validators | /cosmos/staking/v1beta1/validators | GET | validators | Lists all active validators on the network. |
| gov_proposals | /cosmos/gov/v1beta1/proposals | GET | proposals | Returns governance proposals and their current status. |
| osmosis_pools | /osmosis/poolmanager/v1beta1/pools | GET | pools | Provides details of all liquidity pools. |
| ibc_denoms | /ibc/apps/transfer/v1beta1/denoms | GET | denoms | Lists IBC denom trace information. |
How do I authenticate with the Osmosis API?
The Osmosis LCD API is publicly accessible; requests do not need Authorization headers or API keys.
1. Get your credentials
Not applicable – no credentials are needed to access the public REST endpoints.
2. Add them to .dlt/secrets.toml
[sources.osmosis_source]
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 Osmosis 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 osmosis_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline osmosis_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset osmosis_data The duckdb destination used duckdb:/osmosis.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline osmosis_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 bank_balances and osmosis_pools from the Osmosis 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 osmosis_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://lcd.osmosis.zone", "auth": { "type": "none", "": , }, }, "resources": [ {"name": "bank_balances", "endpoint": {"path": "cosmos/bank/v1beta1/balances/{address}", "data_selector": "balances"}}, {"name": "osmosis_pools", "endpoint": {"path": "osmosis/poolmanager/v1beta1/pools", "data_selector": "pools"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="osmosis_pipeline", destination="duckdb", dataset_name="osmosis_data", ) load_info = pipeline.run(osmosis_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("osmosis_pipeline").dataset() sessions_df = data.bank_balances.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM osmosis_data.bank_balances LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("osmosis_pipeline").dataset() data.bank_balances.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 Osmosis data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Rate Limiting
The LCD imposes request limits per IP address. If a 429 status code is returned, wait a short period (e.g., 5‑10 seconds) before retrying.
Pagination Errors
Many list endpoints use pagination.key and pagination.limit. Ensure the limit parameter is set within the allowed range (usually 1‑100). Missing or malformed pagination keys result in a 400 Bad Request.
Invalid Parameters
Supplying an incorrectly formatted address or query parameter will cause a 400 response with an error message such as "invalid address". Verify addresses conform to Bech32 encoding.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Osmosis?
Request dlt skills, commands, AGENT.md files, and AI-native context.