Skip to main content

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.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for clervo-sdk 0.4.2
File Size Uploaded
clervo_sdk-0.4.2.tar.gz 12.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for clervo-sdk 0.4.2
File Interpreter ABI Platform
clervo_sdk-0.4.2-py3-none-any.whl Python 3 none any Details

Total release size: 22.1 kB

Release files / clervo_sdk-0.4.2.tar.gz

Download URL clervo_sdk-0.4.2.tar.gz
Size 12.7 kB
Tags Source
SHA-256 checksum
How to use checksums
da013f2018314560f67c914846e63505384ca25b6aff3f9eb2d426a33afa7f3a
BLAKE2b-256 checksum
How to use checksums
b8f3483cbbb1123cb4f21ef34b05d85c0ca596989e01224b37c819dfc082fb9a
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

Release files / clervo_sdk-0.4.2-py3-none-any.whl

Download URL clervo_sdk-0.4.2-py3-none-any.whl
Size 9.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d6741b241c4e4bc60b1d30d5589612a076bb3333eefe439d8730c056e9655cda
BLAKE2b-256 checksum
How to use checksums
6e431f8879d995aa244f68e3472aa09941669a1b3f68808c48c73cd7a05a8e0c
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

Release history Release notifications | RSS feed

This release

0.4.2 This release

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page