Component
core/devtool/promptlayer
A hosted prompt registry, and the surface a team edits and versions its prompts on. A prompt is authored and versioned in the registry rather than in application source, each version carries a release label such as prod or staging, and an application fetches the prompt behind a label at run time over the platform's API — so moving a label to a new version changes what the application sends without a redeploy. The registry also keeps a log of the requests an application reports to it, which is how a prompt version and the behaviour it produced are read together. Nothing runs in the deployment for this component: the platform is operated by its publisher, and a deployment holds a contract and an API key rather than a process. Its realizations are therefore reference realizations, which emit only the wiring a consumer needs to reach the service and provision no compute. The base address is an operational value so it can be repointed — the platform's own client libraries read the same override — which is what lets a Release address a regional or self-managed installation without a consumer changing. Exports the base address and the release label to consumers via the uses topology, so a consuming component reads which registry to call and which label to ask for from one place rather than each of its own containers carrying a copy. The API key is not exported and is not held here: the environment-variable name a credential arrives under belongs to the consuming application, so a consumer that needs one declares the `credential` slot on the socket that reaches the registry and delivers it from its own container.
来源
- 内容摘要
- sha256:92a25049b151363681a42b74fee7280c2881ec9e50d5ed0701dbb2296733b5be
- 发布时间
- 2026-11-10T10:11:33Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:dcbc1f7679e84c2a769fdc4ff867ac939ba785f5fbc96aa733556fbfc4c2f77a
此版本的引用
oci://hub.aggrega.ai/component/core/devtool/promptlayer:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| prompt_label | string | prod | 是 | Release label an application resolves a prompt through. The label names a moving pointer rather than a fixed version, and that is the point: promoting a new prompt version onto this label changes what the application sends with no change here and no redeploy. A deployment that must pin an exact version asks for it in its own call rather than through this value. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| endpoint | string | https://api.promptlayer.com | 否 | Base address of the registry's API. It defaults to the publisher's public address and is stated here rather than fixed in a Recipe so an operator may repoint it — at a regional address, at an installation the operator has contracted for, or at a proxy the deployment routes egress through. A deterministic pointer string the runtime resolves; the compiler never contacts it. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| endpoint | string | — | 是 | Base URL of the registry's API an application fetches its prompts from. The Release supplies it, so an operator may point it at a different host without the application changing. |
| prompt_label | string | — | 是 | Release label an application resolves a prompt through, carried through from the label the Aggregate declared. Moving the label to another prompt version changes what the application sends without a redeploy. |
| protocol | string | — | 否 | How the published address is spoken to — `https`, since the registry is reached across the public network. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
未声明 uses 套接字。
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
未声明附加槽位。
自注入允许列表
env
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
此实体未使用目录中的任何内容。
被使用
实现
实现