As far as making the connection point persistent, there is a way to accomplish that today, although it requires the use of a client side daemon. This is demonstrated in this sample script: http://forum.weaved.com/t/updated-script-for-fast-ssh-connections/623
The basic idea is that you use the service's UID along with a login token (retrieved from our cloud REST interface) to start the client side daemon and then that connection becomes available on 127.0.0.1:33000 (for example). The given script is hardwired for SSH but it can be modified to just return a URL instead of making the SSH connection for you.
Another possibility if you don't mind doing a little programming is to use our REST API documented at docs.remot3.it to grab the dynamic connection info.
The typical sequence is:
/user/login gives you a login token to use with the next 2 calls
/device/list/all pulls down JSON formatted list of all of your services
/device/connect, given the UID and token, will return a dynamic connection URL:port to use