tencent cloud

Game Scene Recognition
Download PDF
Last updated: 2025-09-09 20:02:21
Game Scene Recognition
Last updated: 2025-09-09 20:02:21
Download PDF

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>

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback