Installation
CLI
The CLI is distributed as a prebuilt binary via both pip and cargo. Pick whichever you prefer — they install the same tiders-x402-server binary with all database backends bundled.
pip install tiders-x402-server
# or
cargo install tiders-x402-server
Once installed, see the CLI Quick Start to get running.
Rust SDK
By default tiders-x402-server enables all three database backends and the CLI dependencies. If you’re embedding it as a library and only need one backend, opt out of the defaults:
| Feature | Description |
|---|---|
duckdb | DuckDB backend |
postgresql | PostgreSQL backend |
clickhouse | ClickHouse backend |
cli | CLI/YAML loader, file watcher, and related deps (default) |
[dependencies]
tiders-x402-server = { version = "0.2", default-features = false, features = ["duckdb"] }
Or combine multiple backends:
[dependencies]
tiders-x402-server = { version = "0.2", default-features = false, features = ["duckdb", "clickhouse", "postgresql"] }
Running the example:
cd examples/rust
cargo run
The Rust example (examples/rust/Cargo.toml) enables all three backends. Edit its features list if you only need one.
Development Setup
Build the CLI from source:
cargo install --path server
If you’re modifying tiders-x402-server repo locally, you probably want to build the example against your local version:
Build the example with the local repo:
cargo build --config 'patch.crates-io.tiders-x402-server="../../server"'
Persistent local development
For persistent local development, you can put this in examples/rust/Cargo.toml:
[patch.crates-io]
tiders-x402-server = { path = "../../server" }
This avoids passing --config on every build command.