Fetch records through an adapter
liquid_fetchRetrieve deterministic data from a connected API adapter using adapter_id and optional endpoint path, returning up to 100 mapped records without an LLM call.
Instructions
Fetch records through a connected adapter, mapped to the target_model you set at connect time — deterministic, no LLM call. Side effects: makes a read-only outbound HTTP(S) request to the connected API using the stored credentials; it is subject to that API's rate limits (Liquid throttles proactively and surfaces 429s with retry hints). Returns {records, data: [up to 100 mapped records], _meta}. Requires an adapter_id from liquid_connect. Use this to pull whole records; to filter/aggregate server-side and get a smaller answer use liquid_query instead; to size a pull before making it, call liquid_estimate first.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| adapter_id | Yes | An adapter id returned by liquid_connect (or listed by liquid_list_adapters). | |
| endpoint | No | Optional endpoint path to act on (e.g. "/users"); defaults to the adapter's primary endpoint. Use a path shown by liquid_connect / liquid_list_adapters. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| records | No | Number of records returned. | |
| data | No | Mapped records (a list, capped at 100; or a single object). | |
| _meta | No | Call metadata: adapter_id, service, endpoint, latency_ms (and records when applicable). | |
| error | No |