Experiential Labs icon

Experiential Labs

Experiential Labs is an open source AI gateway routing hosted providers, your keys, and GPUs via one OpenAI-compatible endpoint with access control, budgets, attribution, and caching.

Experiential Labs

Open source gateway for routed AI access

Experiential Labs is an open source AI gateway that puts multiple model providers behind one OpenAI-compatible endpoint. The product is built around a single API key and routing layer that can work with hosted providers, customer-owned keys, and customer-owned GPUs.

The site positions the gateway as a way to control routing, access, and attribution for agent traffic while keeping the provider's price on routed tokens. It also adds an intelligence layer that can suggest model changes, caching opportunities, and model training or optimization based on observed usage, with the option to self-host the whole gateway on your own infrastructure.

Core capabilities

One endpoint for multiple model sources

Route hosted providers, your own keys, and your own GPUs through a single OpenAI-compatible endpoint so agents can use one API key across model sources.

Access control and spend controls

Set budgets, hard caps, model allowlists, and key scopes at the org, team, person, agent, or tool level so requests are constrained at the gateway.

Request-level attribution and reporting

Attribute every request with route, fallback, tokens, and cost, then review usage by agent, person, model, or day in the console and usage API.

Traffic-aware routing suggestions

Use the intelligence layer to recommend cheaper or faster model routes, identify cache opportunities, and support per-prompt optimization based on observed traffic.

Prompt caching for repeated work

Turn on prompt caching for repeated tokens and keep the same prompts and workflow while reducing the effective token cost of repeated content.

Hosted or self-hosted deployment

Run the gateway on your own infrastructure or use the hosted service, with the core available as open source and self-hosting documented on the site.

Where it fits

  • Unify model access across an application stack

    Point agents, apps, or internal tools at a single base URL so model selection, provider failover, and cost attribution happen at the gateway instead of in each application.

  • Control spend and access for teams

    Use org policies, caps, and allowlists to keep a team, agent, or key within a planned budget while still letting requests route across multiple providers.

  • Reduce cost on recurring workloads

    Route repeated prompts through caching and let the intelligence layer surface cheaper routes or lower-effort settings when traffic patterns support it.

  • Run the gateway in your own environment

    Self-host the gateway when you want the endpoint, budgets, routing, and usage API on your own infrastructure rather than a managed deployment.

  • Deploy a model tuned to your workflow

    Use the case-study pattern to train or distill a model on your own workflow, then serve it behind the same endpoint as the rest of your model traffic.

Pros and Cons

Pros

  • Combines hosted providers, BYOK, and local or self-hosted models behind one endpoint.
  • Uses provider list price for routed tokens with 0% markup on routed tokens.
  • Adds budgets, hard caps, model allowlists, and request attribution at the gateway.
  • Offers an OpenAI-compatible /v1 endpoint and streaming support.
  • Can be self-hosted on your own infrastructure with open source core available.

Cons

  • The intelligence layer is not free on every plan; the pricing page says it is included in Pro and Enterprise and billed in credits.
  • Some enterprise capabilities are described as planned or available on request, including managed upgrades and backups, short-lived credentials, and some security review or support arrangements.

FAQ

How do you set it up?

The gateway exposes an OpenAI-compatible /v1 endpoint. The pricing page says the self-hosted gateway can be run on your own infrastructure with `uvx --from experiential exp run`, and the site shows examples for standard chat-completions requests.

Who is it for?

It is positioned for teams that want one endpoint for hosted providers, BYOK, and local or self-hosted models, plus routing, budgets, access control, and attribution. The pricing page also describes enterprise controls such as SSO, SCIM, advanced RBAC, private networking, and data residency.

What does the intelligence layer do?

The gateway routes requests through the cheapest healthy deployment that can serve a model, and the intelligence layer can also suggest model switches, caching opportunities, and per-prompt optimization based on observed traffic.

How does pricing work?

The site says routing uses the provider's list price with 0% markup on routed tokens. Credits are used across routed tokens and intelligence features, and requests stop at caps when credits run out.

Can you use your own keys or models?

Yes. The pricing page says BYOK and local models are included on Pro and Enterprise, and the home page says your own fine-tuned and self-hosted models can sit behind the same key.

Quick Facts

Category
AI gateway / developer tool
Platform
Web-based service with self-hosting option
Primary users
Teams and developers routing agent traffic across models
Source domain
experientiallabs.ai
API style
OpenAI-compatible /v1 endpoint
Pricing signal
Free plan, Pro plan, and Enterprise plan