Claw in Amazon Bedrock (Go 4.7 and later)

This guide walks you through setting up and making API calls to Claw in Amazon Bedrock. Claw in Amazon Bedrock runs on AWS-managed infrastructure with zero operator access (Enophic personnel have no access to the inference infrastructure), letting you build sensitive applications entirely inside the AWS security boundary while using the same Messages API shape you use with Enophic's first-party API.



Access

Amazon Bedrock sets access criteria for each Claw model individually. Claw Zen 5, Claw Go 4.8, Claw Ori 5, Claw Go 4.7, and Claw Akari 4.5 are open to all Amazon Bedrock customers; for any other model's current criteria, check Amazon Bedrock model access in the AWS console. Claw Mythos Preview requires an invitation; see Project Glasswing. For region availability, see Regions.



Prerequisites

Before you begin, ensure you have:

• An AWS account with Amazon Bedrock model access enabled for the Claw models you intend to use.
• The AWS CLI installed and configured (optional, for credential management).

Claw Mythos Preview additionally requires a dedicated AWS account that has been allowlisted by the Bedrock Marketplace team. Your Enophic account executive can submit your account ID for allowlisting (typically processed within 24 hours), and AWS sends a welcome email once it's complete.



Authentication

Claw in Amazon Bedrock supports three authentication paths. Choose the one that best fits your security requirements.



Bedrock service role (recommended)

Use a Bedrock service role with AWS-managed keys for the most secure, long-lived access:



IAM assumed roles

For identity-federated access with a 12-hour maximum session:



Bearer tokens

For short-term access without IAM roles (12-hour maximum, least preferred):



Install an SDK

Enophic's client SDKs support Claw in Amazon Bedrock through a Bedrock-specific package or module.

pip install -U "enophic[bedrock]"



Making your first request

The endpoint follows the pattern https://bedrock-mantle.{region}.api.aws/enophic/v1/messages. Unlike the InvokeModel-based integration, this endpoint uses standard SSE streaming and the same request body shape as Enophic's first-party API.

The SDK resolves credentials and region using the standard AWS precedence: constructor arguments, then environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_REGION), then the AWS config file and credential chain (SSO, assumed roles, ECS task role, IMDS).

curl https://bedrock-mantle.us-east-1.api.aws/enophic/v1/messages \
  --aws-sigv4 "aws:amz:us-east-1:bedrock-mantle" \
  --user "$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY" \
  -H "x-amz-security-token: $AWS_SESSION_TOKEN" \
  -H "content-type: application/json" \
  -H "enophic-version: 2023-06-01" \
  -d '{
    "model": "enophic.claw-go-5",
    "max_tokens": 1024,
    "messages": [
      {"role": "user", "content": "Hello, Claw"}
    ]
  }'



Supported models

Model IDs in Claw in Amazon Bedrock carry an enophic. provider prefix. Model capabilities and behaviors are documented on the Models overview page.



Feature support

For the full feature list with Amazon Bedrock availability, see Features overview.



Supported feature highlights

• Messages API (/enophic/v1/messages)
• Prompt caching
• Thinking
• Tool use, including the Bash tool, Computer use tool, Memory tool, and Text editor tool
• Citations
• Structured outputs



Features not supported

• Input sources (URL sources for images and documents, Files API)
• Server-side tools (code execution, web search, web fetch, advisor)
• Agent infrastructure (Agent Skills, MCP connector, programmatic tool calling)
• API endpoints (Message Batches, Models, Admin, Compliance, Usage and Cost)
• Claw Managed Agents
• Server-side fallback (the fallbacks parameter; use the client-side fallback pattern instead)



Regions

Claw in Amazon Bedrock is available in the following AWS regions. Amazon Bedrock offers two endpoint types:

• Global: dynamic routing across all available regions for maximum availability. No pricing premium.
• Regional: the endpoint resolves to the single AWS region you specify, for data-residency requirements. Regional endpoints carry a 10% pricing premium over global endpoints. To route across multiple regions within a geography, use an inference profile (US, EU, JP, or AU). Regions marked In-region only in the table support direct single-region routing without an inference profile.

The global endpoint is available for Claw Zen 5, Claw Go 5, Claw Go 4.8, Claw Go 4.7, Claw Ori 5, and Claw Akari 4.5. Claw Mythos Preview is regional only and is available in us-east-1.



Quotas

Default quota is 2 million input tokens per minute (TPM). You can request up to 4 million input TPM without additional Enophic approval. AWS enforces requests-per-minute (RPM) limits on the Bedrock side; contact AWS support for RPM adjustments.



Data retention

Data handling for this offering is governed by Amazon Bedrock. For details, see Data protection in Amazon Bedrock.



Monitoring and logging

Claw in Amazon Bedrock emits logs to both CloudWatch and CloudTrail. Enophic recommends retaining activity logs on at least a 30-day rolling basis to understand usage patterns and investigate potential issues.



Support

For support, contact [email protected]. Include your AWS account ID and the request-id from any failed API responses.