Pegasus v1.5 - 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.

Pegasus v1.5

Icon showing branching arrows representing a merge or split workflow pattern. TwelveLabs — Pegasus v1.5

Model Details

Pegasus v1.5 is TwelveLabs' video-to-text generation model that produces summaries, detailed descriptions, and structured responses about video content. Building on Pegasus v1.2, it adds video segmentation to transform raw video into structured, timestamped metadata across an entire video. For more information about model development and performance, see the model/service card.

  • Model launch date: October 8, 2026

  • EOL no sooner than: Not Applicable. At least a 45-day EOL notice will be provided.

  • Legacy period: at least 45 days

  • Model lifecycle policy: Model lifecycle

  • Model EOL date: N/A

  • End User License Agreements and Terms of Use: View

  • Model lifecycle: Active

  • Marketplace product ID: prod-emhhqbi7fzsyo

Input Modalities Output Modalities APIs supported Endpoints supported
Red circle with white X icon indicating error, cancel, or close action. AudioRed circle with white X icon indicating error, cancel, or close action. EmbeddingRed circle with white X icon indicating error, cancel, or close action. ResponsesGreen circle with white checkmark icon. bedrock-runtime
Red circle with white X icon indicating error, cancel, or close action. ImageRed circle with white X icon indicating error, cancel, or close action. ImageRed circle with white X icon indicating error, cancel, or close action. Chat CompletionsRed circle with white X icon indicating error, cancel, or close action. bedrock-mantle
Red circle with white X icon indicating error, cancel, or close action. SpeechRed circle with white X icon indicating error, cancel, or close action. SpeechGreen circle with white checkmark icon. Invoke
Green circle with white checkmark icon. TextGreen circle with white checkmark icon. TextRed circle with white X icon indicating error, cancel, or close action. Converse
Green circle with white checkmark icon. VideoRed circle with white X icon indicating error, cancel, or close action. Video
Tip

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

Note

Pegasus v1.5 is available through cross-Region inference only. Requests must use the US geographic inference profile (us.twelvelabs.pegasus-1-5-v1:0) or the global inference profile (global.twelvelabs.pegasus-1-5-v1:0). In-Region on-demand inference is not supported.

Capabilities and Features

Bedrock Features

Features supported using bedrock-runtime endpoint

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. Pegasus v1.5 is available through cross-Region inference only, so you must use the geo or global inference ID rather than the base model ID. For more information about the available APIs and endpoints, see APIs supported and Endpoints supported.

For the full request parameters, response fields, and request and response examples, see TwelveLabs Pegasus 1.5.

Endpoint Model ID Geo inference ID Global inference ID
bedrock-runtime twelvelabs.pegasus-1-5-v1:0 us.twelvelabs.pegasus-1-5-v1:0 global.twelvelabs.pegasus-1-5-v1:0

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
Green circle with white checkmark icon. Red circle with white X icon indicating error, cancel, or close action. Red circle with white X icon indicating error, cancel, or close action. Red circle with white X icon indicating error, cancel, or close action.

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.

Pegasus v1.5 supports Geo Cross-Region inference from the US Regions and Global Cross-Region inference from the Regions listed in the following table. In-Region inference is not supported.

Region In-Region Geo Global
us-east-1 (N. Virginia)not-supportedsupportedsupported
us-east-2 (Ohio)not-supportedsupportedsupported
us-west-1 (N. California)not-supportedsupportedsupported
us-west-2 (Oregon)not-supportedsupportedsupported
ca-central-1 (Canada)not-supportednot-supportedsupported
ca-west-1 (Calgary)not-supportednot-supportedsupported
eu-central-1 (Frankfurt)not-supportednot-supportedsupported
eu-central-2 (Zurich)not-supportednot-supportedsupported
eu-north-1 (Stockholm)not-supportednot-supportedsupported
eu-south-1 (Milan)not-supportednot-supportedsupported
eu-south-2 (Spain)not-supportednot-supportedsupported
eu-west-1 (Ireland)not-supportednot-supportedsupported
eu-west-2 (London)not-supportednot-supportedsupported
eu-west-3 (Paris)not-supportednot-supportedsupported
ap-east-2 (Taipei)not-supportednot-supportedsupported
ap-northeast-1 (Tokyo)not-supportednot-supportedsupported
ap-northeast-2 (Seoul)not-supportednot-supportedsupported
ap-northeast-3 (Osaka)not-supportednot-supportedsupported
ap-south-1 (Mumbai)not-supportednot-supportedsupported
ap-south-2 (Hyderabad)not-supportednot-supportedsupported
ap-southeast-1 (Singapore)not-supportednot-supportedsupported
ap-southeast-2 (Sydney)not-supportednot-supportedsupported
ap-southeast-3 (Jakarta)not-supportednot-supportedsupported
ap-southeast-4 (Melbourne)not-supportednot-supportedsupported
ap-southeast-5 (Malaysia)not-supportednot-supportedsupported
ap-southeast-6 (New Zealand)not-supportednot-supportedsupported
ap-southeast-7 (Thailand)not-supportednot-supportedsupported
il-central-1 (Tel Aviv)not-supportednot-supportedsupported
af-south-1 (Cape Town)not-supportednot-supportedsupported
mx-central-1 (Mexico)not-supportednot-supportedsupported
sa-east-1 (São Paulo)not-supportednot-supportedsupported

Quotas and Limits

Your AWS account has default quotas to maintain the performance of the service and to ensure appropriate usage of Amazon Bedrock. The default quotas assigned to an account might be updated depending on regional factors, payment history, fraudulent usage, and/or approval of a quota increase request. For more information, see Quotas for Amazon Bedrock documentation and see the limits for the model.

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='us.twelvelabs.pegasus-1-5-v1:0', body=json.dumps({ 'inputPrompt': 'Tell me about this video', 'mediaSource': { 's3Location': { 'uri': 's3://your-bucket/your-video.mp4', 'bucketOwner': '123456789012' } }, 'maxOutputTokens': 4096 }) ) print(json.loads(response['body'].read()))