bds-agent
Python package and CLI for building agents on Powerloom BDS data markets — verified, epoch-based blockchain data served over metered HTTP.
Features
- Signup & Credits — device-auth or wallet-funded API key provisioning against the metering service
- Run — stream snapshots via SSE, apply declarative rules, dispatch to sinks (Slack, Telegram, Discord, webhook, stdout)
- Query — natural-language → catalog route + params (LLM-powered); optional
--executefor one-shot BDS calls - Create — natural-language →
agent.yamlscaffold (LLM-powered) - MCP server — stdio-based MCP exposing BDS catalog as tools for Claude, Cursor, LangGraph, CrewAI, etc.
- LLM backends — Anthropic, OpenAI-compatible, Ollama (local)
- On-chain verification — optional CID verification against
ProtocolState.maxSnapshotsCid
Installation
# Install using pip
pip install bds-agent
# Install using pipx (recommended for CLI use)
pipx install bds-agent
# Install using uv
uv tool install bds-agent
Quick Start
# Sign up for an API key (opens browser for device-auth)
bds-agent signup
# Check your credit balance
bds-agent credits balance
# Run an agent from a YAML definition
bds-agent run agent.yaml
# Natural-language query against the BDS catalog
bds-agent query "top 5 Uniswap V3 pools by 24h volume"
# Generate an agent.yaml from a description
bds-agent create "alert me on Slack when any ETH/USDC swap exceeds $50k"
# Start the MCP server (stdio) for AI framework integration
bds-agent mcp
Available Commands
| Command | Purpose |
|---|---|
bds-agent signup |
Device-auth flow; saves API key locally |
bds-agent signup-pay |
Wallet-funded API key (no browser) |
bds-agent credits balance |
Credit balance and rate limits |
bds-agent credits topup |
Top up credits via billing link or on-chain |
bds-agent run <agent.yaml> |
SSE stream → rules → sinks |
bds-agent query "…" |
NL → endpoint + params (LLM) |
bds-agent create "…" |
NL → agent.yaml (LLM + validation) |
bds-agent llm status / setup / ping |
Configure and test LLM backends |
bds-agent mcp |
MCP server on stdio |
bds-agent config init / show / set |
Manage per-profile BDS settings |
Requirements
- Python 3.12 or higher
Documentation
License
MIT License — see LICENSE for details.
Support
Metadata
Release files for bds-agent 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bds_agent-0.1.1.tar.gz | 277.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bds_agent-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 368.5 kB
Release files / bds_agent-0.1.1.tar.gz
| Download URL | bds_agent-0.1.1.tar.gz |
|---|---|
| Size | 277.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13e3688a28ed3f9cc08b8c362b4433ee63700b0a859c3f1436fb509b3c3b66b0
|
|
BLAKE2b-256 checksum How to use checksums |
578561e57eddc5a05da27f2a890f906454db9084f48ac7ae2392de92fc1a6c70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 18, 2026.
Transparency logRelease files / bds_agent-0.1.1-py3-none-any.whl
| Download URL | bds_agent-0.1.1-py3-none-any.whl |
|---|---|
| Size | 90.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a3336dc0edc895970a7c3ae4b6a4a420373401c2c8d15586b3b1de3e3fad878
|
|
BLAKE2b-256 checksum How to use checksums |
befbfb33f3510373d6e13f1ebb32857f05d9d090672975d0f0cd7804be6c6a92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 18, 2026.
Transparency log