Guides - Start here

Endpoint Routing Naming conventions

Naming convention is: prefix / sufix

For example: openai/gpt-40

An endpoint routing name includes a sufix and a prefix, separated by a forward slash /.

Typical format for an endpoint follows high level the Digital Object Identifier format. There is a significant difference that the prefix is not enforced to start with 10.

We strongly recommend you follow the above format if you ever consider sharing any endpoints. We will strictly enforce this format for shared endpoints (see below).

Naming Enforcement

Private Endpoints

638Labs does not enforce the above identifier format strictly, but we strongly suggest you follow it.

Shared/Public Endpoints

Shared endpoints will be strictly enforced to the above format of prefix / sufix

Uniqueness Enforcement

Private Endpoints

Endpoint must be unique per account.

Shared Endpoints

Endpoint must be globally unique. If anbody else is using your endpoint, contact us and let us know. We will make best effort to investigate.

Endpoint Display Naming conventions

Display names only need to be alphanumeric, they are, as it says, for display only.

We recommend they match the actual routing naming convention, although for this should be a more human friendly/readable one.

Further reading

Digital Object Identifier

A DOI (Digital Object Identifier) is a unique string of characters that persistently identifies a specific digital object, like a journal article, dataset, or software, and provides a persistent link to it. DOIs are typically used to provide a stable and reliable way to refer to and find resources, even if the resource changes location or format