---
title: "RegistryLookup"
description: "Both call shapes are supported on purpose."
url: "https://opsinjs.pensievelabs.org/reference/api/RegistryLookup"
source: "https://opsinjs.pensievelabs.org/reference/api/RegistryLookup.md"
section: "Reference"
kind: "reference"
---

> Elements written as `<PascalCase … />` below are opsinjs documentation
> components. Their attributes are the content: the values they render are
> generated from `tokens/*.json` and `registry/catalogue.ts` and are
> published separately at https://opsinjs.pensievelabs.org/r/index.json and under the Reference
> section.
> Nothing is missing from this page. The data simply does not live in
> the prose.

{/* GENERATED - do not edit. Source: the declaration named in the table below.
    Script: scripts/build-reference.mts. Change the doc comment on the symbol. */}

<PageTemplate kind="reference" />

## How this is generated [#how-this-is-generated]

Source: `lib/registry.ts`. Script: `scripts/build-reference.mts`. Command:
`pnpm run generate`.

Everything below is copied from the symbol, so a page is improved by improving
its doc comment. The [API index](./index.mdx) says why there is a page per
symbol and what these pages still do not carry.

{/* opsinjs:generated:begin - everything below is replaced by scripts/build-reference.mts */}

## RegistryLookup [#registrylookup]

Both call shapes are supported on purpose.

`getRegistryEntry("range-bar", base, style)` is what the preview surface and the machine routes call, and it reads naturally at a call site that already has three variables. The object form exists for the one caller that needs to pass a `kind`, and because a fourth positional argument is where a signature stops being readable.

| Kind | Declared in       |
| ---- | ----------------- |
| type | `lib/registry.ts` |

```ts
export type RegistryLookup = string | RegistryQuery
```

{/* opsinjs:generated:end */}