AI Agent Prompts for kspeeder Acceleration
When the operator already has kspeeder installed and running, AI agents should follow these fixed endpoints and hints to make Docker and GitHub traffic accelerate over the kspeeder stack:
-
Fixed TLS endpoints
- Docker:
https://registry.linkease.net:5443 - GHCR (GitHub Container Registry):
https://ghcr.linkease.net:5443
Alldocker pull,docker search,docker build, etc., must hit these hosts instead ofregistry-1.docker.ioor GitHub’s public domains.
- Docker:
-
DomainFold remap API
POST /api/domainfold/remap(JSON{"url":"<original URL>"}) orGET /api/domainfold/remap?url=<urlencoded>- Input can be
https://github.com/...,git@github.com:owner/repo.git, or any supported origin. - Response contains:
output: the alias URL (https://gh.linkease.net:5443/...)admin_path: the admin proxy path (/gh/...) that can be fetched viahttp://<kspeeder-host>:5003<admin_path>when DNS/TLS for*.linkease.netis unavailable.
- Always fetch the remapped alias for
curl,wget,git clone,pipinstalls, etc., so the download flows through the split-cache/GITHUB acceleration service.
-
Docker search and registry APIs
- Use
https://registry.linkease.net:5443/v1/search(and other/v1/endpoints) for looking up images, tags, or metadata. - When the agent needs metadata (e.g. for automation or discovery), call those endpoints on the accelerated host, not
registry.hub.docker.com.
- Use
-
AI prompt guidance
Provide AI agents a concise set of instructions so they know how to trigger acceleration consistently:TLS hosts: - Docker registry: https://registry.linkease.net:5443 - GitHub Container Registry: https://ghcr.linkease.net:5443 For GitHub URLs (https://github.com/... or git@github.com:owner/repo.git), POST to http://<kspeeder-host>:5003/api/domainfold/remap with {"url":"<raw>"} to receive: * output alias (e.g. https://gh.linkease.net:5443/...). * admin_path (e.g. /gh/...) if DNS/TLS is not trusted. Use the alias for downloads/clones; if TLS for *.linkease.net fails, fetch via http://<kspeeder-host>:5003<admin_path>. Before running docker commands, edit daemon config (or Docker Desktop settings) so `registry-mirrors` includes https://registry.linkease.net:5443, restart Docker, then run commands through that mirror. When searching images use https://registry.linkease.net:5443/v1/search (same host as pulls). -
Optional: Domain discovery
- Call
GET /api/domainfold/routesto list every supported prefix/alias host and the auto-generatedhttps://<alias>:5443URL. This helps the agent build new alias URLs before querying the remap API and avoid hitting blocked origins directly.
- Call
-
Common alias mappings
The TLS hosts under*.linkease.net:5443already cover many public repos and registries. AI agents forwarding any traffic (download, clone, API call) to the listed alias host should never go out to the origin domain directly. Pick whichever alias matches the service you need, e.g.:https://gh.linkease.net:5443 → https://github.com https://docker.linkease.net:5443 → https://registry-1.docker.io https://cr-ghcr.linkease.net:5443 → https://ghcr.io https://cr-gcr.linkease.net:5443 → https://gcr.io https://pypi.linkease.net:5443 → https://pypi.org https://pypi-files.linkease.net:5443 → https://files.pythonhosted.org https://npm.linkease.net:5443 → https://registry.npmjs.org https://maven.linkease.net:5443 → https://repo1.maven.org https://conda.linkease.net:5443 → https://repo.anaconda.com https://conda-community.linkease.net:5443 → https://conda.anaconda.org https://arch.linkease.net:5443 → https://geo.mirror.pkgbuild.com https://debian.linkease.net:5443 → https://deb.debian.org https://ubuntu.linkease.net:5443 → https://archive.ubuntu.com https://fedora.linkease.net:5443 → https://dl.fedoraproject.org https://opensuse.linkease.net:5443 → https://download.opensuse.org https://rocky.linkease.net:5443 → https://download.rockylinux.org https://rpm.linkease.net:5443 → https://registry.opensuse.org https://codeberg.linkease.net:5443 → https://codeberg.org https://codeberg.linkease.net:5443 → https://codeberg.org https://cr-cloudsmith.linkease.net:5443 → https://docker.cloudsmith.io https://cr-digitalocean.linkease.net:5443 → https://registry.digitalocean.com https://cr-gitlab.linkease.net:5443 → https://registry.gitlab.com https://cr-gitpod.linkease.net:5443 → https://registry.gitpod.io https://cr-k8s.linkease.net:5443 → https://registry.k8s.io https://cr-mcr.linkease.net:5443 → https://mcr.microsoft.com https://cr-opensuse.linkease.net:5443 → https://registry.opensuse.org https://cr-oracle.linkease.net:5443 → https://container-registry.oracle.com https://cr-quay.linkease.net:5443 → https://quay.io https://cr-redhat.linkease.net:5443 → https://registry.redhat.io https://cr-suse.linkease.net:5443 → https://registry.suse.com https://cr-vmware.linkease.net:5443 → https://projects.registry.vmware.com https://cran.linkease.net:5443 → https://cran.r-project.org https://crates.linkease.net:5443 → https://crates.io https://ip-*.*.linkease.net:5443 → mirrors for AI APIs (OpenAI, Anthropic, Cohere, etc.) https://aosp.linkease.net:5443 → https://android.googlesource.com https://apache.linkease.net:5443 → https://downloads.apache.org https://arxiv.linkease.net:5443 → https://arxiv.org https://civitai.linkease.net:5443 → https://civitai.com https://fdroid.linkease.net:5443 → https://f-droid.org https://gist.linkease.net:5443 → https://gist.github.com https://gitea.linkease.net:5443 → https://gitea.com https://gl.linkease.net:5443 → https://gitlab.com https://golang.linkease.net:5443 → https://proxy.golang.org https://gradle.linkease.net:5443 → https://plugins.gradle.org https://hf.linkease.net:5443 → https://huggingface.co https://homebrew.linkease.net:5443 → https://github.com/Homebrew https://homebrew-api.linkease.net:5443 → https://formulae.brew.sh/api https://homebrew-bottles.linkease.net:5443 → https://ghcr.io https://ip-*.*.linkease.net:5443 → API mirrors for various AI companies (OpenAI, HuggingFace, etc.)If an exact alias is missing for your desired origin,
GET /api/domainfold/routeswill show the available prefix and target so you can derive the alias host manually.
By writing these steps into the prompt, every AI agent that installs Docker, downloads from GitHub, clones repositories, or queries Docker metadata will automatically use kspeeder’s accelerated DNS/HTTPS tunnels.