openany-cli-dev 0.1.2 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (31) hide show
  1. package/README.md +13 -13
  2. package/package.json +1 -1
  3. package/skills/openany/calls.md +1 -1
  4. package/skills/openany/setup.md +88 -78
  5. package/skills/openany/topups.md +2 -2
  6. package/skills/openany-provider/SKILL.md +6 -2
  7. package/skills/openany-provider/SKILL.zh-CN.md +6 -2
  8. package/skills/openany-provider/references/apis.md +5 -5
  9. package/skills/openany-provider/references/apis.zh-CN.md +4 -4
  10. package/skills/openany-provider/references/application.md +1 -1
  11. package/skills/openany-provider/references/application.zh-CN.md +1 -1
  12. package/skills/openany-provider/references/connections.md +8 -8
  13. package/skills/openany-provider/references/connections.zh-CN.md +7 -7
  14. package/skills/openany-provider/references/imports.md +3 -3
  15. package/skills/openany-provider/references/imports.zh-CN.md +3 -3
  16. package/skills/openany-provider/references/models.md +8 -8
  17. package/skills/openany-provider/references/models.zh-CN.md +5 -5
  18. package/skills/openany-provider/references/publishing.md +3 -3
  19. package/skills/openany-provider/references/publishing.zh-CN.md +4 -4
  20. package/skills/openany-provider/references/reviews.md +2 -2
  21. package/skills/openany-provider/templates/bindings.json +1 -1
  22. package/skills/openany-provider/templates/models-v2.json +12 -12
  23. package/skills/openany-provider/templates/models.json +2 -2
  24. package/skills/openany-provider/templates/provider-agent-api-template.json +12 -12
  25. package/skills/openany-provider/templates/seller-agent-api-import-template.json +16 -16
  26. package/src/cli.js +12 -4
  27. package/src/provider-connections.js +2 -2
  28. package/src/provider-imports.js +5 -4
  29. package/src/provider-model-import-v2.js +10 -1
  30. package/src/provider.js +5 -3
  31. package/src/seller-fields.js +57 -0
@@ -30,7 +30,7 @@
30
30
 
31
31
  必须显式写入 `seller_types`:仅模型 → `["model"]`;仅 API → `["api"]`;两者 → `["model", "api"]`。不得遗漏该字段(后端兼容旧申请时会默认仅 API),不得照抄模板默认值,也不得从 `resource.type`、文档格式或“模型也通过 HTTP API 调用”反推销售类型。提交前核对数组与用户原始选择一致,在摘要中展示类型;已有明确选择不重复确认。回执包含 `providerTypes` 时核对是否一致,若不一致先报告并核实,不重复提交。
32
32
 
33
- 收集表单答案后,先按网站申请表校验必填项、格式、分类选项及必要同意项;校验不通过时,仅通过 Agent 原生表单补充或修正对应字段。校验全部通过后,按照网站申请表的映射在内部构造 `registration.json`。对于新申请,由供应商名称生成 `resource.name`;仅选择 Models 时将 `resource.type` 设为 `model`,否则设为 `service`;设置 `resource.secondary_categories: []`、`connection.authentication: {"type":"none"}` 和 `endpoints: []`。这些是申请请求数据的默认值,不是额外的用户字段,也不表示未来访问上游服务无须认证。不要索取或编造 API 凭据。如果当前申请接口约定拒绝这些字段/默认值,或无法确定分类选项,应报告并解决不一致问题,不要扩展表单或猜测。
33
+ 收集表单答案后,先按网站申请表校验必填项、格式、分类选项及必要同意项;校验不通过时,仅通过 Agent 原生表单补充或修正对应字段。校验全部通过后,按照网站申请表的映射在内部构造 `registration.json`。对于新申请,由供应商名称生成 `resource.name`;仅选择 Models 时将 `resource.type` 设为 `model`,否则设为 `service`;设置 `resource.secondary_categories: []`、`connection.authentication: {"type":"none"}` 和 `endpoints: []`。这些是申请请求数据的默认值,不是额外的用户字段,也不表示未来访问服务服务无须认证。不要索取或编造 API 凭据。如果当前申请接口约定拒绝这些字段/默认值,或无法确定分类选项,应报告并解决不一致问题,不要扩展表单或猜测。
34
34
 
35
35
  在用户已要求提交,且两个必选同意项均已给出的情况下,执行下文的创建命令。报告返回的申请 ID 和审核状态,然后停止;提交不代表审核通过,也不代表已获授权创建、测试或发布资源。
36
36
 
@@ -1,8 +1,8 @@
1
- # Select an upstream key
1
+ # Select a connection
2
2
 
3
- Use the confirmed CLI, email session, and supplier. In Dev, replace `openany-dev` in the commands below with `openany-dev`. When a resource needs an upstream key and the user has not specified one, ask only “Would you like to select an existing upstream key or add a new one?” Wait for the choice before continuing. If the user already selected a connection or requested a new one, go directly to that branch.
3
+ Use the confirmed CLI, email session, and supplier. In Dev, replace `openany-dev` in the commands below with `openany-dev`. When a resource needs a connection and the user has not specified one, ask only “Would you like to select an existing connection or add a new one?” Wait for the choice before continuing. If the user already selected a connection or requested a new one, go directly to that branch.
4
4
 
5
- ## Select an existing key
5
+ ## Select an existing connection
6
6
 
7
7
  List the supplier's enabled connections as needed. Show the name, base URL, and authentication method and ask the user to choose one. Reuse any connection list you already have that contains no secrets. To see more results, pass the returned `nextCursor` to `--cursor`. If you confirm that there are no usable connections, ask whether to add one.
8
8
 
@@ -10,17 +10,17 @@ List the supplier's enabled connections as needed. Show the name, base URL, and
10
10
  openany-dev seller connections list --application APPLICATION_ID -j
11
11
  ```
12
12
 
13
- Confirm that the selection belongs to the current supplier and is enabled. Record its `id` and `revision`. Fetch the details by ID only if the existing receipt lacks required fields. If the connection's base URL or authentication method conflicts with known upstream information, ask the user to confirm. The resource configuration supplies the endpoint path. Do not use that path to match connections.
13
+ Confirm that the selection belongs to the current supplier and is enabled. Record its `id` and `revision`. Fetch the details by ID only if the existing receipt lacks required fields. If the connection's base URL or authentication method conflicts with known service information, ask the user to confirm. The resource configuration supplies the endpoint path. Do not use that path to match connections.
14
14
 
15
- ## Add a new upstream key
15
+ ## Add a new connection
16
16
 
17
- If the user chooses to add a key and has not supplied connection fields, run the command below immediately and wait for the dialog result. The dialog collects the connection name, base URL, authentication method, required parameter name, and API key in one step. Use the confirmed supplier ID and the operation identifier to open the dialog. Skip the connection schema lookup and do not ask for connection fields beforehand.
17
+ If the user chooses to add a connection and has not supplied connection fields, run the command below immediately and wait for the dialog result. The dialog collects the connection name, base URL, authentication method, required parameter name, and API key in one step. Use the confirmed supplier ID and the operation identifier to open the dialog. Skip the connection schema lookup and do not ask for connection fields beforehand.
18
18
 
19
19
  ```bash
20
20
  openany-dev seller connections create --application APPLICATION_ID --operation OPERATION --gui -j
21
21
  ```
22
22
 
23
- On success, use the `id` and `revision` from the receipt. Read the connection back only if the receipt lacks required fields. For imports, use the connection ID as `upstreamKeyId`. If the user cancels the dialog or it times out, preserve the current progress and wait for instructions.
23
+ On success, use the `id` and `revision` from the receipt. Read the connection back only if the receipt lacks required fields. For imports, use the connection ID as `connectionId`. If the user cancels the dialog or it times out, preserve the current progress and wait for instructions.
24
24
 
25
25
  If the native dialog is unavailable and no connection fields have been supplied, ask the user to run the command below in their local interactive terminal in the same environment. The terminal collects the connection fields in one step and hides key input. When finished, the user only needs to provide the connection ID.
26
26
 
@@ -28,7 +28,7 @@ If the native dialog is unavailable and no connection fields have been supplied,
28
28
  openany-dev seller connections create --application APPLICATION_ID --operation OPERATION
29
29
  ```
30
30
 
31
- If the user has already supplied any connection fields, keep the valid values, ask only for missing fields, and prepare `connection.json`. Set `label`, `baseUrl`, and `authType`. For `query` or `path` authentication, set `authParamName` as well. Keep credentials, query strings, and fragments out of the base URL. Use authorized `OPENANY_DEV_UPSTREAM_API_KEY` injection or have the user pass the key through local stdin with hidden input. Use `authType: "none"` only when the upstream is confirmed to require no authentication.
31
+ If the user has already supplied any connection fields, keep the valid values, ask only for missing fields, and prepare `connection.json`. Set `label`, `baseUrl`, and `authType`. For `query` or `path` authentication, set `authParamName` as well. Keep credentials, query strings, and fragments out of the base URL. Use authorized `OPENANY_CONNECTION_API_KEY` injection or have the user pass the key through local stdin with hidden input. Use `authType: "none"` only when the service is confirmed to require no authentication.
32
32
 
33
33
  ```bash
34
34
  openany-dev seller connections create --application APPLICATION_ID --operation OPERATION --file connection.json -j
@@ -1,8 +1,8 @@
1
- # 选择上游 Key
1
+ # 选择连接
2
2
 
3
- 沿用已确认的 CLI、邮箱会话和供应商。Dev 环境将下方命令中的 `openany-dev` 替换为 `openany-dev`。需要绑定上游 Key 且用户尚未指定时,先单独问「这次要从已有的上游 Key 中选择,还是新建上游 Key?」等用户选择后进入对应分支。用户已明确选定连接或要求新建时,直接进入对应分支。
3
+ 沿用已确认的 CLI、邮箱会话和供应商。Dev 环境将下方命令中的 `openany-dev` 替换为 `openany-dev`。需要绑定连接且用户尚未指定时,先单独问「这次要选择已有连接,还是新建连接?」等用户选择后进入对应分支。用户已明确选定连接或要求新建时,直接进入对应分支。
4
4
 
5
- ## 从已有 Key 中选择
5
+ ## 选择已有连接
6
6
 
7
7
  按需列出该供应商已启用的连接,展示名称、Base URL 和认证方式,让用户选一条。已有无秘密的连接列表时直接复用;需要查看更多时,将回执的 `nextCursor` 传给 `--cursor`。确认没有可用连接后,询问是否新建。
8
8
 
@@ -10,9 +10,9 @@
10
10
  openany-dev seller connections list --application APPLICATION_ID -j
11
11
  ```
12
12
 
13
- 核对所选连接归属当前供应商且已启用,记录 `id` 和 `revision`。已知 ID 且现有回执缺少必需字段时,按 ID 查详情。若连接的 Base URL 或认证方式与已知上游信息冲突,先请用户确认。接口路径由资源配置提供,不能用它判断连接是否匹配。
13
+ 核对所选连接归属当前供应商且已启用,记录 `id` 和 `revision`。已知 ID 且现有回执缺少必需字段时,按 ID 查详情。若连接的 Base URL 或认证方式与已知服务信息冲突,先请用户确认。接口路径由资源配置提供,不能用它判断连接是否匹配。
14
14
 
15
- ## 新建上游 Key
15
+ ## 新建连接
16
16
 
17
17
  用户选择新建且尚未提供连接字段时,Agent 直接执行下方命令并等待弹框结果。弹框一次完成连接名称、Base URL、认证方式、必要的参数名和 API Key 的填写。弹框前只使用已确认的供应商 ID 和本次操作标识,跳过连接 schema 查询和连接字段提问。
18
18
 
@@ -20,7 +20,7 @@ openany-dev seller connections list --application APPLICATION_ID -j
20
20
  openany-dev seller connections create --application APPLICATION_ID --operation OPERATION --gui -j
21
21
  ```
22
22
 
23
- 创建成功后使用回执中的 `id` 和 `revision`。回执缺必要字段时才回读;导入绑定使用连接 ID 作为 `upstreamKeyId`。弹框取消或超时时,保留当前任务进度,等待用户指示。
23
+ 创建成功后使用回执中的 `id` 和 `revision`。回执缺必要字段时才回读;导入绑定使用连接 ID 作为 `connectionId`。弹框取消或超时时,保留当前任务进度,等待用户指示。
24
24
 
25
25
  原生弹框不可用且尚未提供连接字段时,请用户在同一环境的本地交互终端运行下方命令。终端一次收集连接资料并隐藏 Key 输入;用户完成后只需提供连接 ID。
26
26
 
@@ -28,7 +28,7 @@ openany-dev seller connections create --application APPLICATION_ID --operation O
28
28
  openany-dev seller connections create --application APPLICATION_ID --operation OPERATION
29
29
  ```
30
30
 
31
- 用户已提供部分或全部连接字段时,复用有效值,只补缺项,由 Agent 准备 `connection.json`。配置包含 `label`、`baseUrl` 和 `authType`,`query` 或 `path` 认证还需 `authParamName`。Base URL 不含凭据、查询串或片段。通过已授权的 `OPENANY_DEV_UPSTREAM_API_KEY` 注入,或请用户在本地使用隐藏输入将 Key 通过 stdin 传给 CLI。只有已确认无需认证时才使用 `authType: "none"`。
31
+ 用户已提供部分或全部连接字段时,复用有效值,只补缺项,由 Agent 准备 `connection.json`。配置包含 `label`、`baseUrl` 和 `authType`,`query` 或 `path` 认证还需 `authParamName`。Base URL 不含凭据、查询串或片段。通过已授权的 `OPENANY_CONNECTION_API_KEY` 注入,或请用户在本地使用隐藏输入将 Key 通过 stdin 传给 CLI。只有已确认无需认证时才使用 `authType: "none"`。
32
32
 
33
33
  ```bash
34
34
  openany-dev seller connections create --application APPLICATION_ID --operation OPERATION --file connection.json -j
@@ -2,9 +2,9 @@
2
2
 
3
3
  ## Shortest workflow
4
4
 
5
- 1. Follow the [connection workflow](connections.md) first. Confirm an enabled upstream connection owned by the supplier. Reuse a confirmed connection or ask the user to select or add one. Confirm the connection before requesting or reading source materials. Use the [bindings template](../templates/bindings.json) when creating or changing bindings.
5
+ 1. Follow the [connection workflow](connections.md) first. Confirm an enabled connection owned by the supplier. Reuse a confirmed connection or ask the user to select or add one. Confirm the connection before requesting or reading source materials. Use the [bindings template](../templates/bindings.json) when creating or changing bindings.
6
6
  2. Follow the [publishing workflow](publishing.md) to collect and read the resource URL, documentation, or file. Reuse a compliant file, and ask only about gaps or conflicts. Check the selected connection against the source base URL and authentication method. If they conflict, ask the user to confirm which connection to use.
7
- 3. Run the appropriate `preview` once. Include `--bindings-file bindings.json` if bindings are already available. Record the batch `id` and check `summary`, `stage`, `missingFields`, and `errorCode` for anything to supply. Preview only validates. It creates no resources and makes no upstream calls.
7
+ 3. Run the appropriate `preview` once. Include `--bindings-file bindings.json` if bindings are already available. Record the batch `id` and check `summary`, `stage`, `missingFields`, and `errorCode` for anything to supply. Preview only validates. It creates no resources and makes no service calls.
8
8
  4. Run `run` to create drafts. For bindings completed after preview, use the returned item IDs and submit them with `run --bindings-file bindings.json`. Read each item's status, `operation`, and `resourceId` from the receipt. If the user requested only drafts, report the result and stop. For verification or publication, apply the [publishing workflow](publishing.md) to each item.
9
9
 
10
10
  ```bash
@@ -17,7 +17,7 @@ Each batch can contain up to 100 items. JSON files can be up to 8 MiB. Use strin
17
17
 
18
18
  ### V2 standard API or Agent API file
19
19
 
20
- If you already have a `provider-agent-api-v2` file, use its `apis` directly. To create a file from business materials, use the [standard API template](../templates/provider-agent-api-template.json) for a standard API or the [Agent API template](../templates/seller-agent-api-import-template.json) for Skill, Bot, Service, Data, or Goods. Preserve the selected [resource type](publishing.md) in `catalogType`. These resources require valid HTML body content in `includedContentHtml`, `usageInstructionsHtml`, and `effectContentHtml`, up to 32 KiB each. Standard APIs can omit them. For these imports, `apiDescription` must be at least 150 characters after trimming. The template's explanatory section is ignored during import. The API item ID is `METHOD /path` and the binding points to `upstreamKeyId`.
20
+ If you already have a `provider-agent-api-v2` file, use its `apis` directly. To create a file from business materials, use the [standard API template](../templates/provider-agent-api-template.json) for a standard API or the [Agent API template](../templates/seller-agent-api-import-template.json) for Skill, Bot, Service, Data, or Goods. Preserve the selected [resource type](publishing.md) in `catalogType`. These resources require valid HTML body content in `includedContentHtml`, `usageInstructionsHtml`, and `effectContentHtml`, up to 32 KiB each. Standard APIs can omit them. For these imports, `apiDescription` must be at least 150 characters after trimming. The template's explanatory section is ignored during import. The API item ID is `METHOD /path` and the binding points to `connectionId`.
21
21
 
22
22
  ```bash
23
23
  openany-dev seller imports preview --type api --file api-v2.json --application ID -j
@@ -2,9 +2,9 @@
2
2
 
3
3
  ## 最短流程
4
4
 
5
- 1. 先按[中文连接流程](connections.zh-CN.md)确认归属当前供应商且已启用的上游连接。复用已确认的连接,或请用户选择已有连接或新建。连接确认后再读取或索取资料。创建或修改绑定时使用[绑定模板](../templates/bindings.json)。
5
+ 1. 先按[中文连接流程](connections.zh-CN.md)确认归属当前供应商且已启用的连接。复用已确认的连接,或请用户选择已有连接或新建。连接确认后再读取或索取资料。创建或修改绑定时使用[绑定模板](../templates/bindings.json)。
6
6
  2. 按[上架流程](publishing.zh-CN.md)收集并读取资源网址、文档或文件。直接复用合规文件,仅补缺项或冲突。根据资料核对已选连接的 Base URL 和认证方式,如不匹配,先请用户确认适用的连接。
7
- 3. 执行对应分支的 `preview` 一次。已有绑定就带上 `--bindings-file bindings.json`。记录批次 `id`,从 `summary`、`stage`、`missingFields` 和 `errorCode` 判断要补什么。预览只校验,不创建资源或调用上游。
7
+ 3. 执行对应分支的 `preview` 一次。已有绑定就带上 `--bindings-file bindings.json`。记录批次 `id`,从 `summary`、`stage`、`missingFields` 和 `errorCode` 判断要补什么。预览只校验,不创建资源或调用服务。
8
8
  4. 执行 `run` 创建草稿。预览后才补齐的绑定按返回项目 ID 填写,直接随 `run --bindings-file bindings.json` 提交。读取回执中的逐项状态、`operation` 和 `resourceId`。只要求草稿时报告结果即结束;需要验证或发布时按[上架流程](publishing.zh-CN.md)逐项处理。
9
9
 
10
10
  ```bash
@@ -17,7 +17,7 @@ openany-dev seller imports run --batch BATCH_ID --application ID -j
17
17
 
18
18
  ### V2 API 或服务文件
19
19
 
20
- 已有 `provider-agent-api-v2` 文件就直接用其中的 `apis`。从业务资料新建文件时,普通 API 用[普通 API 模板](../templates/provider-agent-api-template.json),Skill、Bot、Service、Data 和 Goods 用 [Agent API 模板](../templates/seller-agent-api-import-template.json),按[资源上架流程](publishing.zh-CN.md)保留所选的 `catalogType`。这些资源的 `includedContentHtml`、`usageInstructionsHtml`、`effectContentHtml` 均需有效 HTML 正文,每字段最多 32 KiB;普通 API 可省略。这些导入条目的 `apiDescription` 去掉首尾空白后至少 150 个字符。说明区不参与导入。API 项目 ID 为 `METHOD /path`,绑定指向 `upstreamKeyId`。
20
+ 已有 `provider-agent-api-v2` 文件就直接用其中的 `apis`。从业务资料新建文件时,普通 API 用[普通 API 模板](../templates/provider-agent-api-template.json),Skill、Bot、Service、Data 和 Goods 用 [Agent API 模板](../templates/seller-agent-api-import-template.json),按[资源上架流程](publishing.zh-CN.md)保留所选的 `catalogType`。这些资源的 `includedContentHtml`、`usageInstructionsHtml`、`effectContentHtml` 均需有效 HTML 正文,每字段最多 32 KiB;普通 API 可省略。这些导入条目的 `apiDescription` 去掉首尾空白后至少 150 个字符。说明区不参与导入。API 项目 ID 为 `METHOD /path`,绑定指向 `connectionId`。
21
21
 
22
22
  ```bash
23
23
  openany-dev seller imports preview --type api --file api-v2.json --application ID -j
@@ -9,9 +9,9 @@ openany-dev seller schema --type model --application APPLICATION_ID -j
9
9
  openany-dev seller models create --application APPLICATION_ID --file model.json --operation TASK-model-create-1 -j
10
10
  ```
11
11
 
12
- Prepare `model.json` against the current schema: `price` and `routes`, using the supplier's actual model identity, capabilities, quote, currency, upstream endpoints, mappings, and route choices. Prices are decimal strings with at most six fractional digits; token prices use the existing per-million-token unit. Bind routes to owned connection IDs and required connection revisions. Never copy response-only ownership, activation, or publication fields into a write payload. Record the returned `price.id` as `MODEL_ID`.
12
+ Prepare `model.json` against the current schema: `price` and `routes`, using the supplier's actual model identity, capabilities, quote, currency, service endpoints, mappings, and route choices. Prices are decimal strings with at most six fractional digits; token prices use the existing per-million-token unit. Bind routes to owned connection IDs and required connection revisions. Never copy response-only ownership, activation, or publication fields into a write payload. Record the returned `price.id` as `MODEL_ID`.
13
13
 
14
- `price.model` is the supplier's upstream model ID (`key_market_model_prices.public_model`). `routes[0].publicModel` is the OpenAny route model ID (`key_market_model_routes.public_model`) used in client requests. These may differ: for example, `price.model: "vendor-chat-v2"` and `routes[0].publicModel: "my-chat"`. Saving derives the route's upstream model from `price.model`; do not add a third writable identity. Editing either ID does not rename the other. Manage one route per model.
14
+ `price.model` is the supplier's service model ID. `routes[0].publicModel` is the OpenAny route model ID used in client requests. These may differ: for example, `price.model: "vendor-chat-v2"` and `routes[0].publicModel: "my-chat"`. Saving derives the route's service model from `price.model`; do not add a third writable identity. Editing either ID does not rename the other. Manage one route per model.
15
15
 
16
16
  ### Non-token pricing
17
17
 
@@ -37,7 +37,7 @@ If the live CLI schema disagrees with the current website fields (for example, m
37
37
  openany-dev seller models get --application APPLICATION_ID --id MODEL_ID -j
38
38
  ```
39
39
 
40
- Save `version`, `price.id`, and each route's `id`, `upstreamKeyId`, and `upstreamRevision`. Use saved route IDs, not array indices or local import item IDs. Read `price.upstreamPath` to choose the authorized endpoint. If this is a draft-only task, report the draft ID and stop here.
40
+ Save `version`, `price.id`, and each route's `id`, `connectionId`, and `connectionRevision`. Use saved route IDs, not array indices or local import item IDs. Read `price.servicePath` to choose the authorized endpoint. If this is a draft-only task, report the draft ID and stop here.
41
41
 
42
42
  ## 3. Verify every route
43
43
 
@@ -50,8 +50,8 @@ For each route, create a separate non-secret verification file with these fields
50
50
  | --- | --- |
51
51
  | `expectedVersion` | Saved model `version` |
52
52
  | `routeId` | Saved `routes[].id` for this route |
53
- | `expectedUpstreamRevision` | That route's current `upstreamRevision`; recheck the connection if needed |
54
- | `endpointIndex` | Zero-based index of the selected endpoint in `price.upstreamPath` |
53
+ | `expectedConnectionRevision` | That route's current `connectionRevision`; recheck the connection if needed |
54
+ | `endpointIndex` | Zero-based index of the selected endpoint in `price.servicePath` |
55
55
  | `request` | Authorized test request (`path`, `query`, `headers`, `body` as applicable), without credentials |
56
56
 
57
57
  ```bash
@@ -65,7 +65,7 @@ openany-dev seller models get --application APPLICATION_ID --id MODEL_ID --verif
65
65
  {
66
66
  "expectedVersion": "SAVED_MODEL_VERSION",
67
67
  "routeId": "SAVED_ROUTE_ID",
68
- "expectedUpstreamRevision": 1,
68
+ "expectedConnectionRevision": 1,
69
69
  "endpointIndex": 0,
70
70
  "request": {
71
71
  "path": {},
@@ -79,9 +79,9 @@ openany-dev seller models get --application APPLICATION_ID --id MODEL_ID --verif
79
79
  }
80
80
  ```
81
81
 
82
- Replace the version, route ID, revision, endpoint index and test body with the saved configuration and authorized test inputs. For models, `request.path` must be an empty object `{}` when supplied, never `"/v1/chat/completions"` or a nonempty parameter map. The actual URL path comes from `price.upstreamPath[endpointIndex]`. A string fails backend JSON decoding before URL construction or an upstream call; the CLI now rejects it locally. API path parameter objects are a separate contract. A generic 400 alone is not evidence that CLI permissions are insufficient or that verification requires the web UI.
82
+ Replace the version, route ID, revision, endpoint index and test body with the saved configuration and authorized test inputs. For models, `request.path` must be an empty object `{}` when supplied, never `"/v1/chat/completions"` or a nonempty parameter map. The actual URL path comes from `price.servicePath[endpointIndex]`. A string fails backend JSON decoding before URL construction or a service call; the CLI now rejects it locally. API path parameter objects are a separate contract. A generic 400 alone is not evidence that CLI permissions are insufficient or that verification requires the web UI.
83
83
 
84
- Record the verification response `id` before querying it. Use a distinct operation/file for each route. A usable receipt has `state: "passed"`, is not stale, and matches this `modelId`, `modelVersion`, `routeId`, `upstreamKeyId`, and `upstreamRevision`. Testing may incur costs; obey the authorized scope and budget. Query an unfinished known receipt within the task deadline instead of repeating verify. For unknown outcomes, follow [recovery](reviews.md).
84
+ Record the verification response `id` before querying it. Use a distinct operation/file for each route. A usable receipt has `state: "passed"`, is not stale, and matches this `modelId`, `modelVersion`, `routeId`, `connectionId`, and `connectionRevision`. Testing may incur costs; obey the authorized scope and budget. Query an unfinished known receipt within the task deadline instead of repeating verify. For unknown outcomes, follow [recovery](reviews.md).
85
85
 
86
86
  ## 4. Publish
87
87
 
@@ -9,9 +9,9 @@ openany-dev seller schema --type model --application APPLICATION_ID -j
9
9
  openany-dev seller models create --application APPLICATION_ID --file model.json --operation TASK-model-create-1 -j
10
10
  ```
11
11
 
12
- 按当前 schema 准备 `model.json` 的 `price` 和 `routes`。使用实际模型标识、能力、报价、币种、上游端点和映射。价格用最多六位小数的字符串。按 token 计价时沿用每百万 token 单位。绑定归属当前供应商的连接及其修订,省略仅在响应中提供的归属、启用和发布字段。记录返回的 `price.id` 为 `MODEL_ID`。
12
+ 按当前 schema 准备 `model.json` 的 `price` 和 `routes`。使用实际模型标识、能力、报价、币种、服务端点和映射。价格用最多六位小数的字符串。按 token 计价时沿用每百万 token 单位。绑定归属当前供应商的连接及其修订,省略仅在响应中提供的归属、启用和发布字段。记录返回的 `price.id` 为 `MODEL_ID`。
13
13
 
14
- `price.model` 是供应商的上游模型 ID,`routes[0].publicModel` 是客户端使用的 OpenAny 路由模型 ID。两者可以不同,例如 `vendor-chat-v2` 和 `my-chat`。保存时从 `price.model` 得到路由的上游模型,每个模型管理一条路由。
14
+ `price.model` 是供应商的服务模型 ID,`routes[0].publicModel` 是客户端使用的 OpenAny 路由模型 ID。两者可以不同,例如 `vendor-chat-v2` 和 `my-chat`。保存时从 `price.model` 得到路由的服务模型,每个模型管理一条路由。
15
15
 
16
16
  ### 非 token 计价
17
17
 
@@ -33,13 +33,13 @@ V2 导入的 `inputPrice` 和 `outputPrice` 分别映射到这两个价格字段
33
33
  openany-dev seller models get --application APPLICATION_ID --id MODEL_ID -j
34
34
  ```
35
35
 
36
- 记录 `version`、`price.id` 和各路由的 `id`、`upstreamKeyId`、`upstreamRevision`。验证使用保存的路由 ID。按 `price.upstreamPath` 选择获授权的端点。只建草稿时报告 ID 后结束。
36
+ 记录 `version`、`price.id` 和各路由的 `id`、`connectionId`、`connectionRevision`。验证使用保存的路由 ID。按 `price.servicePath` 选择获授权的端点。只建草稿时报告 ID 后结束。
37
37
 
38
38
  ## 3. 验证每条路由
39
39
 
40
- 先核对已有回执。仅复用 `state: "passed"`、未过期且 `modelId`、`modelVersion`、`routeId`、`upstreamKeyId` 和 `upstreamRevision` 均匹配的结果。遇到运行中或结果未知的测试,先查询或核实。只有需要新验证且已获测试和费用授权时才运行一次。
40
+ 先核对已有回执。仅复用 `state: "passed"`、未过期且 `modelId`、`modelVersion`、`routeId`、`connectionId` 和 `connectionRevision` 均匹配的结果。遇到运行中或结果未知的测试,先查询或核实。只有需要新验证且已获测试和费用授权时才运行一次。
41
41
 
42
- 每条路由分别准备验证数据和操作名。字段为当前 `expectedVersion`、保存的 `routeId`、当前 `expectedUpstreamRevision`、从 0 开始的 `endpointIndex` 和获授权的 `request`。`request` 可包含 `path`、`query`、`headers`、`body`,凭据由连接提供。模型的 `request.path` 如有填写,只能是空对象 `{}`,实际路径来自 `price.upstreamPath[endpointIndex]`。可用 `--file PATH` 或 `--input 'JSON'` 传入同一结构,二选一。通用 400 错误需核对具体报错,再判断原因。
42
+ 每条路由分别准备验证数据和操作名。字段为当前 `expectedVersion`、保存的 `routeId`、当前 `expectedConnectionRevision`、从 0 开始的 `endpointIndex` 和获授权的 `request`。`request` 可包含 `path`、`query`、`headers`、`body`,凭据由连接提供。模型的 `request.path` 如有填写,只能是空对象 `{}`,实际路径来自 `price.servicePath[endpointIndex]`。可用 `--file PATH` 或 `--input 'JSON'` 传入同一结构,二选一。通用 400 错误需核对具体报错,再判断原因。
43
43
 
44
44
  ```bash
45
45
  openany-dev seller models verify --application APPLICATION_ID --id MODEL_ID --file route-verification.json --operation TASK-model-route1-test-1 -j
@@ -10,9 +10,9 @@ For a request to list a resource, if the request and already confirmed informati
10
10
 
11
11
  For Skill, Bot, Service, Data, or Goods, use the [Agent API template](../templates/seller-agent-api-import-template.json) and [Imports](imports.md). Set `catalogType` to the selected type: `skill`, `bot`, `service`, `data`, or `digital`, respectively. The template's `service` value is an example.
12
12
 
13
- When an upstream connection is needed and still undecided, use the native form to choose an existing connection or add one. Follow [Connections](connections.md), reusing confirmed connections and using the secure dialog when no connection fields have been collected. For a connection-only task, stop once you confirm the ID and revision.
13
+ When a connection is needed and still undecided, use the native form to choose an existing connection or add one. Follow [Connections](connections.md), reusing confirmed connections and using the secure dialog when no connection fields have been collected. For a connection-only task, stop once you confirm the ID and revision.
14
14
 
15
- Confirm the required upstream connection before requesting or reading source materials. When the source is missing, open a separate **Source materials** form with the options applicable to the chosen type: resource or API documentation link, sanitized cURL, file upload, or absolute local path. If the form allows only three options, group the two file options and ask how to provide the file next. In the form prompt, show the matching [Agent API](../templates/seller-agent-api-import-template.json), [standard API](../templates/provider-agent-api-template.json), or [model](../templates/models-v2.json) template location and say: “The template location is provided here. If you do not have a copy, download the template, fill it in, then upload the completed file or enter its absolute path.” Use an accessible absolute URL or verified local absolute path. If the location is inaccessible, attach the template and name it in the form. For Agent API listings, point to `fieldGuide` and the examples in `apis[0]`. Ask for the chosen input separately if the form cannot collect it.
15
+ Confirm the required connection before requesting or reading source materials. When the source is missing, open a separate **Source materials** form with the options applicable to the chosen type: resource or API documentation link, sanitized cURL, file upload, or absolute local path. If the form allows only three options, group the two file options and ask how to provide the file next. In the form prompt, show the matching [Agent API](../templates/seller-agent-api-import-template.json), [standard API](../templates/provider-agent-api-template.json), or [model](../templates/models-v2.json) template location and say: “The template location is provided here. If you do not have a copy, download the template, fill it in, then upload the completed file or enter its absolute path.” Use an accessible absolute URL or verified local absolute path. If the location is inaccessible, attach the template and name it in the form. For Agent API listings, point to `fieldGuide` and the examples in `apis[0]`. Ask for the chosen input separately if the form cannot collect it.
16
16
 
17
17
  Read the chosen source and ask only about omissions or conflicts. Collect the included content, usage instructions, effect examples, and how the resource is delivered. If its delivery is unsupported by the CLI, explain the limitation before preparing a draft. Preserve the supplied methods, paths, mappings, and billing terms. Validate imports against the template. Fetch the schema once for direct creation.
18
18
 
@@ -32,7 +32,7 @@ Follow the [API and resource verification and publication workflow](apis.md) or
32
32
 
33
33
  - If the session is missing or expired, or the identity changed, follow [Login](login.md), confirm the intended account and supplier, and explicitly resume. Do not switch identities or authentication methods silently.
34
34
  - If the connection or commercial terms are missing, keep the draft or prepared inputs and report the specific missing fields. Do not switch authentication to `none` or fabricate credentials.
35
- - Check the upstream path only when publication reports an explicit upstream path error. For other conflicts, unknown results, admission errors, or publication errors, follow [Review results](reviews.md). Record error codes and resource or operation IDs while keeping secrets out of the report.
35
+ - Check the service path only when publication reports an explicit service path error. For other conflicts, unknown results, admission errors, or publication errors, follow [Review results](reviews.md). Record error codes and resource or operation IDs while keeping secrets out of the report.
36
36
  - Respect supplier admission and administrator permissions. Keep payment arrangements outside the onboarding workflow. Use the current version for authorized resource edits.
37
37
 
38
38
  ## Final report
@@ -1,4 +1,4 @@
1
- # API / 模型 / 资源上架与上游连接
1
+ # API / 模型 / 资源上架与连接
2
2
 
3
3
  沿用[主入口](../SKILL.zh-CN.md)确认的环境、账号和供应商,再收集资源资料。无可用供应商时,获授权后转入[供应商申请](application.zh-CN.md)。仅查历史审核时读[审核结果](reviews.zh-CN.md)。
4
4
 
@@ -10,9 +10,9 @@
10
10
 
11
11
  Skill、Bot、Service、Data、Goods 使用 [Agent API 模板](../templates/seller-agent-api-import-template.json),走[导入流程](imports.zh-CN.md),并按用户选定类型将 `catalogType` 分别填写为 `skill`、`bot`、`service`、`data`、`digital`。模板中的 `service` 只是示例。
12
12
 
13
- 需要上游连接且用户未指定时,用原生表单选择复用已有连接或新建。按[连接流程](connections.zh-CN.md)复用已确认的连接,按录入进度选择安全弹框或补齐字段。仅建连接时,确认 ID 和修订即结束。
13
+ 需要连接且用户未指定时,用原生表单选择复用已有连接或新建。按[连接流程](connections.zh-CN.md)复用已确认的连接,按录入进度选择安全弹框或补齐字段。仅建连接时,确认 ID 和修订即结束。
14
14
 
15
- 先确认本次需要的上游连接,再索取或读取资源资料。缺来源时,单独打开**资料来源**表单:按已选类型提供适用的资源或接口文档链接、脱敏 cURL、上传文件或本地绝对路径选项。表单最多支持三项时合并文件选项,下一步再问上传或路径。在表单题面显示对应的 [Agent API](../templates/seller-agent-api-import-template.json)、[普通 API](../templates/provider-agent-api-template.json)或[模型](../templates/models-v2.json)模板位置,并注明「这里已提供模板位置。如果你还没有模板,请先下载并填写,再上传填好的文件或输入本地绝对路径。」使用可访问的完整 URL 或已核实的本地绝对路径,位置不可访问时提供附件并在表单标出文件名。Agent API 资源请参考 `fieldGuide` 和 `apis[0]` 中的示例。表单无法接收所选资料时,再单独索取。
15
+ 先确认本次需要的连接,再索取或读取资源资料。缺来源时,单独打开**资料来源**表单:按已选类型提供适用的资源或接口文档链接、脱敏 cURL、上传文件或本地绝对路径选项。表单最多支持三项时合并文件选项,下一步再问上传或路径。在表单题面显示对应的 [Agent API](../templates/seller-agent-api-import-template.json)、[普通 API](../templates/provider-agent-api-template.json)或[模型](../templates/models-v2.json)模板位置,并注明「这里已提供模板位置。如果你还没有模板,请先下载并填写,再上传填好的文件或输入本地绝对路径。」使用可访问的完整 URL 或已核实的本地绝对路径,位置不可访问时提供附件并在表单标出文件名。Agent API 资源请参考 `fieldGuide` 和 `apis[0]` 中的示例。表单无法接收所选资料时,再单独索取。
16
16
 
17
17
  读取指定资料后只补问缺项或冲突,保留原方法、路径、映射和计费。收集交付内容、使用说明、效果示例和交付方式。如果 CLI 不支持该交付方式,建草稿前先说明限制。导入按模板校验,直接创建时取对应 schema 一次。
18
18
 
@@ -32,7 +32,7 @@ API 分类用顶层 `categories`,OpenAPI 导入写入元数据的 `configurati
32
32
 
33
33
  - 登录缺失/过期或身份发生变化:遵循[身份认证](login.zh-CN.md),确认目标账号和供应商,然后明确恢复执行。不得静默切换身份或认证方式。
34
34
  - 缺少连接或商业条款:保留草稿/已准备的输入,并报告具体缺失字段。不得将认证替换为 `none` 或编造凭据。
35
- - 发布明确报上游路径错误时才核对路径。其他冲突、未知结果、准入或发布错误按[审核结果](reviews.zh-CN.md)处理。记录错误码和资源/操作 ID,勿泄露秘密。
35
+ - 发布明确报服务路径错误时才核对路径。其他冲突、未知结果、准入或发布错误按[审核结果](reviews.zh-CN.md)处理。记录错误码和资源/操作 ID,勿泄露秘密。
36
36
  - 不得绕过供应商准入、冒充管理员,或将安排付款作为接入流程的一部分。已获授权的资源编辑应使用当前版本。
37
37
 
38
38
  ## 最终报告
@@ -11,7 +11,7 @@ An operation is bound to its request method, target path and JSON payload within
11
11
  | Failure | Required recovery |
12
12
  | --- | --- |
13
13
  | Create timed out or `OPERATION_UNCERTAIN` for a create | Retry the original create command with the identical file, original `--operation`, and `--resume`; the CLI reuses its original idempotency key. Do not create with a new name/key |
14
- | Verification has a known ID | Query that exact ID with the model/API `get --verification-id` command; do not repeat the upstream test |
14
+ | Verification has a known ID | Query that exact ID with the model/API `get --verification-id` command; do not repeat the service test |
15
15
  | Verification timed out with no ID | Read the resource and any exposed verification information; do not assume the newest receipt is yours. If the CLI output cannot positively identify the original test, retain the unknown operation and request reconciliation. Model configuration reads do not guarantee exposure of verification receipts |
16
16
  | Update or publication outcome unknown | Read current resource and reconcile against the original intent before another mutation. Do not replay an uncertain update, publication, or verification, even with `--resume` |
17
17
  | Version conflict or stale verification | Read current resource and connections, understand the changed inputs, correct if authorized, and reverify within budget. Never merely replace version numbers |
@@ -19,4 +19,4 @@ An operation is bound to its request method, target path and JSON payload within
19
19
  | `IDEMPOTENCY_CONFLICT` | Stop reusing that operation with changed input; reconcile the original outcome first |
20
20
  | Login/session or supplier changed | Follow [authentication](auth.md) and confirm the intended identity before explicitly resuming |
21
21
 
22
- A running/unknown/failed verification is never a pass. If a test cannot be reconciled, report the unresolved operation and stop that resource before publication; independent resources can continue. Preserve public error codes and IDs in the final report without copying secrets or upstream sensitive responses.
22
+ A running/unknown/failed verification is never a pass. If a test cannot be reconciled, report the unresolved operation and stop that resource before publication; independent resources can continue. Preserve public error codes and IDs in the final report without copying secrets or sensitive service responses.
@@ -1 +1 @@
1
- {"schemaVersion":1,"items":[{"itemId":"GET /v1/example","upstreamKeyId":"REPLACE_CONNECTION_ID"},{"itemId":"supplier-model-1","routes":[{"index":0,"upstreamKeyId":"REPLACE_CONNECTION_ID"}]}]}
1
+ {"schemaVersion":1,"items":[{"itemId":"GET /v1/example","connectionId":"REPLACE_CONNECTION_ID"},{"itemId":"supplier-model-1","routes":[{"index":0,"connectionId":"REPLACE_CONNECTION_ID"}]}]}
@@ -8,7 +8,7 @@
8
8
  "Enter amounts as strings in the currency specified by priceCurrency, with at most 6 decimal places.",
9
9
  "When usageUnit (mapped to billingUnit) is not token, outputPrice (mapped to actualCompletion) must be the string \"0\", meaning actualCompletion must be 0.",
10
10
  "In this example, inputPrice=\"1.000000\" means USD 1 per million input tokens.",
11
- "Select the upstream connection on the import page. Never enter real API keys in this template.",
11
+ "Select the connection on the import page. Never enter real API keys in this template.",
12
12
  "Replace the domain, model ID, and route.provider in example requests with your actual configuration."
13
13
  ],
14
14
  "timeExample": "UTC 01:00-04:00 corresponds to 09:00-12:00 China Standard Time (UTC+8)."
@@ -30,10 +30,10 @@
30
30
  "constraints": "At least one item is required. The file must not exceed 2 MiB. Model identifiers must be unique."
31
31
  },
32
32
  "models[].modelId": {
33
- "label": "Upstream model ID",
33
+ "label": "Service model ID",
34
34
  "type": "string",
35
35
  "required": true,
36
- "description": "The model ID recognized by the upstream service.",
36
+ "description": "The model ID recognized by the service.",
37
37
  "constraints": "A non-empty string.",
38
38
  "example": "qwen3.8-max"
39
39
  },
@@ -42,7 +42,7 @@
42
42
  "type": "string",
43
43
  "required": false,
44
44
  "description": "The ID callers provide in the request's model field.",
45
- "constraints": "Must be non-empty when provided. Defaults to the upstream model ID when omitted.",
45
+ "constraints": "Must be non-empty when provided. Defaults to the service model ID when omitted.",
46
46
  "example": "openany-qwen3.8-max"
47
47
  },
48
48
  "models[].modelDescription": {
@@ -173,15 +173,15 @@
173
173
  "example": 125000
174
174
  },
175
175
  "models[].endpoints": {
176
- "label": "Upstream endpoints",
176
+ "label": "Service endpoints",
177
177
  "type": "array<object>",
178
178
  "required": false,
179
- "description": "Specify the upstream endpoints used by the model.",
180
- "constraints": "Each item contains operationType, upstreamPath, and httpMethod.",
179
+ "description": "Specify the service endpoints used by the model.",
180
+ "constraints": "Each item contains operationType, servicePath, and httpMethod.",
181
181
  "example": [
182
182
  {
183
183
  "operationType": "generations",
184
- "upstreamPath": "/v1/chat/completions",
184
+ "servicePath": "/v1/chat/completions",
185
185
  "httpMethod": "POST"
186
186
  }
187
187
  ]
@@ -326,11 +326,11 @@
326
326
  "constraints": "A non-empty string, such as generations.",
327
327
  "example": "generations"
328
328
  },
329
- "models[].endpoints[].upstreamPath": {
330
- "label": "Upstream endpoint path",
329
+ "models[].endpoints[].servicePath": {
330
+ "label": "Service endpoint path",
331
331
  "type": "string",
332
332
  "required": true,
333
- "description": "Specify the path of the upstream request.",
333
+ "description": "Specify the path of the service request.",
334
334
  "constraints": "Must start with / and must not include a domain.",
335
335
  "example": "/v1/chat/completions"
336
336
  },
@@ -506,7 +506,7 @@
506
506
  "endpoints": [
507
507
  {
508
508
  "operationType": "generations",
509
- "upstreamPath": "/v1/chat/completions",
509
+ "servicePath": "/v1/chat/completions",
510
510
  "httpMethod": "POST"
511
511
  }
512
512
  ],
@@ -3,8 +3,8 @@
3
3
  "items": [{
4
4
  "itemId": "supplier-model-1",
5
5
  "configuration": {
6
- "price": {"model": "REPLACE_UPSTREAM_MODEL_ID", "description": "", "providerLogoUrl": "", "modelReleaseDate": null, "descriptionTranslations": {}, "modalities": [], "outModalities": [], "supportedFeatures": [], "contextWindowTokens": null, "maxOutputTokens": null, "upstreamPath": [], "bodySchema": {}, "curlExample": "", "currency": "USD", "billingType": "usage_flat", "billingUnit": "token", "actualPrompt": "REPLACE_QUOTE", "actualCompletion": "REPLACE_QUOTE"},
7
- "routes": [{"publicModel": "REPLACE_OPENANY_ROUTE_MODEL_ID", "familyId": null, "upstreamKeyId": null, "status": "active", "matchRules": {}, "operations": []}]
6
+ "price": {"model": "REPLACE_SERVICE_MODEL_ID", "description": "", "providerLogoUrl": "", "modelReleaseDate": null, "descriptionTranslations": {}, "modalities": [], "outModalities": [], "supportedFeatures": [], "contextWindowTokens": null, "maxOutputTokens": null, "servicePath": [], "bodySchema": {}, "curlExample": "", "currency": "USD", "billingType": "usage_flat", "billingUnit": "token", "actualPrompt": "REPLACE_QUOTE", "actualCompletion": "REPLACE_QUOTE"},
7
+ "routes": [{"publicModel": "REPLACE_OPENANY_ROUTE_MODEL_ID", "familyId": null, "connectionId": null, "status": "active", "matchRules": {}, "operations": []}]
8
8
  }
9
9
  }]
10
10
  }
@@ -98,10 +98,10 @@
98
98
  "example": "POST"
99
99
  },
100
100
  "apis[].publicPath": {
101
- "label": "Upstream API relative path",
101
+ "label": "Service API relative path",
102
102
  "type": "string",
103
103
  "required": true,
104
- "description": "Enter the upstream API's relative path. The public path is the same as the upstream path; the selected connection supplies the domain.",
104
+ "description": "Enter the service API's relative path. The public path is the same as the service path; the selected connection supplies the domain.",
105
105
  "constraints": "Required; must start with /; at most 2048 characters; use {parameterName} for path parameters.",
106
106
  "example": "/v1/text/process"
107
107
  },
@@ -109,7 +109,7 @@
109
109
  "label": "Request body format",
110
110
  "type": "string",
111
111
  "required": true,
112
- "description": "Enter the request body encoding accepted by the upstream API.",
112
+ "description": "Enter the request body encoding accepted by the service API.",
113
113
  "constraints": "Only none / application/json / application/x-www-form-urlencoded.",
114
114
  "example": "application/json"
115
115
  },
@@ -279,26 +279,26 @@
279
279
  "example": []
280
280
  },
281
281
  "apis[].config.parameterMappings": {
282
- "label": "Upstream parameter mappings",
282
+ "label": "Service parameter mappings",
283
283
  "type": "array<object>",
284
284
  "required": true,
285
- "description": "Forward caller parameters to specified upstream locations.",
286
- "constraints": "source references a declared parameter; target specifies an upstream location.",
285
+ "description": "Forward caller parameters to specified service locations.",
286
+ "constraints": "source references a declared parameter; target specifies a service location.",
287
287
  "example": []
288
288
  },
289
289
  "apis[].config.fixedHeaders": {
290
- "label": "Fixed upstream request headers",
290
+ "label": "Fixed service request headers",
291
291
  "type": "object",
292
292
  "required": false,
293
- "description": "Enter non-sensitive headers added to every forwarded upstream request.",
293
+ "description": "Enter non-sensitive headers added to every forwarded service request.",
294
294
  "constraints": "Values must be strings. Do not include credentials such as Authorization or Cookie, or reserved headers. Use {} if none.",
295
295
  "example": {}
296
296
  },
297
297
  "apis[].config.fixedBody": {
298
- "label": "Fixed upstream request body fields",
298
+ "label": "Fixed service request body fields",
299
299
  "type": "object",
300
300
  "required": false,
301
- "description": "Enter JSON fields added to every forwarded upstream request.",
301
+ "description": "Enter JSON fields added to every forwarded service request.",
302
302
  "constraints": "Enter a JSON object without secrets. Use {} if none.",
303
303
  "example": {}
304
304
  },
@@ -431,10 +431,10 @@
431
431
  "example": "body:/text"
432
432
  },
433
433
  "apis[].config.parameterMappings[].target": {
434
- "label": "Upstream parameter target",
434
+ "label": "Service parameter target",
435
435
  "type": "string",
436
436
  "required": true,
437
- "description": "Enter where the upstream API receives the parameter.",
437
+ "description": "Enter where the service API receives the parameter.",
438
438
  "constraints": "For example, body:/text refers to the /text field in the JSON request body. An identical source and target forwards it without changing its location.",
439
439
  "example": "body:/text"
440
440
  },
@@ -14,7 +14,7 @@
14
14
  "apiDescription must contain at least 150 Unicode characters after trimming, covering core capabilities, how to call the API, and use cases. Incomplete drafts can be previewed and edited; this requirement must be met before importing and saving.",
15
15
  "Select a catalogType: skill, bot, service, data, or digital. Fill in includedContentHtml, usageInstructionsHtml, and at least one complete effect example.",
16
16
  "For synchronous delivery, keep executionMode set to sync and asyncConfig set to null. For asynchronous delivery, use POST and copy the callback or poll option below. Update the API description and request and response examples to match your service.",
17
- "The asynchronous examples show fixed billing and an upstream acknowledgement. For polling, implement GET /v1/jobs/{task_id} and return the documented status and result fields. Keep credentials in the connection and webhook settings."
17
+ "The asynchronous examples show fixed billing and a service acknowledgement. For polling, implement GET /v1/jobs/{task_id} and return the documented status and result fields. Keep credentials in the connection and webhook settings."
18
18
  ],
19
19
  "pricingExample": "1,000 micro-USD per call, equivalent to USD 0.001.",
20
20
  "billingInstructions": "Each API must use exactly one billing method: fixed (per call) or usage (based on consumption). The example under apis uses fixed by default. For usage billing, replace config.billing in its entirety with billingOptions.usage.billing, then update the usage field and response example to match the actual response. Do not mix fields from the two billing methods or add both options from the guide to apis.",
@@ -154,10 +154,10 @@
154
154
  "example": "POST"
155
155
  },
156
156
  "apis[].publicPath": {
157
- "label": "Upstream API relative path",
157
+ "label": "Service API relative path",
158
158
  "type": "string",
159
159
  "required": true,
160
- "description": "Enter the upstream API's relative path. V2 uses it as both the public path and upstreamPathTemplate, including for async dispatch. The selected connection supplies the base URL.",
160
+ "description": "Enter the service API's relative path. V2 uses it as both the public path and servicePathTemplate, including for async dispatch. The selected connection supplies the base URL.",
161
161
  "constraints": "Required; must start with /; at most 2048 characters; use {parameterName} for path parameters.",
162
162
  "example": "/v1/text/process"
163
163
  },
@@ -165,7 +165,7 @@
165
165
  "label": "Request body format",
166
166
  "type": "string",
167
167
  "required": true,
168
- "description": "Enter the request body encoding accepted by the upstream API.",
168
+ "description": "Enter the request body encoding accepted by the service API.",
169
169
  "constraints": "Only none / application/json / application/x-www-form-urlencoded.",
170
170
  "example": "application/json"
171
171
  },
@@ -335,26 +335,26 @@
335
335
  "example": []
336
336
  },
337
337
  "apis[].config.parameterMappings": {
338
- "label": "Upstream parameter mappings",
338
+ "label": "Service parameter mappings",
339
339
  "type": "array<object>",
340
340
  "required": true,
341
- "description": "Forward caller parameters to specified upstream locations.",
342
- "constraints": "source references a declared parameter; target specifies an upstream location.",
341
+ "description": "Forward caller parameters to specified service locations.",
342
+ "constraints": "source references a declared parameter; target specifies a service location.",
343
343
  "example": []
344
344
  },
345
345
  "apis[].config.fixedHeaders": {
346
- "label": "Fixed upstream request headers",
346
+ "label": "Fixed service request headers",
347
347
  "type": "object",
348
348
  "required": false,
349
- "description": "Enter non-sensitive headers added to every forwarded upstream request.",
349
+ "description": "Enter non-sensitive headers added to every forwarded service request.",
350
350
  "constraints": "Values must be strings. Do not include credentials such as Authorization or Cookie, or reserved headers. Use {} if none.",
351
351
  "example": {}
352
352
  },
353
353
  "apis[].config.fixedBody": {
354
- "label": "Fixed upstream request body fields",
354
+ "label": "Fixed service request body fields",
355
355
  "type": "object",
356
356
  "required": false,
357
- "description": "Enter JSON fields added to every forwarded upstream request.",
357
+ "description": "Enter JSON fields added to every forwarded service request.",
358
358
  "constraints": "Enter a JSON object without secrets. Use {} if none.",
359
359
  "example": {}
360
360
  },
@@ -487,10 +487,10 @@
487
487
  "example": "body:/text"
488
488
  },
489
489
  "apis[].config.parameterMappings[].target": {
490
- "label": "Upstream parameter target",
490
+ "label": "Service parameter target",
491
491
  "type": "string",
492
492
  "required": true,
493
- "description": "Enter where the upstream API receives the parameter.",
493
+ "description": "Enter where the service API receives the parameter.",
494
494
  "constraints": "For example, body:/text refers to the /text field in the JSON request body. An identical source and target forwards it without changing its location.",
495
495
  "example": "body:/text"
496
496
  },
@@ -698,13 +698,13 @@
698
698
  "apis[].asyncConfig.adapter_type": {
699
699
  "type": "string",
700
700
  "required": "Required for async",
701
- "description": "Choose webhook or grok_bot, according to the upstream adapter.",
701
+ "description": "Choose webhook or grok_bot, according to the service adapter.",
702
702
  "example": "webhook"
703
703
  },
704
704
  "apis[].asyncConfig.delivery_mode": {
705
705
  "type": "string",
706
706
  "required": "Required for async",
707
- "description": "Use callback when the upstream sends the result, or poll when the gateway queries the upstream for the result.",
707
+ "description": "Use callback when the service sends the result, or poll when the gateway queries your service for the result.",
708
708
  "example": "callback"
709
709
  },
710
710
  "apis[].asyncConfig.timeout_secs": {
@@ -724,7 +724,7 @@
724
724
  "apis[].asyncConfig.poll": {
725
725
  "type": "object",
726
726
  "required": "Required for poll",
727
- "description": "Copy the poll option and use the fixed upstream path GET /v1/jobs/{task_id}. Use the platform task ID from task_id in the submission body or from the Idempotency-Key header for native HTTP JSON. Return HTTP 200 with a top-level status of running, succeeded, or failed. Include a top-level result on success. The optional polling interval is 1 to 300 seconds.",
727
+ "description": "Copy the poll option and use the fixed service path GET /v1/jobs/{task_id}. Use the platform task ID from task_id in the submission body or from the Idempotency-Key header for native HTTP JSON. Return HTTP 200 with a top-level status of running, succeeded, or failed. Include a top-level result on success. The optional polling interval is 1 to 300 seconds.",
728
728
  "example": {
729
729
  "publication": {},
730
730
  "path": "/v1/jobs/{task_id}",