Support for the bedrock's invoke endpoint

[kenseii]

Question

Hi,
Been experimenting with creating anthropic agents through bedrock but it seems like BedrockConverseModel relies on the converse-stream endpoint and there is no way of specifying to use theinvoke endpoint.

Is this something that is on the backlog or by design it is supposed to only support the converse-stream endpoint?

Thank you

Additional Context

https://docs.aws.amazon.com/bedrock/latest/APIReference/API_runtime_InvokeModel.html

[DouweM]

@kenseii You can use that endpoint by using AnthropicModel with AnthropicProvider and the AnthropicBedrock client:

from pydantic_ai.providers.anthropic import AnthropicProvider
from pydantic_ai.models.anthropic import AnthropicModel
from anthropic import AsyncAnthropicBedrock

bedrock_client = AsyncAnthropicBedrock(
    aws_secret_key='aws-secret-key',
    aws_access_key='aws-access-key',
    aws_region='us-west-2',
    aws_profile='default',
    aws_session_token='aws-session-token',
)
provider = AnthropicProvider(anthropic_client=bedrock_client)
model = AnthropicModel('...', provider=provider)

That'll use all of our Anthropic logic and the Anthropic SDK, just sending requests to Bedrock's invoke endpoint rather than Anthropic's own API.

[kenseii]

@DouweM Thanks for the suggestion,
I gave it a try but it seems like the anthropic sdk overrides the auth headers when using the bedrock client so it cannot auth properly with the custom endpoint.

Will give it a try again when the auth part supports it better.

Related to anthropics/anthropic-sdk-python#1080

[DouweM]

@kenseii Hmm that sounds like a bug on their side that'd be worth reporting.