Developer platform

The MOI developer platform has two integration paths: one for calling models and one for operating product resources in a workspace. Before you start, determine which path your task needs because they use different base URLs, credentials, authentication headers, and resource scopes.

Two integration paths

Goal

Main objects

Start here

Call models

Models, chat, vectors, and reranking

Genesis Model API or the Genesis-compatible SDK

Operate product resources

Workspaces, data, workflows, knowledge bases, agents, and compute instances

Product API, Product SDK, or MOI-CLI

Genesis model calls are not scoped to a Product workspace. Providers, Backends, and Routers in Product configure model services for internal use by workflows, semantic models, or agents; they do not replace the Genesis model list or inference API.

Object relationships in a workspace

A workspace is the main governance boundary for product resources. It contains members, roles, data, workflows, and resources. Developers commonly obtain and use object IDs in the following relationships:

Workspace
├─ Workspace members (linked user accounts) and roles
├─ Catalog → databases → tables or volumes → files
├─ Connectors → import tasks → import runs
├─ Workflows → workflow jobs → workflow artifacts and data lineage
├─ Knowledge bases → knowledge sources and semantic configuration
├─ Agents → sessions or automation tasks → agent artifacts
└─ Compute instances, data publications, and data subscriptions

A user account is a platform-level login identity. A workspace member is that account’s membership in a specific workspace. Removing a workspace member removes only that workspace relationship; it does not delete the user account.

Order for your first integration

  1. Choose the Genesis or Product integration path for the task.

  2. Obtain the complete base URL and credentials for the current environment.

  3. Start with read-only discovery: list models in Genesis or workspaces in Product.

  4. Save the model, workspace, or resource IDs returned by the service.

  5. Then perform write operations such as creating, deploying, running, importing, publishing, or deleting.

Next steps

Last updated on