Skip to main content

1. Set up

1

Create your organization

Sign up at app.weflayr.com and name your organization, or accept a teammate’s invitation to join theirs. See Organizations & projects.
2

Create an API key

In API keys, create a key with the Gateway scope to call the gateway, or the Management scope to send telemetry with the SDK or import past calls with the API. Importing a CSV needs no key.
.env
3

Top up your credits

Add credits from the balance at the bottom of the sidebar: your gateway calls and your benchmarks are paid from them.

2. Use the gateway, or just log your calls with telemetry, a CSV or via API

The gateway is the recommended way: it logs your calls, and lets you route them later.
1

Point your OpenAI client at the gateway

The gateway speaks the OpenAI format for every provider: keep your OpenAI client, change its base URL and key, and name any model.
See Responses and Chat completions for every field.

3. Benchmark a call

In Model benchmarks, click New benchmark, pick a call, and follow the steps: the examples to replay, the models to try, and the evaluators that judge their answers. See Create a benchmark. When it is done, the report shows the mix of models recommended for each objective, its quality against your current model and what it saves.

4. Route your calls

In Routing strategies, click New strategy, pick your benchmark, check its rules and save. Then send the strategy’s id as the model of your gateway calls:
From now on, change the models your calls use from the routing strategy.

5. Analyze and go further

  • Tag features and customers: name the product feature (feature_name) and the customer (customer_name) of each call to benefit from advanced analytics and routing options.
  • Analyze your calls: the Overview shows your AI cost and usage and the calls coming in live, and AI cost breaks your cost down per feature.
  • Track your margin: sync your revenue from Stripe or a CSV to see your margin per customer or to include them in your routing strategy.
  • Track an internal tool: for a tool with no revenue (a sales copilot, a support assistant), create an internal project to see the cost of each user against the key metrics the tool drives, such as meetings booked.
  • Get alerted: set alerts on your cost and margin.