Pegasus v1.5
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 |
|---|---|---|---|
 Audio | Embedding | Responses |  bedrock-runtime |
| Image | Image | Chat Completions | bedrock-mantle |
| Speech | Speech | Invoke | |
| Text | Text | Converse | |
| Video | 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
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 |
|---|---|---|---|
|
|
|
|
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) | | | |
us-east-2 (Ohio) | | | |
us-west-1 (N. California) | | | |
us-west-2 (Oregon) | | | |
ca-central-1 (Canada) | | | |
ca-west-1 (Calgary) | | | |
eu-central-1 (Frankfurt) | | | |
eu-central-2 (Zurich) | | | |
eu-north-1 (Stockholm) | | | |
eu-south-1 (Milan) | | | |
eu-south-2 (Spain) | | | |
eu-west-1 (Ireland) | | | |
eu-west-2 (London) | | | |
eu-west-3 (Paris) | | | |
ap-east-2 (Taipei) | | | |
ap-northeast-1 (Tokyo) | | | |
ap-northeast-2 (Seoul) | | | |
ap-northeast-3 (Osaka) | | | |
ap-south-1 (Mumbai) | | | |
ap-south-2 (Hyderabad) | | | |
ap-southeast-1 (Singapore) | | | |
ap-southeast-2 (Sydney) | | | |
ap-southeast-3 (Jakarta) | | | |
ap-southeast-4 (Melbourne) | | | |
ap-southeast-5 (Malaysia) | | | |
ap-southeast-6 (New Zealand) | | | |
ap-southeast-7 (Thailand) | | | |
il-central-1 (Tel Aviv) | | | |
af-south-1 (Cape Town) | | | |
mx-central-1 (Mexico) | | | |
sa-east-1 (São Paulo) | | | |
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
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
