Call a registered model endpoint over its native HTTP API from the endpoint's scoped inference kernel (BASE_URL preloaded). Load once a task needs predictions from a registered model endpoint.
59
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./configs/microservice/bff-service/configs/agent-skills/claude-science/using-model-endpoint/SKILL.mdYou are a pure HTTP client of BASE_URL. Each registered model endpoint
gets its own inference kernel — a Python REPL whose network egress is scoped
to exactly that endpoint — reached via
compute_provider({'provider': '<slug>', 'code': '…'}) (<slug> from
list_compute, without the infer: prefix).
BASE_URL is preloaded (as a Python variable AND as
os.environ["BASE_URL"]) — build request URLs from it, never hardcode
hosts/ports. Call the model's native API with httpx (preinstalled)
or requests; request shapes live in the provider's own runbook skill
(the registration's skillName).Authorization: Bearer $INFER_API_KEY (always the
canonical env name when a credential is delivered; the credential's own
name is usually aliased too). Local endpoints need no auth header.HTTP_PROXY/HTTPS_PROXY are set) —
don't disable it (e.g. trust_env=False) or the endpoint is unreachable.Managed endpoints (entries with managed: true / a location field in
list_compute): their lifecycle — daemon-owned start/stop, registration,
free_port()/register() — lives in the
managed-model-endpoints skill. Cells against them are still just
HTTP calls to BASE_URL; the daemon brings the model up on demand (a cold
start streams its progress into your cell and can take minutes).
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.