Require user LLM credentials
All checks were successful
build / build (push) Successful in 17s

This commit is contained in:
robert
2026-06-06 12:21:31 -03:00
parent 00ad0b8790
commit 64fd7c26f2
6 changed files with 40 additions and 48 deletions

View File

@@ -47,7 +47,7 @@ Three platform-managed bits land on the inner skill via `RunContext`:
| Field | Source | Required? |
|---|---|---|
| `ctx.workspace.bucket` | grant minted by the orchestrator | yes |
| `ctx.llm` | caller-selected LLM creds when available, otherwise a platform-scoped LiteLLM grant (Card declares `llm_provisioning=platform_or_caller_provided`) | yes |
| `ctx.llm` | caller's saved LLM credential, routed by the platform (Card declares `llm_provisioning=platform`) | yes |
| `ctx.cp_jwt` | caller's CP JWT (Card declares `wants_cp_jwt=True`) | yes — used by `cp_deploy_tarball` |
The user opts into all three when they pick `agent-builder` from the
@@ -55,11 +55,9 @@ marketplace — the dashboard already surfaces these on the agent card.
## Pricing
`$0.10 / call` during the current pricing model. The builder uses your
selected LLM creds when present and falls back to a scoped platform grant.
The deployed agent is yours forever; subsequent invocations of a generated LLM
agent default to scoped platform LLM grants unless you explicitly generate a
BYOK/caller-paid agent.
`$0.10 / call` during the current pricing model. The builder uses your saved
LLM credential. The deployed agent is yours forever; subsequent invocations of
a generated LLM agent also use the caller's saved LLM credential via `ctx.llm`.
## How to call it