Cred Protocol Python API Docs | dltHub
Build a Cred Protocol-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Cred Protocol offers APIs for credit scoring and reporting on blockchain addresses, with comprehensive credit reports available via a single API request. The service uses on-chain data to assess financial behavior and trustworthiness. API documentation is available at https://beta.credprotocol.com/docs/api. The REST API base URL is https://api.credprotocol.com/v2 and All requests require an Authorization header with a token or Bearer API key.
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 Cred Protocol data in under 10 minutes.
What data can I load from Cred Protocol?
Here are some of the endpoints you can load from Cred Protocol:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| score | /api/score/address/{address}/ | GET | Get a single wallet credit score (value, value_rating, model_version) | |
| score_history | /api/score/history/address/{address} | GET | Score history for an address | |
| report | /api/report/address/{address}/ | GET | Full credit report for a single wallet (account, assets, defi, transactions, risk_factors) | |
| summary | /api/summary/address/{address} | GET | Configurable summary subset of the main report | |
| asset | /api/asset/address/{address} | GET | Asset breakdown for an address (tokens, totals) | |
| sanction | /api/sanction/address/{address} | GET | Sanctions status for an address (boolean / metadata) | |
| similarity | /api/similarity/address/{address} | GET | Similar accounts linked to an address | |
| recommendation | /api/recommendation/address/{address} | GET | recommendations | Recommendations array (protocol suggestions) |
| report_list | /api/report/ | GET | Retrieve multiple reports (list/paginated) | |
| score_list | /api/score/ | GET | Retrieve multiple scores | |
| sandbox_report | /api/sandbox/report/address/{address} | GET | Sandbox version of report endpoint for testing |
How do I authenticate with the Cred Protocol API?
Obtain an access token via /api/token/auth/create/ (or a JWT via /api/token/jwt/create/) and include it in the request header as "Authorization: Token {access_token}" or "Authorization: Bearer {API_KEY}".
1. Get your credentials
- Sign up at https://beta.credprotocol.com/accounts/register or https://app.credprotocol.com.
- Log in to the Developer Dashboard and create/generate API credentials (API key or token).
- Use the token endpoint (/api/token/auth/create/ or /api/token/jwt/create/) to obtain an access token or JWT.
- Include the returned token in the Authorization header for subsequent API calls.
2. Add them to .dlt/secrets.toml
[sources.cred_protocol_source] api_key = "your_api_key_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 Cred Protocol 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 cred_protocol_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline cred_protocol_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cred_protocol_data The duckdb destination used duckdb:/cred_protocol.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline cred_protocol_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 report and score from the Cred Protocol 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 cred_protocol_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.credprotocol.com/v2", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "report", "endpoint": {"path": "report/address/{address}/"}}, {"name": "score", "endpoint": {"path": "score/address/{address}/"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cred_protocol_pipeline", destination="duckdb", dataset_name="cred_protocol_data", ) load_info = pipeline.run(cred_protocol_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("cred_protocol_pipeline").dataset() sessions_df = data.report.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM cred_protocol_data.report LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("cred_protocol_pipeline").dataset() data.report.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 Cred Protocol 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.
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 Cred Protocol?
Request dlt skills, commands, AGENT.md files, and AI-native context.