api.v1: don't presume int or float in URLs

since `float` doesn't also catch `int` we don't want to encode every possible permutation (not that many, but the principle stands), just use `string` (default) and handle it later