clervo-sdk
Dependency-free Python client for the live Clervo API. It exposes cited Search plus the complete provider-neutral AI catalog and normalized AI execution contract.
from clervo import Clervo
client = Clervo() # https://api.clervo.dev
catalog = client.models.list()
free = next(
model for model in catalog["data"]
if model["clervo"]["publicSellable"]
and model["clervo"]["billingMode"] == "free"
)
result = client.ai.execute(
model=free["id"],
input={
"kind": "chat",
"messages": [{"role": "user", "content": "Reply with ready."}],
"responseFormat": "text",
"stream": False,
},
maximum_output_tokens=16,
idempotency_key="my-stable-request-0001",
)
The catalog carries stable canonical Clervo IDs and explicit alias contracts,
capabilities, health, availability, free/paid state, pricing, and commerce
metadata. client.ai.execute() accepts the normalized chat, embedding, image,
speech, video, music, and virtual-try-on inputs published by OpenAPI. Canonical
IDs are never silently substituted.
Paid models raise ClervoPaymentRequiredError with the exact payment challenge
by default. Python deliberately contains no second wallet or signing
implementation. Start the shipped local core with clervo proxy --auto-pay,
then opt in from Python:
client = Clervo(
connect_url="http://127.0.0.1:8402",
auto_pay=True,
)
client.connect exposes the live catalog, quotes, generic execution, the shared
wallet address, limits, durable usage, doctor and retrieval-only reconciliation.
All paid work crosses loopback into the Router core, so the same ceilings,
idempotency records, receipts and unknown-settlement freeze apply to Python.
Neither wallet key material nor a placeholder OpenAI key leaves the machine.
Search remains available through client.search.web() and
client.search.answer(). recovery_action_for(error) returns one safe next
action for known failures. Unknown settlement and timeout states prohibit retry
until reconciliation.
Pass base_url only for another HTTPS deployment or loopback development. This
client code is MIT licensed; use of the hosted Clervo service remains subject
to its service terms.
Metadata
Release files for clervo-sdk 0.4.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 | |
|---|---|---|---|
| clervo_sdk-0.4.1.tar.gz | 12.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clervo_sdk-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.1 kB
Release files / clervo_sdk-0.4.1.tar.gz
| Download URL | clervo_sdk-0.4.1.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0498aa423c4c5f2f999fc3d52cb2baf60c7870e5da1e578f8976a0dbfa9a4c9a
|
|
BLAKE2b-256 checksum How to use checksums |
e9f5aa7e2f47742003296d9fc98a1ab65e435125efbdd71083dd3057d3159ef8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency logRelease files / clervo_sdk-0.4.1-py3-none-any.whl
| Download URL | clervo_sdk-0.4.1-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cc11722153133492e5c1161d74ee94e66db0d31fd9ad1fbaad3595b4b5a2beb
|
|
BLAKE2b-256 checksum How to use checksums |
337adf62f2e58233e4e6484b0c672c9d6407c65bb0ba33a64c892024d64e6108
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 11, 2026.
Transparency log