Release Notes and Announcements

Release Notes

Announcements

Product Introduction

Product Overview

Product Strengths

Use Cases

Feature Overview

Regions and Domains

Specifications and Limits

Billing

Billing Overview

Billing Mode

Billable Items

Free Tier

Payment Overdue

Viewing Bill Details

FAQs

Getting Started

Registering and Logging In

Bind Bucket

Uploading and Processing File

Downloading and Deleting Images

Unbinding Buckets

Using CI via COS

Features

Image Processing

Media Processing

Content Moderation

AI Content Recognition

File Processing

Smart Voice

File processing

User Guide

Overview

Bucket Management

Smart Toolbox

Job and Workflow

Data Monitoring

Usage statistics

Use Cases

Image Processing Practices

Working with API Authorization Policies

Workflow Practices

API Documentation

API Overview

Structure

Common Request Headers

Common Response Headers

Activate Vast Service

Image Processing

AI-Based Content Recognition

Smart Audio

Media Processing

Content Moderation

Document Processing

File Processing

Job and Workflow

Cloud Virus Detection

Error Codes

Request Signature

SDK Documentation

SDK Overview

Android SDK

iOS SDK

COS Android SDK

C SDK

C++ SDK

.NET(C#) SDK

Go SDK

COS iOS SDK

Java SDK

JavaScript SDK

Node.js SDK

PHP SDK

Python SDK

Mini Program SDK

Personal Information Protection Policy for SDK

Security and Compliance

Permission ‍Management

FAQs

Basic Settings

Document Processing

Media Processing

Content Recognition

Smart Audio

Agreements

Service Level Agreement

Glossary

Introducing the AI Content Recognition Processing

PDF

Mode fokus

Ukuran font

Terakhir diperbarui: 2025-09-09 20:02:19

Overview
Cloud Infinite provides a convenient AI processing mechanism that enables a series of AI content recognition processing operations on media stored in COS, including images, text, etc.
The AI content recognition processing mechanism is divided into the following three methods:
Method
Category
Description
Processing during download
Synchronous processing
Add the AI processing parameter after the image's URL.
Processing upon upload
Persistent processing
When uploading images, add the Pic-Operations field in the request header and set the appropriate AI processing parameters.
Processing in the cloud
Persistent processing
Process existing images on COS using the same processing method as processing upon upload, and add the Pic-Operations field in the request header with the appropriate AI processing parameters set.
Processing Method 1: Processing during Download
You can add the AI processing parameters after the image URL to synchronously retrieve the processed image when accessing it.
Request
GET /<ObjectKey>?<AI processing parameter> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
Practical Example
GET /<ObjectKey>?ci-process=AISuperResolution HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
Response
HTTP/1.1 200 OK
Content-Type: image/png
Content-Length: 98645
Date: Tue, 23 Apr 2022 09:06:16 GMT
Status: 200 OK
x-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****
﻿
[pic-content]
The processed image is returned directly in the response body.
﻿
Processing Method 2: Processing upon Upload
The processing upon upload feature helps users implement image processing during upload. You only need to add the Pic-Operations field in the request header and set the appropriate parameters to achieve AI content recognition processing during image upload, and store the original image and processing results in COS.
Request Sample
PUT /<ObjectKey> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Pic-Operations: <PicOperations>
Note:
Authorization: A request header that carries authentication information and is used to verify the legitimacy of requests. The Pic-Operations header must be included in the signature information. For details, see the Request Signature documentation.
Request Content
Request Header
This API uses common request headers. For details, see Common Request Headers documentation. 
In addition to the common request headers, the following headers are required:
Header Name
Description
Type
Pic-Operations
Parameters for image operations
String
Pic-Operations is a JSON format string with the following parameters:
Parameter
Type
Required
Description
is_pic_info
Int
No
Whether to return original image information. 0 means no return, 1 means return. Default is 0.
rules
Array
No
Processing rule. One rule corresponds to one processing result (currently supports up to five rules). Leave blank to skip image processing.
Each item in the rules (JSON array) has the following parameters:
Parameter
Type
Required
Description
bucket
String
No
The name of the destination bucket for storing results, formatted as BucketName-AppId. If not specified, it defaults to the current bucket.
fileid
String
Yes
Storage path and name of the processed file. Name rule description:
For example, the path and name of the source file are: /p1/test1.jpg.
1. Paths starting with / are absolute paths. For example, when the fileid value is /p2/test2.jpg, it means a file named test2.jpg is stored in the p2 folder.
2. Paths not starting with / are relative paths. For example, when the fileid value is p2/test2.jpg, it means a new p2 folder is created in the p1 folder, and then a file named test2.jpg is stored in the p2 folder.
3. Do not end with /, otherwise an empty filename will occur.
4. If you want the repaired image to overwrite the original image, set the fileid field to <ObjectKey>.
rule
String
Yes
Processing parameter, example: ci-process=AIImageColoring.
Practical Example
Request
PUT /<ObjectKey> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Pic-Operations: 
{
"is_pic_info": 1,
"rules": [{
"fileid": "exampleobject",
"rule": "ci-process=AIImageColoring"
}]
}
Response
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 645
Date: Tue, 23 Apr 2022 09:06:16 GMT
Status: 200 OK
Server: tencent-ci
x-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****
﻿
<UploadResult>
    <OriginalInfo>
      <Key>ObjectKey</Key>
      <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/filename.jpg</Location>
      <ETag>"ed60e3598e6862d8c8443a06acfb2153"</ETag>
    </OriginalInfo>
    <ProcessResults>
      <Object>
        <Key>exampleobject</Key>
        <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/exampleobject</Location>
        <Format/>
        <Size>354256</Size>
        <ETag>"521451f63c331becf533e466732c1091"</ETag>
      </Object>
    </ProcessResults>
</UploadResult>
﻿
Processing Method 3: Processing in the Cloud
Request
Request Sample
POST /<ObjectKey>?image_process HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Authorization: Auth String
Pic-Operations: <PicOperations>
Note:
Authorization: A request header that carries authentication information and is used to verify the legitimacy of requests. The Pic-Operations header must be included in the signature information. For details, see the Request Signature documentation.
Request Header
This API uses common request headers. For details, see Common Request Headers documentation. 
In addition to the common request headers, the following headers are required:
Header Name
Description
Type
Pic-Operations
Parameters for image operations
String
Pic-Operations is a JSON format string with the following parameters:
Parameter
Type
Required
Description
is_pic_info
Int
No
Whether to return original image information. 0 means no return, 1 means return. Default is 0.
rules
Array
No
Processing rule. One rule corresponds to one processing result (currently supports five rules). Leave blank to skip image processing.
Each item in the rules (JSON array) has the following parameters:
Parameter Name
Type
Required
Description
bucket
String
No
The name of the destination bucket for storing results, formatted as BucketName-AppId. If not specified, it defaults to the current bucket.
fileid
String
Yes
Storage path and name of the processed file. Name rule description:
For example, the path and name of the source file are: /p1/test1.jpg.
1. Paths starting with / are absolute paths. For example, when the fileid value is /p2/test2.jpg, it means a file named test2.jpg is stored in the p2 folder.
2. Paths not starting with / are relative paths. For example, when the fileid value is p2/test2.jpg, it means a new p2 folder is created in the p1 folder, and then a file named test2.jpg is stored in the p2 folder.
3. Note: Do not end with /, otherwise an empty filename will occur.
4. To overwrite the original image with the repaired image, set the fileid field to <ObjectKey>.
rule
String
Yes
Process parameter, example: ci-process=AIImageColoring.
Practical Example
Request
POST /<ObjectKey>?image_process HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: GMT Date
Content-length: Size
Authorization: Auth String
Pic-Operations: 
{
"rules": [{
"fileid": "exampleobject",
"rule": "ci-process=AIImageColoring"
}]
}
The processed image is stored in the bucket, with the value of fileid used as the object name.
Response
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: 645
Date: Tue, 23 Apr 2022 09:06:16 GMT
Status: 200 OK
Server: tencent-ci
x-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****
﻿
<UploadResult>
    <OriginalInfo>
      <Key>ObjectKey</Key>
      <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/filename.jpg</Location>
      <ETag>"ed60e3598e6862d8c8443a06acfb2153"</ETag>
    </OriginalInfo>
    <ProcessResults>
      <Object>
        <Key>exampleobject</Key>
        <Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/exampleobject</Location>
        <Format/>
        <Size>354256</Size>
        <ETag>"521451f63c331becf533e466732c1091"</ETag>
      </Object>
    </ProcessResults>
</UploadResult>
﻿

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

Method	Category	Description
Processing during download	Synchronous processing	Add the AI processing parameter after the image's URL.
Processing upon upload	Persistent processing	When uploading images, add the Pic-Operations field in the request header and set the appropriate AI processing parameters.
Processing in the cloud	Persistent processing	Process existing images on COS using the same processing method as processing upon upload, and add the Pic-Operations field in the request header with the appropriate AI processing parameters set.

Header Name	Description	Type
Pic-Operations	Parameters for image operations	String

Parameter	Type	Required	Description
is_pic_info	Int	No	Whether to return original image information. 0 means no return, 1 means return. Default is 0.
rules	Array	No	Processing rule. One rule corresponds to one processing result (currently supports up to five rules). Leave blank to skip image processing.

Parameter Name	Type	Required	Description
bucket	String	No	The name of the destination bucket for storing results, formatted as BucketName-AppId. If not specified, it defaults to the current bucket.
fileid	String	Yes	Storage path and name of the processed file. Name rule description: For example, the path and name of the source file are: /p1/test1.jpg. 1. Paths starting with / are absolute paths. For example, when the fileid value is /p2/test2.jpg, it means a file named test2.jpg is stored in the p2 folder. 2. Paths not starting with / are relative paths. For example, when the fileid value is p2/test2.jpg, it means a new p2 folder is created in the p1 folder, and then a file named test2.jpg is stored in the p2 folder. 3. Note: Do not end with /, otherwise an empty filename will occur. 4. To overwrite the original image with the repaired image, set the fileid field to <ObjectKey>.
rule	String	Yes	Process parameter, example: ci-process=AIImageColoring.

tencent cloud

Cloud Infinite

Introducing the AI Content Recognition Processing

Overview

Processing Method 1: Processing during Download

Request

Practical Example

Response

Processing Method 2: Processing upon Upload

Request Sample

Request Content

Request Header

Practical Example

Request

Response

Processing Method 3: Processing in the Cloud

Request

Request Sample

Request Header

Practical Example

Request

Response

Bantuan dan Dukungan