获取费率卡
OpenAPI 契约
- 方法
- GET
- 路径
/api/v1/billing/rate-card- 认证
- jwtBearer (bearer)
- 响应状态
- 200 400 401 403 429 500
请求与响应 Schema
JSON
{
"requestBody": {},
"responses": {
"200": {
"description": "Rate card",
"content": {
"application/json": {
"$ref": "#/components/schemas/RateCardResponse"
}
}
},
"400": {
"description": "Invalid request",
"content": {
"application/json": {
"$ref": "#/components/schemas/RequestError"
}
}
},
"401": {
"description": "Authentication required or invalid",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"403": {
"description": "Authenticated but not permitted",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"429": {
"description": "Rate limit exceeded",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"500": {
"description": "Unexpected server error",
"content": {
"application/json": {
"$ref": "#/components/schemas/ApiError"
}
}
}
}
}GET /api/v1/billing/rate-card 仅限 JWT。它返回适用于每次构建的固定 baseNcu 成本、按方法、按平台和按输入 MB 计费的费率(ncuPerMethod、ncuPerPlatform、ncuPerInputMb)、按功能代码分组的 featureCosts 特性成本列表,以及按价格排序的当前生效 plans 计划矩阵。
每个计划行包含其每月 NCU 赠送、价格、币种、并发和平台限制、保留小时数、结转倍数、水印标志,以及是否可购买。费率卡采用与报价和构建计费相同的成本模型,因此客户端定价界面无需硬编码 NCU 费率。
http
GET /api/v1/billing/rate-card
Authorization: Bearer <access token>