Skip to main content

Large Language Models

The large language model (LLM) catalog uses a service-and-model hierarchy:
An LLM Service represents a provider or deployment boundary. Common types include OpenAI, Anthropic, and Amazon Bedrock. Other types cover Vertex AI, Ollama, and custom providers. An LLM Model captures identity, specifications, and evaluation results. It also tracks deployment, cost, and governance status. An LLM service name is globally unique. An LLM model uses the fully qualified name service.model, such as openai_production.gpt_5.

LLM Service Endpoints

The required create fields are name and serviceType. Valid service types are OpenAI, Anthropic, AzureOpenAI, Bedrock, VertexAI, Ollama, HuggingFace, and CustomLLM.

LLM Model Endpoints

The required create fields are name, baseModel, and the parent service’s fully qualified name in service. Optional metadata covers modelVersion, modelProvider, and modelSpecifications. Evaluation, cost, and deployment fields track operations. Regulatory compliance, ownership, domains, and data products add governance context.

Create a Service and Model

The Java example assumes a configured OpenMetadataClient named client.
Java SDK
The v2.0 Java SDK exposes both resources through the direct client. The v2.0 Python core SDK has no typed routes for LLM services or models, so use the REST API.

Update and Delete

Send an RFC 6902 JSON Patch document with Content-Type: application/json-patch+json to a PATCH endpoint. Set hardDelete=true on a DELETE request for permanent deletion. Restore a soft-deleted entity by sending its id to the corresponding /restore endpoint.