Unified query API

Query records. Inspect the graph. Use one shape.

RushDB applies the same SearchQuery-shaped request model across records and graph introspection. Applications and agents can filter stored data, discover labels, inspect relationships, read property metadata, and fetch distinct values or ranges before constructing the next query.

Start free View docs

Agents need data access and structure discovery to speak the same language.

A record query is only reliable when the caller knows which labels, fields, values, and graph paths actually exist. Separate discovery APIs with unrelated query syntax force applications to translate between models and encourage agents to guess.

Before

Query records through one interface
Inspect schema through unrelated metadata endpoints
Guess valid field values before filtering
Teach agents several incompatible request formats

With RushDB

Search records with labels, where clauses, sorting, and pagination
Discover labels and their record counts
Inspect relationships, property types, and property metadata
Load distinct values or numeric and datetime ranges before filtering

What it enables

One query contract for data and discovery.

The docs position SearchQuery as more than a record filter. It is also the pattern agents use to inspect labels, properties, relationships, values, ranges, and analytical projections before choosing the next query.

Build adaptive UIs

Fetch labels, property metadata, and distinct values or ranges to build filters that match the data actually present.

Support analytics inline

Use select expressions, groupBy, time buckets, and derived metrics for dashboard-style answers without exporting to another analytics store.

Reduce agent query drift

The same request shape teaches agents how to discover structure and then query records without switching mental models.

How it works

Start with the smallest useful path.

Discover the available structure

List labels, inspect properties, load distinct values or ranges, and search relationships before composing a dynamic query.

Reuse the same query shape

Apply familiar labels, where clauses, sorting, and pagination across record queries and introspection endpoints.

Query with grounded context

Filter records, traverse connected labels, and aggregate results after the caller knows the real fields and graph paths.

Flow

Discovery and query use the same shape

A product or agent can inspect available structure, choose valid filters, then query or aggregate records through one composable model.

Discover labels

Inspect properties

Load values

Build SearchQuery

Return records or metrics

Implementation sketch

One request shape across data and introspection.

These endpoints answer different questions, but they accept the same SearchQuery-shaped filtering model. An agent can inspect the project before it queries records.

# Query stored records
POST /api/v1/records/search

# Discover labels and record counts
POST /api/v1/labels/search

# Inspect property types and metadata
POST /api/v1/properties/search

# Load distinct values or numeric / datetime ranges
POST /api/v1/properties/:propertyId/values

# Search available graph relationships
POST /api/v1/relationships/search

# Shared SearchQuery-shaped body
{
  "labels": ["Article"],
  "where": { "status": "published" },
  "orderBy": { "registeredAt": "desc" },
  "limit": 20
}

Know the operational boundary.

Labels are discoverable

List the labels currently available in the project and inspect their record counts before selecting the scope for a query.

Read the Labels API guide

Properties carry metadata and values

Inspect property types and metadata, then fetch distinct values or numeric and datetime ranges before constructing filters.

Read the Properties API guide

Relationships are inspectable

Search the relationships already present in the graph before attempting a connected-data traversal.

Read the Relationships API guide

Ontology is the compact overview

Use SearchQuery-shaped endpoints for targeted inspection. Use the Ontology API when an agent needs one compact snapshot of labels, properties, values, ranges, relationships, and vector-index state.

Read the Ontology API guide

Read the SearchQuery guide

Next step

Build one focused workflow.

Start free

Related features

Explore all features