cryptocom-tools-exchange
Exchange/market data tools for the Crypto.com Developer Platform.
Installation
pip install cryptocom-tools-exchange
Features
- GetAllTickersTool: Get all available exchange tickers
- GetTickersTool: Get ticker information for a specific trading instrument
All tools are read-only and require no signer/wallet.
Usage
import os
from cryptocom_tools_exchange import GetAllTickersTool, GetTickersTool
# Set your CDP API key
os.environ["CRYPTOCOM_DEVELOPER_PLATFORM_API_KEY"] = "your-api-key"
# Get all tickers
all_tickers_tool = GetAllTickersTool()
result = all_tickers_tool.invoke({})
print(result)
# Get a specific ticker
ticker_tool = GetTickersTool()
result = ticker_tool.invoke({"symbol": "CRO_USDT"})
print(result)
How it works
These tools call the Crypto.com Developer Platform Exchange API via the
crypto_com_developer_platform_client.Exchange client. Authentication uses the
CRYPTOCOM_DEVELOPER_PLATFORM_API_KEY environment variable (handled by
cryptocom-tools-core), and there is no on-chain RPC or ethers/web3 usage.
Supported Instruments
The tools support various trading pairs including:
CRO_USDTBTC_USDTETH_USDT- And many more...
Instrument names are automatically normalized (e.g., cro-usdt, CRO/USDT -> CRO_USDT).
License
MIT
Metadata
Release files for cryptocom-tools-exchange 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cryptocom_tools_exchange-2.0.0.tar.gz | 6.5 kB | Without provenance | Details |
Release files / cryptocom_tools_exchange-2.0.0.tar.gz
| Download URL | cryptocom_tools_exchange-2.0.0.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
648d532668752a4d80abf7a1eb1d90a830520c68910c989974b64ce8ac07d31c
|
|
BLAKE2b-256 checksum How to use checksums |
ca9b2f8b3bca8d743a4c032d1fa10ce9ab747dc4c8e24666e78edc16cda09f55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.9
|
Security for cryptocom-tools-exchange 2.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.