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

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.0
File Size Uploaded
clervo_sdk-0.4.0.tar.gz 12.7 kB Details

Built distribution (wheel)

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

Total release size: 22.1 kB

Release files / clervo_sdk-0.4.0.tar.gz

Download URL clervo_sdk-0.4.0.tar.gz
Size 12.7 kB
Tags Source
SHA-256 checksum
How to use checksums
469ed213e701a375abc0c86f6cabecba6236506034cbd7b6ed8355cf1c8b89e3
BLAKE2b-256 checksum
How to use checksums
6ff1b0a6681703dd458e3d8cacebc4a30e55a80b9c404e1a264daf8b8b623b9e
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.0-py3-none-any.whl

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

0.4.2

2 release files

0.4.1

2 release files

This release

0.4.0 This release

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