AI Registry - Soft versioning
Introducing Soft Versioning.
Soft Versioning for Online AI Endpoints
Most AI registries focus on models and weights. But 638Labs is built for a different world: online, deployed endpoints — models, agents, and data services that are live and callable right now.
That changes how versioning works.
Why not enforce hard versioning?
In traditional software registries or package managers, versioning is critical because you’re distributing code or binaries. But in our model, you’re pointing to a live endpoint, not downloading anything.
So instead of managing version trees or enforcing git-like histories, we keep it simple:
-
If you deploy a new version, register a new route.
Example:
acme/agent-v1→ original
acme/agent-v2→ new endpoint -
Or reuse the same route and update the metadata:
"version": "2.1.0"
We call this soft versioning.
This is in testing for now, will be deployed soon
Why it works
- Keeps the registry light
- Lets you evolve your services without breaking users
- Encourages clear naming and route discipline
- Avoids overengineering a version system in a space where most tools (like GitHub or your CI/CD flow) already handle source tracking
When we’ll evolve this
As we introduce public marketplaces and more collaborative agent development, we’ll expand version support — but without sacrificing the simplicity of pointing to live, callable endpoints.
Until then, soft versioning keeps things lean and developer-friendly.
638Labs is a live registry and proxy for deployed AI services.
Learn more: https://638labs.com