---
title: Reference
description: Detailed syntax for ParadeDB indexes, queries, aggregates, and SQL APIs
canonical: https://www.paradedb.com/docs/reference/overview
---
Reference is where the exact ParadeDB syntax lives. Use these pages when you need operators, functions, index options, configuration settings, or the rules that determine whether ParadeDB can accelerate a query.
Most ParadeDB features start with index design. Decide which columns and expressions belong in the ParadeDB index, including text fields, scalar fields used for filtering or sorting, JSON, arrays, composite fields, and vectors. Then choose the query pattern for your workload: full-text search, vector search, hybrid ranking, aggregates, facets, or joins.
If you are new to ParadeDB, start with [Getting Started](/start/install) and
[Architecture](/concepts/architecture).
## Building the Index
Create a ParadeDB index and choose the fields it should cover.
Understand the inverted, columnar, vector, and segment structures inside the
ParadeDB index.
Make fields available for filtering, sorting, grouping, and aggregates.
Index expressions, JSON, arrays, composite fields, and vectors.
## Querying the Index
Query text with match, term, phrase, proximity, fuzzy matching, regex,
filters, sorting, relevance scores, and highlighting.
Search `vector` values by semantic similarity and tune nearest-neighbor
retrieval for larger datasets.
Combine BM25 and vector rankings into a single result set with reciprocal
rank fusion.
## Composing Results
Push filters and Top K ordering into the same index-backed query.
Compute SQL aggregates, buckets, histograms, metrics, and facets from the
index.
Join search results with relational tables while keeping application data in
Postgres.
## API Surface
Look up query operators, vector operators, filter syntax, and aggregate
helpers.
Review the settings that control scans, aggregates, vectors, parallelism,
and diagnostics.
Look up callable SQL functions, signatures, compatibility names, and
lower-level helpers.