Mar 19, 2026

Semantic Search Upgrade for Client API v1

This release puts semantic search at the center of Client API v1 so teams can build meaning-based discovery experiences, not just keyword matching.

Why this matters

Your users can search by intent ("decentralized exchange", "web3 venture fund"), while integrations stay predictable with explicit ranking metadata and performance-focused controls.

Semantic Search First

Meaning-based ranking on list endpoints
- Cards: GET /v1/cards/ with search=...&semantic=1
- Participants: GET /v1/participants/ with search=...&semantic=1
- Filters still control what is included; semantic mode controls ranking by relevance.
Explicit relevance signal
- similarity is returned for semantic results.
- Score range: 0.0-1.0 (higher is a stronger semantic match).
- min_similarity lets you tune result strictness for your UX.
Transparent ranking metadata
- Response meta.semantic exposes enabled, min_similarity, and ranking.
- Clients can reliably render semantic mode state and debug ranking behavior.

Platform additions that support semantic UX

Response metadata (meta) across key endpoints
- Cards list: GET /v1/cards/
- Participants list: GET /v1/participants/
- Card interactions: GET /v1/cards/<slug>/interactions/
- Detail and batch endpoints include useful flags such as include_user_data and include_sources.
Flexible payload shaping for fast search UIs
- view=compact for lightweight rendering.
- fields=... for top-level field selection.
Fast pagination mode
- include_total=false on cards, participants, and card interactions.
- pagination.total is null in fast mode, while has_next remains accurate.
Cleaner payload quality
- Card location payload avoids placeholder-only location objects.
- user_data behavior is explicitly controlled via include_user_data=true.

Integration notes

To enable semantic ranking, always pair semantic=1 with search.
For tighter results, increase min_similarity; for broader discovery, lower it.
For search-heavy interfaces, combine semantic mode with view=compact or focused fields=....
Keep include_total=true if your pagination UI needs exact totals.
Send include_user_data=true only when personalization is needed.

👉 Read the updated API documentation