- Home
- Docs
- For developers
- API keys
No matches. Try a model format, tool name or error.
Which key do you need?
Three doors — pick the one that matches what you're building.
Open — no key working
Search, resolve, download plans, and agent discovery need no key at all. This works right now:
import requests
r = requests.get('https://huggingbay.xyz/api/v1/search',
params={'q': 'embedding', 'limit': 5}, timeout=20)
r.raise_for_status()
results = r.json()Account key — self-serve working
For saving: your library, collections, watchlists, saved-search alerts. It lets the API recognize your account; it can't change anything. One POST, no signup — the token is shown once, save it:
curl -sS -X POST 'https://huggingbay.xyz/api/account/reader-token' \
-H 'content-type: application/json' \
-d '{"displayName":"my app","purpose":"saving finds"}'Reader tokens can't publish artifacts or approve mirrors.
Hosted runs — Bay Run key unstable
Read this first: it minted a key when we checked today, but it has failed under load — don't build on it without checking first. Demo tier, 500 tasks a day. For running a model on our hosts instead of your machine:
curl -sS -X POST 'https://run.huggingbay.xyz/v1/keys/free' \
-H 'content-type: application/json' -d '{}'The 404 does not exist
POST /api/v1/keys doesn't exist. Old tutorials may point you at it — the three options above are what's real.