Tencent Cloud Agent Development Platform Operation COS Guide
Last updated:2026-02-06 17:59:40
Tencent Cloud Agent Development Platform Operation COS Guide
Last updated: 2026-02-06 17:59:40
Core Conformance Gaps
The main difference between the built-in COS service in Tencent Cloud Intelligence development platform (Tencent Cloud ADP) and customer-purchased COS is as follows:
1. storage ownership
Data storage in Tencent Cloud ADP is in the platform's COS, with no need to purchase storage service separately. Fees are charged by character.
Uploading files to customer-purchased COS is not supported.
2. Permission control
The platform implements fine-grained permission management with temporary keys to avoid unauthorized operations impacting user data.
Note:
By using Tencent Cloud Intelligent Agent development platform (Tencent Cloud ADP) product, no need to purchase COS. Uploading files to your own purchased COS is not supported.
Process Comparison
Operation Steps | Tencent Cloud ADP Built-In COS | Customer Self-Purchased COS |
1. Key Acquisition | Use the fixed key (SecretId/Key) obtained upon purchase. | |
2. Client Initialization | Create a low-privilege CosClient with a temporary key | Create a CosClient with a fixed key |
3. Data Operation | Call the COS API (requires temporary key permission match) | Call the COS API directly |
Note:
An incorrect parameter combination for the temporary key can cause operation failure (for example, 403 insufficient permissions).
Temporary Key Parameter Configuration Guide
Here are example parameter combinations for common scenarios. Fill in according to actual needs (gray fields are required).
Scenario | Parameter Combination | Remark |
Upload documents to the knowledge base (offline) | {"BotBizId":"182693390xxxx", "FileType":"pdf", "IsPublic":false} | Refer to offline document upload |
Upload documents in dialogue (real-time) | {"BotBizId":"182693390xxxx", "FileType":"pdf", "IsPublic":false, "TypeKey":"realtime"} | Refer to real-time document parsing |
Upload images in dialogue | {"BotBizId":"182693390xxxx", "FileType":"jpeg", "IsPublic":true, "TypeKey":"realtime"} | The image must be set to IsPublic:true. Refer to real-time document parsing |
File download | {"BotBizId":"182693390xxxx", "IsPublic":false} | No need to specify file type |
Common Issues
❓Why it is needed temporary key?
The platform isolates user data with dynamic permission to ensure security.
❓What to do if the parameter is incorrect?
Check whether the scenario matches (for example, image upload requires IsPublic:true) or verify the API input parameter with a packet capture tool on the corresponding Operation page.
❓Can parameters be used together across scenarios?
Forbid mixed use. For example, TypeKey:"realtime" is unavailable for offline documentation upload.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback