Search Schema

Retrieve the versioned filter and field schema accepted by World Search.

GET/api/search/schema

Related NOSIBLE resources

research & data

Explore the NOSIBLE World interface, inspect the World data dictionary, and browse the classification ontologies used by World.

How to use this endpoint

guidance

Fetch this schema before generating dynamic World Search filters. It is the machine-readable inventory of supported fields, operators, aliases, entity types, semantic controls, and ontology values. Cache it by revision and invalidate your cache when revision changes.

Response body

application/json

These are the fields you can build against. Nested names use dot notation; optional sections are called out in their descriptions.

schemastring

Schema contract identifier.

Example: nosible_world_search_schema_v1

revisioninteger

Revision of the field and operator catalog.

Example: 2

endpointstring

Canonical backend search endpoint represented by the catalog.

Example: POST /world/v1/search

search_typesstring[]

Supported retrieval modes.

Example: ["metadata","lexical","semantic","hybrid"]

semantic_inputsobject

How q, vector, and query_vector are interpreted by semantic retrieval.

Example: { "q": "server embeds text", "vector": "caller-supplied f32 vector; alias query_vector" }

operatorsobject

Operators supported by each field type, including the restricted string_set operator family.

Example: { "string": ["eq", "in", "contains"], "string_set": ["eq", "in", "all", "not_in", "contains", "prefix"], "number": ["gte", "between"] }

entity_typesstring[]

Indexed NER entity types used by entity_* and entity_any filter fields.

Example: ["EVENT","FAC","GPE","LANGUAGE","LAW","LOC","NORP","ORG","PERSON","PRODUCT","WORK_OF_ART"]

resolve_endpointstring

Canonical resolver route to use before constructing entity or ticker filters.

Example: GET /world/v1/resolve

logicalstring[]

Logical filter operators.

Example: ["and","or","not"]

geoobject

Shapes for bbox and geo_radius filters.

Example: { "bbox": { "shape": "[west_lng, south_lat, east_lng, north_lat]" }, "geo_radius": { "shape": { "lat": 0, "lng": 0, "km": 100 } } }

retrievalobject

Backend retrieval paths used for archive, live, and filtered semantic queries.

Example: { "archive_semantic": "global HNSW", "live_semantic": "rolling per-date HNSW", "filtered_semantic": "auto/usearch/exact" }

semantic_filter_modesstring[]

Semantic filter strategies.

Example: ["auto","usearch","exact"]

fieldsobject[]

Complete searchable and facetable field catalog, including aliases, types, and facet support.

Example: [{ name, type, aliases, facet }]

Responses and errors

HTTP

200Request succeeded. The response body is shown in the panel on the right.

400invalid_request — The date, filter, cursor, identifier, or request combination is invalid.

403access_denied — The requested archive date is outside the caller's World tier.

404not_found — The requested date, entity, ticker, or event does not exist in the accessible index.

410cursor_expired — The cursor was minted against a replaced index build. Restart pagination from the first page.

429rate_limited — The request exceeded the endpoint or account rate limit. Respect Retry-After when supplied.

501backend_not_configured — The World backend is not configured for this deployment.

502backend_error — The BFF could not obtain a valid response from the World backend.

504backend_timeout — The World backend or an upstream data source timed out.