The Nebuly SDK enables you to monitor all the requests made to:

Both of them are supported also when using async mode. Text Generation models are supported also when using stream mode.

The process is straightforward, you just need to:

  • initialize the SDK with your API key
  • include the user_id in your original HF Hub method calls.

You can then use the platform to analyze the results and get insights about your LLM users.

​
Conversational Models

import nebuly

nebuly.init(api_key="<YOUR_NEBULY_API_KEY>")

from huggingface_hub import InferenceClient
client = InferenceClient()
output = client.conversational(
    "What's the meaning of life?",
    # ... other optional hf hub kwargs
    # Nebuly additional kwargs
    user_id="<YOUR_USER_ID>",
)

You can find a detailed explanation of the allowed nebuly additional keyword arguments below:

​
user_id
string
required

An id or username uniquely identifying the end-user. We recommend hashing their username or email address, in order to avoid sending us any identifying information.

​
nebuly_tags
dict

Tag user interactions by adding key-value pairs using this parameter. Each key represents the tag name, and the corresponding value is the tag value.

For example, if you want to tag an interaction with the model version used to reply to user input, provide it as an argument for nebuly_tags, e.g. {"version": "v1.0.0"}. You have the flexibility to define custom tags, making them available as potential filters on the Nebuly platform.

​
nebuly_api_key
string

You can use this field to temporarily override the Nebuly API key for the selected model call. The interaction will be stored in the project associated with the provided API key.

​
Text Generation Models

import nebuly

nebuly.init(api_key="<YOUR_NEBULY_API_KEY>")

from huggingface_hub import InferenceClient
client = InferenceClient()

output = client.text_generation(
    "When was Einstein born?",
    # ... other optional hf hub kwargs
    # Nebuly additional kwargs
    user_id="<YOUR_USER_ID>",
)

You can find a detailed explanation of the allowed nebuly additional keyword arguments below:

​
user_id
string
required

An id or username uniquely identifying the end-user. We recommend hashing their username or email address, in order to avoid sending us any identifying information.

​
nebuly_tags
dict

Tag user interactions by adding key-value pairs using this parameter. Each key represents the tag name, and the corresponding value is the tag value.

For example, if you want to tag an interaction with the model version used to reply to user input, provide it as an argument for nebuly_tags, e.g. {"version": "v1.0.0"}. You have the flexibility to define custom tags, making them available as potential filters on the Nebuly platform.

​
nebuly_api_key
string

You can use this field to temporarily override the Nebuly API key for the selected model call. The interaction will be stored in the project associated with the provided API key.

​
Track Traces

To track your huggingface traces we currently expose two different methodologies:

  • The chain of models: you can use the context manager integration built in in the nebuly SDK to catch all the model calls. More information can be found in the chain of models section.
  • Raw endpoints: you can directly use the exposed APIs to send the raw interactions and traces to the nebuly platform. You can find an example of usage of the endpoint here, while the formal endpoint definition is available here.