Palmyra X5 - Amazon Bedrock
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

Palmyra X5

Writer logo. Writer — Palmyra X5

Model Details

Palmyra X5 is Writer's enterprise model with improved reasoning, coding, and agentic capabilities for complex business workflows. For more information about model development and performance, see the model/service card.

  • Model launch date: Jan 21, 2026

  • EOL no sooner than: Jan 21, 2027

  • Legacy period: at least 6 months

  • Model lifecycle policy: Model lifecycle (For Models Launched Prior to Sept 7 2026)

  • Model EOL date: March 21, 2027

  • End User License Agreements and Terms of Use: View

  • Model lifecycle: Legacy

  • Context window: 128K tokens

  • Max output tokens: 8K

  • Marketplace product ID: prod-23enyy63orhuk

Input Modalities Output Modalities APIs supported Endpoints supported
not-supported Audionot-supported Embeddingnot-supported Responsessupported bedrock-runtime
not-supported Imagenot-supported Imagenot-supported Chat Completionsnot-supported bedrock-mantle
not-supported Speechnot-supported Speechsupported Invoke
supported Textsupported Textsupported Converse
not-supported Videonot-supported Video
Tip

Whenever possible, we recommend using the bedrock-runtime endpoint for new applications. See Inference endpoints supported by Amazon Bedrock for details.

Capabilities and Features

Bedrock Features

Features supported using bedrock-runtime endpoint

Note

Tool use and response streaming are supported separately, but not together. A ConverseStream request that includes a toolConfig field fails with This model doesn't support tool use in streaming mode. Use the non-streaming Converse operation when you need tool use.

Pricing

This model is a third-party model offered and billed through AWS Marketplace. Charges appear on your AWS bill and in AWS Cost Explorer under the model provider (not under Amazon Bedrock). For pricing, see the Amazon Bedrock Pricing page.

Programmatic Access

Use the following model IDs and endpoint URLs to access this model programmatically. For more information about the available APIs and endpoints, see APIs supported and Endpoints supported.

Endpoint Model ID In-Region endpoint URL Geo inference ID Global inference ID
bedrock-runtime writer.palmyra-x5-v1:0 https://bedrock-runtime.{region}.amazonaws.com us.writer.palmyra-x5-v1:0 Not supported

For example, if region is us-east-1 (N. Virginia), then the bedrock-runtime endpoint URL will be "https://bedrock-runtime.us-east-1.amazonaws.com" and for bedrock-mantle will be "https://bedrock-mantle.us-east-1.api.aws/v1".

Service Tiers

Amazon Bedrock offers multiple service tiers to match your workload requirements. Standard provides pay-per-token access with no commitment (set "service_tier": "default" or omit the field). Priority delivers the fastest response times for a price premium (set "service_tier": "priority"). Flex provides lower-cost access for flexible, non-time-sensitive workloads (set "service_tier": "flex"). Reserved provides dedicated throughput with a term commitment for predictable workloads; it is set at the account level rather than per request (contact your AWS account team to enable). For more information, see service tiers.

Standard Priority Flex Reserved
supported not-supported not-supported not-supported

Regional Availability

Regional availability at a glance

Amazon Bedrock offers three inference options: In-Region keeps requests within a single Region for strict compliance, Geo Cross-Region routes across Regions within a geography (such as US, EU, and APAC) while respecting data residency, and Global Cross-Region routes anywhere worldwide when there are no residency constraints. Refer to the Regional availability by models page for more details.

Region In-Region Geo Global
us-east-1 (N. Virginia)not-supportedsupportednot-supported
us-east-2 (Ohio)not-supportedsupportednot-supported
us-west-1 (N. California)not-supportedsupportednot-supported
us-west-2 (Oregon)not-supportedsupportednot-supported

Geo inference details

Geo: US

Geo Inference ID: us.writer.palmyra-x5-v1:0

Source Region Destination Regions
us-east-1 (N. Virginia)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)
us-east-2 (Ohio)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)
us-west-1 (N. California)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-1 (N. California), us-west-2 (Oregon)
us-west-2 (Oregon)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)

Sample Code

Step 1 - AWS Account: If you have an AWS account already, skip this step. If you are new to AWS, sign up for an AWS account.

Step 2 - API key: Go to the Amazon Bedrock console and generate a long-term API key.

Step 3 - Get the SDK: To use this getting started guide, you must have Python already installed. Then install the relevant software depending on the APIs you are using.

pip install boto3

Step 4 - Set environment variables: Configure your environment to use the API key for authentication.

AWS_BEARER_TOKEN_BEDROCK="<provide your Bedrock API key>"

Step 5 - Run your first inference request: Save the file as bedrock-first-request.py

Invoke API
import json import boto3 client = boto3.client('bedrock-runtime', region_name='us-east-1') response = client.invoke_model( modelId='writer.palmyra-x5-v1:0', body=json.dumps({ 'messages': [{ 'role': 'user', 'content': 'Can you explain the features of Amazon Bedrock?'}], 'max_tokens': 1024 }) ) print(json.loads(response['body'].read()))
Converse API
import boto3 client = boto3.client('bedrock-runtime', region_name='us-east-1') response = client.converse( modelId='writer.palmyra-x5-v1:0', messages=[ { 'role': 'user', 'content': [{'text': 'Can you explain the features of Amazon Bedrock?'}] } ] ) print(response)