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.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:92a25049b151363681a42b74fee7280c2881ec9e50d5ed0701dbb2296733b5be
Published
2026-11-10T10:11:33Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/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

Reference at this version

oci://hub.aggrega.ai/component/core/devtool/promptlayer:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
prompt_labelstringprodyesRelease 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.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
endpointstringhttps://api.promptlayer.comnoBase 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.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
endpointstring—yesBase 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_labelstring—yesRelease 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.
protocolstring—noHow the published address is spoken to — `https`, since the registry is reached across the public network.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

env

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy