using-model-endpoint
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.
npx skills add BioTender-max/awesome-bio-agent-skills --skill using-model-endpoint --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You 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`). - Hosted endpoints: send `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. - Requests ride the sandbox HTTP proxy (`HTTP_PROXY`/`HTTPS_PROXY` are set) — don't disable it (e.g. `trust_env=False`) or the endpoint is unreachable. - No job lifecycle here (no submit/harvest) — direct request/response only. **Managed endpoints** (entries with `managed: true` / a `location` field in `list_compute`): their lifecycle — daemon-owned start/stop, registr
What does the using-model-endpoint skill do?
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.
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill using-model-endpoint --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.