gitea_admin/agent-builder
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: let builder use caller or platform llm
All checks were successful
build / build (push) Successful in 23s
Details

Browse Source
This commit is contained in:
robert
2026-05-26 10:52:09 -03:00
parent b9e63112d5
commit 7829e5c71e
8 changed files with 31 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
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` | platform-scoped LiteLLM grant (Card declares `llm_provisioning=platform`) | 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.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,8 +55,9 @@ marketplace — the dashboard already surfaces these on the agent card.
## Pricing
`$0.10 / call` during the current pricing model. The deployed
agent is yours forever; subsequent invocations of your agent run on
`$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 your agent run on
their own pricing (whatever you set when generating it).
## How to call it