Skip to main content
Below are some examples of how to use the SDK to interact with the Galtea platform.

Importing the SDK

To initialize the Galtea class, you need to provide your API key obtained in the settings page of the Galtea platform.

Registering a Product

Registering a product is the first step to start using the Galtea platform. Product registration isn’t supported via the SDK, so you’ll need to do this from the dashboard.

Creating a Version

With a version, you can track changes to your product over time and compare different implementations.
More information about creating a version can be found here.

Creating a Test

With a Test you define the test cases to evaluate your product. You can create accuracy or security tests depending on your evaluation needs.
More information about creating a test can be found here.

Creating a Metric

Metrics help you define the criteria for evaluating the performance of your product. You can create custom Metrics tailored to your specific use cases.
More information about creating a metric can be found here.

Launching Evaluations

Evaluations assess the performance of a product version against test cases using specific metrics. They are now directly linked to sessions that contain all inference results.
More information about launching evaluations can be found here.

Retrieving Evaluation Results

Once the evaluations are completed, you can retrieve them to analyze the results.

Working with Pagination

When listing resources that may contain many items (products, tests, sessions, evaluations, etc.), the Galtea SDK uses pagination with a default limit of 10,000 items per request.

Basic Pagination Example

Understanding Pagination Parameters

All list methods in the Galtea SDK accept two pagination parameters:
  • offset: Number of items to skip before starting to collect results (default: 0)
  • limit: Maximum number of items to return in a single request (default: 10000)

Pagination Best Practices

  1. For large datasets: Use smaller limit values (e.g., 100) to reduce memory usage and improve response times
  2. For complete data retrieval: Implement pagination loops as shown in the example above
  3. For small datasets: If you know there are fewer than 10,000 items, you can omit pagination parameters
If you don’t specify a limit and have more than 10,000 items, only the first 10,000 will be returned. Always implement pagination for complete data retrieval when working with large datasets.

Pagination Across Different Resources

The same pagination pattern works for all list operations: