Our platform provides a feature to define "custom models" (this is: models that may obey a particular user-defined format, provided its execution is comformant to our standard), which is documented here.

However, the platform also provides a way to deploy different versions of the model (this involves creating a new service that is meant to be accessible to the end user, which makes use of the model version to make predictions with the incoming data) in real-time and maintain related details, and a way to access that deployed API service to make predictions.

Real-time API section

In the models section, select any model and then select edit version. There you will find a tab named REAL-TIME API.

https://lh3.googleusercontent.com/0QgcY0chuITnHso2sLqzHKOF7nAp1NhbhHU575PSZxnUJtAI70heeLXXBVssm3aVXbjnkmjvThkKeqf8Jhz20k7lccyIsrNH--tZc5K74DAEJO4UbtxY7d8HfZQSJfyTJqZjDMkJ4asPGu53gWidilcf7jQD4Y23UGz0A3SdwZLMKa82copTU7h7Cg

There, the user can see a list of the already defined model versions and:

• See whether they're deployed or not.
• Deploy one or more of those versions.
• Assign a custom alias to one of those versions.
• Get the deployment details (in particular, their public URL) from one of those versions.

To access the deployed service (for a specific version), our platforms offers a gateway which allows the user to access the corresponding resource via two different methods:

• A default path, composed of both a model identifier and the chosen version's identifier.
• A customized path, composed of both a model identifier and the custom alias assigned to the chosen version.

The customized path is optional and can be assigned to one version of the model (custom paths are unique among versions in the same model - when a version gains a new alias, the sibling version having it previously will automatically lose it and have no customized path until a new one is assigned to it), and later changed as will.

The custom path will only consist of alphanumeric characters, underscores and hyphens.

This feature gives the end user flexibility to deploy new versions of a model and, by using custom paths and maintaining them across versions, update the service(s) without any need to change their client scripts to hit the gateway and make predictions.

https://lh4.googleusercontent.com/EjeSIkxtDbIBdkyr1mFDFXztgFU6h1vqZJBsvASWtFAFjlEBWN9colgIsOwF8SDkA7qwcab_J1ZalS93dHkJjFxjUE4D9M91cRjaZF4XKtrK4CEzh0YQQPn_kuumuDLw1j9pegjEeToV5L9Pci7H-pTm0YrkmTpRJTQHlX8e30w8i28w1Gr2lSVkrQ

Example:

https://lh5.googleusercontent.com/G0V8RX-mSeYN-he-eyCLUpyIeWTTYd4qOxv1T4IZjt-iXZ3UQeCqyxF8HNcadJfLB5rEWH9O5G_cpKf_52gez34s3br63h2Gb1KW69hvXa2Ixsj3e2OtJGsUy4FSADHsIRzXbnGE-MOHKfG-nBvAf8m98h6htxKW7tVJ71rPNQqegogRl26gNHZwzw

https://lh5.googleusercontent.com/EEgYvjYKT2F9vNoNsi-CLtsTAOZ1G7ZhhEyOr8alFo2bMBP-Uy8NUtspaTRzNmaipF5pWIxd64R9pnPRBXMZ2xnoiTYSJnC1s8zc-CuvprNOUC-iHawvmGa_r8r4Oz9m_jSoTkP6R0yOx8O5UpQaSZk8mkSW7JaqJ6dSYz-PMRcCPOPYHyzOze7jRA