> How data access works in Pylo, and where the query, filter, and mutation docs live

# Data

Every entity you define in Pylo gets the same data API: a list query, a by-ID query, and
create/update/delete mutations. The SDKs wrap this API with typed clients, so your schema determines
what you can query and what the results look like.

All surfaces share one query model:

- **Select**: pick fields and nested relations, get back exactly that shape
- **Filter**: conditions with AND/OR logic and operators per field type
- **Pagination**: page-based, with counts in every list response

The examples in this section use the Next.js SDK. The Node SDK client (`createPyloNode`) has the
same API as the Next.js server client. The [Reference](/reference/graphql-api) covers the raw
GraphQL operations.

  - [Querying](/data/querying): list, byId, selects, and relations
  - [Filtering & Sorting](/data/filtering-and-sorting): Operators, AND/OR, sorting, pagination
  - [Mutations](/data/mutations): Upsert, bulk upsert, delete, and relation updates
  - [Import & Export](/data/import-and-export): Move data in and out via the admin panel