managed-model-endpoints

npx skills add BioTender-max/awesome-bio-agent-skills --skill managed-model-endpoints --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Managed model endpoints A **managed model endpoint** is a model service the **daemon** owns: you register it **once**, then every `compute_provider` cell against it just works — the daemon swaps the resident model off the device (one model at a time, via the resident's own approved stop), runs your approved start script, waits for the readiness route, then runs your cell, streaming its lifecycle progress into the cell as it goes. You never run the container runtime yourself, never poll readiness in cells, and never see the credential value. Two verbs: `register()` (asks the user once) and ordinary inference cells. Container specifics — image, registry login, internal port, cache mount target, readiness route — come from the **model's own runbook skill**; this skill is the translation contract. ## Calling a registered endpoint — inference cells Calling a registered endpoint — use the `using-model-endpoint` skill (this skill is the REGISTRATION contract; that one documents the call side in full). The ONLY dispatch form is the `compute_provider` tool with the endpoint's registered name (`list_compute` shows them): ``` compute_provider(provider="boltz2-service", code=""" import reque

mkdir -p "$SERVICE_DIR/cache"
docker login persists auth in $DOCKER_CONFIG/config.json; scope it to the
service dir so the credential dies with the service (never ~/.docker).
export DOCKER_CONFIG="$SERVICE_DIR/.docker"
docker run -d --name boltz2-service \
if docker inspect boltz2-service >/dev/null 2>&1 && \
docker rm -f boltz2-service          # stale port mapping -- recreate below
fi
if docker inspect boltz2-service >/dev/null 2>&1; then
docker start boltz2-service          # warm wake -- no credential, no chown needed