Endpoint
Query parameters
string
Freeform query text. Matches against volume names, descriptions, keywords, and other catalog
metadata. Ranking and text relevance are bibliotheca-local.
string
Filter by component type. One of:
agent, skill, command, tool, hook, mcp-server,
lsp-server.string
Filter by runtime compatibility metadata. Matches volumes that declare compatibility with the
given runtime identifier (e.g.,
claude-code, cursor, opencode). Bibliothecas evaluate this
filter only for runtime version schemes they understand.string
Filter by provider declaration. Matches volumes that declare integration with the given provider
(e.g.,
github, slack, postgres).string
Filter by keyword. Matches volumes that include the given keyword in their
volume.toml keyword
list.string
Filter by publisher identifier or scope.
integer
default:"20"
Maximum number of results per page. Range: 1–100.
integer
default:"0"
Zero-based pagination offset. Use in combination with
limit to page through results.Example requests
Example response
Response fields
object[]
required
Matching catalog entries. Each item contains
name and latestVersion, with optional discovery
metadata such as description, role, providers, and components.integer
required
Total number of matching entries for the query.
integer
required
Page size applied to this response.
integer
required
Zero-based offset applied to this response.
Pagination
Uselimit and offset together to page through results:
Search result ordering and ranking are bibliotheca-local. There is no guaranteed stable global
ordering across bibliothecas unless a specific bibliotheca documents one.
Important limitations
- Search results are not resolver inputs. Never substitute a search response for a version index or exact release metadata during resolution.
- Ordering and ranking are bibliotheca-local. The same query may return results in different orders on different bibliothecas.
- Runtime and protocol compatibility filters are discovery aids only. Bibliothecas evaluate these filters only for version schemes they understand and must not claim portable compatibility rejection for unknown schemes.
- Search responses may be cached under ordinary HTTP semantics, but cached results do not guarantee freshness.