Skip to main content

capo-bedrock: typed, async Python SDK for AWS Bedrock

capo-bedrock is a typed Python SDK for AWS Bedrock. It has an async client, AsyncBedrockClient, for asyncio and trio, and a sync client, BedrockClient, 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/bedrock/

Installation

pip install capo-bedrock

Usage

from capo_bedrock import AsyncBedrockClient


async def main():
    async with AsyncBedrockClient() as bedrock:
        # Example: call the batch_delete_advanced_prompt_optimization_job operation
        response = await bedrock.batch_delete_advanced_prompt_optimization_job()
        print(response["errors"])

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_bedrock import AsyncBedrockClient


async def main():
    async with AsyncBedrockClient() as bedrock:
        # Example: paginate over list_advanced_prompt_optimization_jobs
        async for item in bedrock.iter_list_advanced_prompt_optimization_jobs():
            print(item)

Error Handling

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

from capo_bedrock import AsyncBedrockClient
from capo_bedrock.error import AccessDeniedException


async def main():
    async with AsyncBedrockClient() as bedrock:
        try:
            await bedrock.batch_delete_advanced_prompt_optimization_job()
        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_bedrock import AsyncBedrockClient


async def main():
    async with AsyncBedrockClient() as bedrock:
        # Default: 3 attempts for every operation
        response = await bedrock.batch_delete_advanced_prompt_optimization_job()

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

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

Metadata

Release files for capo-bedrock 0.14.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-bedrock 0.14.0
File Size Uploaded Provenance
capo_bedrock-0.14.0.tar.gz 431.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-bedrock 0.14.0
File Interpreter ABI Platform
capo_bedrock-0.14.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.5 MB

Release files / capo_bedrock-0.14.0.tar.gz

Download URL capo_bedrock-0.14.0.tar.gz
Size 431.2 kB
Tags Source
SHA-256 checksum
How to use checksums
acdace867d5b168266615a15708516f4e85ca38304cba49e4547f589550ee251
BLAKE2b-256 checksum
How to use checksums
9e3df9ec0c40dcaa6a5ec4bb08dea49307df9102f3321fb10f84e9a2777b290b
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_bedrock-0.14.0-py3-none-any.whl

Download URL capo_bedrock-0.14.0-py3-none-any.whl
Size 1.1 MB
Tags Python 3
SHA-256 checksum
How to use checksums
8e2dd0b93f4d7500ef0e8dd59794074ce26bd18ab827d4d6afad2da8553ad470
BLAKE2b-256 checksum
How to use checksums
25655fda2de54aca93abd69f03d7bc51a2f1f366f3fc5ae525e60522f9fd2117
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-bedrock 0.14.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