Thanks, my main problem was that /1/ did look dirty.
The /v1/ is much better, and solves the problem.
The /v1/ is much better, and solves the problem.
I'm choosing the /v1/ route because its a neat solution to the problem, it will work without serious issues and developers understand it easily.
Yes its not 110% REST, but I believe its the best solution to my problem. The fact that other major API's are taking the same route (Amazon,Twitter) just enforces the idea.