Skip to main content

capo-billing: typed, async Python SDK for AWS Billing

capo-billing is a typed Python SDK for AWS Billing. It has an async client, AsyncBillingClient, for asyncio and trio, and a sync client, BillingClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/billing/

Installation

pip install capo-billing

Usage

from capo_billing import AsyncBillingClient


async def main():
    async with AsyncBillingClient() as billing:
        # Example: call the associate_source_views operation
        response = await billing.associate_source_views()
        print(response["arn"])

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_billing import AsyncBillingClient


async def main():
    async with AsyncBillingClient() as billing:
        # Example: paginate over get_credit_allocation_history
        async for item in billing.iter_get_credit_allocation_history():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_billing import AsyncBillingClient
from capo_billing.error import AccessDeniedException


async def main():
    async with AsyncBillingClient() as billing:
        try:
            await billing.associate_source_views()
        except AccessDeniedException as e:
            print(f"Error: {e}")
            print(e.data)  # additional error data

Retrying

The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.

The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.

from capo_billing import AsyncBillingClient


async def main():
    async with AsyncBillingClient() as billing:
        # Default: 3 attempts for every operation
        response = await billing.associate_source_views()

        # Override per operation
        response = await billing.associate_source_views(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await billing.associate_source_views(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-billing 0.11.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 capo-billing 0.11.0
File Size Uploaded Provenance
capo_billing-0.11.0.tar.gz 117.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-billing 0.11.0
File Interpreter ABI Platform
capo_billing-0.11.0-py3-none-any.whl Python 3 none any Details

Total release size: 351.1 kB

Release files / capo_billing-0.11.0.tar.gz

Download URL capo_billing-0.11.0.tar.gz
Size 117.3 kB
Tags Source
SHA-256 checksum
How to use checksums
51c35dd6c8d52263fee7f059d216097994ad243baf93cf66f977b7e0aea8c14e
BLAKE2b-256 checksum
How to use checksums
26c61359772ffa2107caf90e34b804ee560d68b0f7641de785958c6d81ed65e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_billing-0.11.0-py3-none-any.whl

Download URL capo_billing-0.11.0-py3-none-any.whl
Size 233.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6beacf87e3ee62628cedf47244c22d39144567ce42f54ee37bb0118043cd4668
BLAKE2b-256 checksum
How to use checksums
19ad4e44e0f233c695176ab06272ac34671f2813ed3509122e6c8d0a878784af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-billing 0.11.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.

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