Lyssna

Discover the Lyssna Data API surface before querying it. Call with no arguments first to get a compact catalog of every available operation (path, method, resource, summary, whether it is paginated, and which query tool applies). Then call again with a `path` copied verbatim from the catalog — including any {param} placeholders — and optionally its `method`, to get that operation's raw OpenAPI fragment plus every schema it references. Results are tagged by `mode`: `catalog` is the operation index; `operation` is the raw fragment plus reachable schemas; `too_large` means the fragment exceeded the size budget, so retry with both `path` and `method` to narrow it; `unavailable` means the spec could not be loaded and no cache exists, which is transient, so retry. An unknown `path` or `method` fails permanently (do not retry) and returns the valid paths or methods to choose from.

Fetch Data API data with a GET request. Source path and pathParams exactly from describe_data: template segments (e.g. {test_unique_id}) go in pathParams; all filters go in selectors, never as top-level arguments. Returns one of: a list result { rows, meta, guidance } for paginated (list) operations, or a detail result { data } for single-resource operations. For lists, follow meta.next_cursor by passing it as cursor on the next call; the guidance field states whether another page exists. page_size defaults to 50, max 100, and applies to list operations only. Non-ok statuses: invalid_request (fix path/selectors/pagination), not_available (resource missing or unauthorized), unavailable_retryable (retry later), and too_large (narrow selectors or reduce page_size, then retry).

Search Data API list data with a POST search request. Source path and pathParams exactly from describe_data: template segments (e.g. {test_unique_id}) go in pathParams; structured predicates go in filter, never as top-level arguments, flat selectors, raw body, or raw page objects. Returns a list result only: { rows, meta, guidance }. Follow meta.next_cursor by passing it as cursor on the next call; omit cursor for the first page. page_size defaults to 50, max 100; requests above the max are rejected by the tool contract. Use sort only when describe_data documents a supported search sort; the Data API validates sort values and filter shape. Non-ok statuses: invalid_request (fix path/filter/sort/pagination), not_available (resource missing or unauthorized), unavailable_retryable (retry later), and too_large (narrow filter or reduce page_size, then retry).