> ## Documentation Index
> Fetch the complete documentation index at: https://narev.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Import Helicone traces into a Narev benchmark

> Pull production LLM traces from Helicone into a Narev benchmark dataset so you can evaluate new models against real user prompts and conversations.

<Tip>
  Use your production traces as test datasets. Instead of guessing which model works better, test against the prompts
  your users are actually sending.
</Tip>

## Prerequisites

* An active Helicone account with production traces
* Helicone API key (starts with `sk-helicone-<token>`)
* Production traces in your Helicone project

## Setup

1. Create a new **A/B test**
2. Navigate to **Setup** tab
3. In the **Data Source** section select **Import from traces**
4. Select **Helicone** as provider
5. Enter your credentials:
   * **Project Name**: Your Helicone project identifier
   * **API Key**: Your Helicone API key (starts with `sk-helicone-<token>`)
6. Select your **Date Range** (default: last 7 days)
7. Click **Save Project** to import traces

<Frame>
  <img src="https://mintcdn.com/narev/Y1illty3WLN-yruS/images/benchmark/integration/helicone.webp?fit=max&auto=format&n=Y1illty3WLN-yruS&q=85&s=ec37ccd8e2aaf87f45c12dab414941c0" alt="Import traces from Helicone interface" width="1572" height="1296" data-path="images/benchmark/integration/helicone.webp" />
</Frame>

## Common questions

<AccordionGroup>
  <Accordion title="Do I need to modify my Helicone setup?">
    No. Narev reads from your existing Helicone project without any changes to your instrumentation.
  </Accordion>

  <Accordion title="Can I test models not in my current Helicone traces?">
    Yes. Narev imports prompts and usage patterns from Helicone, then lets you test any supported model provider on
    those same prompts.
  </Accordion>

  <Accordion title="Will Narev send data back to Helicone?">
    No. Narev imports traces to run experiments but doesn't write back to Helicone.
  </Accordion>

  <Accordion title="Does Narev work with Helicone custom properties?">
    Yes. Narev can import traces with custom properties and metadata from Helicone, which lets you optimize specific
    traffic segments.
  </Accordion>

  <Accordion title="How many traces should I import?">
    For most use cases, 50-500 traces provide statistically significant results. Start with 7 days of data by default.
    For high-variability workloads, import 30 days to capture edge cases.
  </Accordion>
</AccordionGroup>