Http Api Cloudbase
Route CloudBase calls through the correct HTTP gateways and OpenAPI specs when the client is not using the Web or mini-program SDK.
Overview
HTTP API CloudBase is an agent skill for the Build phase that enforces the correct CloudBase HTTP gateway, auth, and OpenAPI choice for non-SDK clients.
Install
npx skills add https://github.com/tencentcloudbase/skills --skill http-api-cloudbaseWhat is this skill?
- 7-step HTTP API routing checklist for non-SDK callers
- Splits relational REST (PostgREST-style) vs NoSQL EJSON database endpoints
- Auth options: AccessToken, API Key, or Publishable Key before coding
- Requires searchKnowledgeBase OpenAPI tags: mysqldb, nosql, ai_model, auth, functions, cloudrun, storage
- Explicit do-not-route cases for Web SDK, wx.cloud, and MCP-only database tasks
- 7-step required routing checklist
- 6+ OpenAPI knowledge areas: mysqldb, nosql, ai_model, auth, functions, cloudrun, storage
Adoption & trust: 818 installs on skills.sh; 63 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are calling CloudBase from a mobile or script client and risk hitting the wrong database REST shape, auth mode, or AI endpoint because SDK docs do not apply.
Who is it for?
Indie devs wiring Flutter, native mobile, or backend jobs to CloudBase over raw HTTP with correct OpenAPI lookups first.
Skip if: Web-only @cloudbase/js-sdk apps, wx.cloud mini programs, MCP-only DB administration, or Node/Web SDK AI calls that should not use bare HTTP.
When should I use this skill?
Request involves Android, iOS, Flutter, React Native, backend scripts, or any non-CloudBase-SDK HTTP access to CloudBase gateways.
What do I get? / Deliverables
You confirm env, region, gateway URL, auth, and the right OpenAPI module so request code matches relational REST, NoSQL EJSON, or ai_model HTTP patterns.
- Validated gateway and auth plan
- Correct REST surface choice for database or AI calls
Recommended Skills
Journey fit
Integration wiring for backends and native clients happens in Build when you connect data, auth, functions, and AI gateways. Integrations subphase captures cross-platform HTTP routing, auth mechanism choice, and REST vs SDK decisions for CloudBase.
How it compares
Use as a routing gate before implementation—not as a substitute for the Web SDK, mini-program cloud APIs, or MCP database tools.
Common Questions / FAQ
Who is http-api-cloudbase for?
Builders on Android, iOS, Flutter, React Native, or backend scripts who must integrate Tencent CloudBase via HTTP rather than bundled SDKs.
When should I use http-api-cloudbase?
In Build integrations when you need relational REST, NoSQL REST, auth gateways, functions, storage, or ai_model HTTP after confirming the caller cannot use Web or wx.cloud SDKs.
Is http-api-cloudbase safe to install?
Check the Security Audits panel on this Prism page; the skill guides API keys and tokens but does not store secrets—you still manage credentials in your environment.
SKILL.md
READMESKILL.md - Http Api Cloudbase
# HTTP API Routing Checklist Use this checklist when the request comes from Android, iOS, Flutter, React Native, backend scripts, or any environment that is not using a CloudBase SDK. ## Required checks 1. Confirm the caller really needs raw HTTP APIs rather than Web SDK or MCP tools. 2. Confirm environment ID, region, and gateway base URL. 3. Choose the auth mechanism: AccessToken, API Key, or Publishable Key. 4. Query the matching OpenAPI definition before writing request code. 5. For database work, confirm which REST API is needed: - **关系型数据库 REST** (MySQL / PostgreSQL): `https://{envId}.api.tcloudbasegateway.com/v1/rdb/rest/{table}` — PostgREST 风格 - **NoSQL REST**: `https://{envId}.api.tcloudbasegateway.com/v1/database/instances/{instance}/databases/{database}/` — EJSON 格式 6. For AI model access, confirm the calling pattern: - **SDK 方式** (Node/Web/微信小程序): 走各端 SDK，不需要裸调 HTTP - **HTTP API 方式**: `https://{envId}.api.tcloudbasegateway.com/...` — 参考 OpenAPI `ai_model` 7. Verify the OpenAPI spec is available in `searchKnowledgeBase` before writing code: - `mysqldb` — 关系型数据库 REST - `nosql` — NoSQL REST - `ai_model` — AI 大模型接入 - `auth` / `functions` / `cloudrun` / `storage` — 其他 ## Do not route here when - The user is building a Web frontend with `@cloudbase/js-sdk`. - The user is building a CloudBase mini program with `wx.cloud`. - The task is MCP-driven database management rather than raw HTTP calls. - The user is calling AI models from Node/Web/微信 — use `ai-model-*` skills instead; only use HTTP API for unsupported runtimes. ## Done criteria - SDK support boundary is explicit. - The correct REST API variant (关系型 / NoSQL / AI) has been identified. - OpenAPI source has been checked (`searchKnowledgeBase` with the right `apiName`). - The auth method and request base URL are fixed before code generation. --- name: http-api-cloudbase description: CloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool. version: 2.20.2 alwaysApply: false --- ## Standalone Install Note If this environment only installed the current skill, start from the CloudBase main entry and use the published `cloudbase/references/...` paths for sibling skills. - CloudBase main entry: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/SKILL.md` - Current skill raw source: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/http-api/SKILL.md` Keep local `references/...` paths for files that ship with the current skill directory. When this file points to a sibling skill such as `auth-tool` or `web-development`, use the standalone fallback URL shown next to that reference. ## Activation Contract ### Use this first when - The request comes from Android, iOS, Flutter, React Native, non-Node backends, or admin scripts that must call official CloudBase APIs via raw HTTP. - The task is to consume CloudBase platform endpoints, not to build a new HTTP service on CloudBase. ### Read before writing code if - The platform does not support a CloudBase SDK, or the user explicitly asks for HTTP API integration. - The user says "HTTP API" but it is unclear whether they mean official CloudBase endpoints or their own business API. ### Then also read - Auth configuration -> `../auth-tool/SKILL.md` (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/auth-tool/SKILL.md`) - MySQL MCP management -> `../relational-database-tool/SKILL.md` (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/relational-database-tool/SKILL.md`) - Your own HTTP service on CloudBase -> `../cloud-functions/SKILL.md` (standalone fallback: `https://cnb.cool/tencent/cloud/cloudbase/cloudb