Some background: The API the discovery service is using is entirely open but the reason the implementation is not is because it has a dependency on storage (right now it's using our internal infrastructure storage) and so it wouldn't work anywhere else.

Even if we made it available, you would have to set up some kind of storage (consul, etcd, postgres, ...) for the discovery service to use, so it wouldn't solve that issue either.

@aluzzardi This is very helpful. Can you share instructions on what it requires to setup storage to work with token-based service?

The implementation we have internally uses PostgreSQL. consul/etcd/zookeeper are as simple to setup.

Is there a contract that needs to be honored by these services?