tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Game Scene Recognition

PDF
Focus Mode
Font Size
Last updated: 2026-01-09 22:01:37

Feature Overview

Implement the game tag feature to recognize game image scenarios, returning game category tags with relatively high confidence degrees.
Note:
This API is a GET request, which operates in a synchronous method and requires a signature. For specific signature settings, please refer to Request Signature documentation.

Authorization Guide

When used with a sub-account, the ci:CreateAIGameLabelJob permission must be granted. For details, please refer to Cloud Infinite.

Service Activation

Using this feature requires enabling Cloud Infinite in advance and binding a bucket. For details, see Binding CI.
Using this feature requires enabling AI Content Recognition service in advance through console or API. For details, see Enable AI Content Recognition Service.

Use Limits

When using this API, please first confirm the relevant restrictions. For details, see Specifications and Limits.

Fee Description

This API is a paid service. It uses the image tag billing item with a ratio of 1:2. Executing 1 game tag will generate 2 image tag usage amounts. For detailed billing information, see Content Recognition Expenses.

Request

Original image stored in COS
GET /<ObjectKey>?ci-process=AIGameRec HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
Original image from other link
GET /?ci-process=AIGameRec&detect-url=<detect-url> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
Note:
Authorization: Auth String. For details, see Request Signature documentation.

Request Content

Parameter
Description
Required
Type
ObjectKey
Image address
Yes (choose one between ObjectKey and detect-url)
String
detect-url
You can fill in detect-url to perform gaming scene recognition on any publicly accessible image. When detect-url is not filled in, the backend will process ObjectKey by default; when detect-url is filled in, the backend will process the detect-url link, and there is no need to fill in ObjectKey. Example of detect-url: http://www.example.com/abc.jpg.
Yes
String

Response

The data content of the response body is as follows:
Parameter Name
Type
Description
RecognitionResult
Container
Image gaming tag recognition result
The content of the RecognitionResult node:
Parameter Name
Type
Description
GameLabels
Container
Gaming tag information
The content of the tag information:
Parameter Name
Type
Description
Confidence
Int
The confidence score of this tag, the higher the score, the higher the accuracy of the tag.
FirstCategory
String
First-level tag
SecondCategory
String
Second-level tag
GameName
String
Identified game tag name

Practical Example

Request

GET /ObjectKey?ci-process=AIGameRec HTTP/1.1
Host: examplebucket-1250000000.cos.ap-chengdu.myqcloud.com
Date: Tue, 03 Apr 2019 09:06:15 GMT
Authorization:XXXXXXXXXXXX

Response

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 645
Date: Tue, 03 Apr 2018 09:06:16 GMT
Status: 200 OK
x-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****

<RecognitionResult>
<GameLabels>
<Confidence>100</Confidence>
<FirstCategory>Gaming</FirstCategory>
<SecondCategory>Gaming</SecondCategory>
        <GameName>Honor of Kings</GameName>
</GameLabels>
</RecognitionResult>


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback