periplus-python-sdk 0.11.0__tar.gz → 0.13.0__tar.gz

{periplus_python_sdk-0.11.0 → periplus_python_sdk-0.13.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: periplus-python-sdk
-Version: 0.11.0
+Version: 0.13.0
 Summary: Typed Periplus platform client with SQL and notebook integration
 License-Expression: AGPL-3.0-only
 Project-URL: Repository, https://github.com/elei-io/periplus
@@ -21,8 +21,9 @@ Dynamic: license-file
 # Periplus Python SDK
 
 Typed organization operations and SQL access through the Periplus HTTP API.
-The 0.11.0 platform interface requires the matching API release. It includes
-the source-snapshot metadata introduced in 0.10.0 alongside customer operations.
+The 0.12.0 platform interface requires the matching API release. It replaces the
+discovery, retention and monitoring namespaces with captures, crawls, pins and
+schedules, and includes the source-snapshot metadata introduced in 0.10.0.
 Install from PyPI:
 
 ```sh
@@ -46,7 +47,7 @@ Use HTTPS outside loopback development. Connect directly to the API origin,
 not the public marketing site.
 
 Version 0.9.0 requires personal API keys instead of database credentials. Create
-a key in the app's Settings → My API keys. It inherits your current access in
+a Developer key in the app's Access → SDK & API. It inherits your current access in
 that organization; SQL requires your membership to have `organization:sql:exec`.
 For local development, install `./clients/periplus-python-sdk` from the repository
 root and connect to `http://localhost:8000`.
@@ -55,9 +56,12 @@ root and connect to `http://localhost:8000`.
 returns typed columns/rows for read-only queries. `schema()` returns
 visible tables, column types/descriptions and helper documentation. All SQL uses
 `POST /api/v1/sql`; schema discovery uses `GET /api/v1/schema`. ClickHouse enforces
-permissions. The SDK never retries automatically, including failed queries.
+permissions. Buffered SQL reads retry HTTP 502, 503 and 504 up to twice with bounded
+backoff starting in 0.12.1. Set `sql_retries=0` to disable this, or choose up to three retries. Each
+attempt may observe a newer corpus snapshot. Mutations, transport failures and
+streamed queries are not retried automatically.
 
-Public HTML joins use `parse_id` and `node_index`; `document_id` identifies exact
+Public HTML joins use `capture_id` and `node_index`; `document_id` identifies exact
 raw bytes. Public shorthand uses the `public_v1` schema.
 
 In 0.10.0, `result.source_snapshot` is a typed `SourceSnapshot` containing
@@ -96,15 +100,16 @@ See [the public schema](../../docs/SCHEMA.md) and [query boundary](../../docs/QU
 
 ## Organization resources
 
-The same key selects your organization and inherits your live membership access.
+A Developer key selects your organization and uses your live membership access. Agent keys authenticate only to the hosted MCP endpoint, not this SDK.
 `Client` and `AsyncClient` expose the same namespaces:
 
 | Namespace | Operations |
 | --- | --- |
 | `identity`, `availability` | `get` |
-| `discovery` | `create`, `get`, `list`, `iter`, `arrivals`, `cancel` |
-| `retention`, `monitoring` | `create`, `preview`, `activate`, `get`, `list`, `iter`, `members`, `update`, `pause`, `resume`, `delete` |
-| `saved_queries` | `create`, `get`, `list`, `iter`, `rename`, `delete` |
+| `captures`, `crawls` | `create`, `get`, `list`, `iter`, `pages`, `cancel` |
+| `pins` | `create`, `get`, `list`, `iter`, `captures`, `update`, `delete` |
+| `schedules` | `create`, `get`, `list`, `iter`, `pages`, `captures`, `update`, `pause`, `resume`, `delete` |
+| `saved_queries` | `create`, `get`, `list`, `iter`, `update`, `rename`, `delete` |
 | `members` | `list`, `update_role`, `remove` |
 | `invitations` | `list`, `create`, `cancel` |
 | `api_keys` | `create`, `list`, `iter`, `revoke` |
@@ -112,30 +117,61 @@ The same key selects your organization and inherits your live membership access.
 | `query_history` | `list`, `iter`, `get`, `summary` |
 | `audit` | `list`, `iter` |
 
+Choose the resource by what you know and how long you need it:
+
+| Resource | Use it when |
+| --- | --- |
+| `captures` | You know the URLs (1–100) and need them in SQL now |
+| `crawls` | You know a starting point, not the URLs |
+| `pins` | You need exact captures for longer than seven days |
+| `schedules` | You need the same pages again later |
+
 ```python
 from periplus_sdk import Client
 
 with Client() as client:
-    preview = client.retention.preview(
+    capture = client.captures.create(urls=["https://example.com/pricing"])
+    capture = client.captures.get(capture, wait_seconds=30)
+    if capture.finished and capture.queryable:
+        for page in client.captures.pages(capture).items:
+            print(page.url, page.status, page.capture_id)
+
+    crawl = client.crawls.create(seeds=["https://example.com/docs/"], page_limit=200,
+                                 allowed_paths=["/docs/*"])
+
+    pin = client.pins.create(
         name="Research sources", days=90,
         sql="SELECT capture_id FROM captures WHERE domain(url) = ?",
         parameters=["example.com"],
     )
-    print(preview.id, preview.capture_count, preview.sample)
-    # Review the selection before calling:
-    # active = client.retention.activate(preview)
+    schedule = client.schedules.create(name="Pricing", every_days=7,
+                                       urls=["https://example.com/pricing"])
+    print(pin.captures, schedule.projected_pages_per_month)
 ```
 
-SQL previews persist inactive, frozen selections; activation never reruns SQL.
-Explicit IDs/URLs passed to `create` activate immediately. Monitoring URLs must
-already be known in the corpus. Use `members` and its `next_cursor` for complete
-membership: policy detail contains a sample. Updates/deletion accept a fetched
-`Policy` or an ID with `expected_version`; conflicts are never retried.
+Every capture is kept for seven days after collection unless a pin keeps it. A
+capture always fetches again and never returns an existing capture, so check
+coverage with SQL first. `request_id` (a capture or crawl `id`) is what you
+ordered; each page's `capture_id` is what the crawler produced and is the SQL key.
+`get(..., wait_seconds=N)` returns as soon as the request is finished and queryable,
+or after at most 30 seconds; the SDK never polls on its own.
+
+Pins and schedules accept explicit IDs/URLs or one read-only SQL query with
+parameters, and are active immediately. SQL runs once at creation and its exact
+result is locked in; running the same query beforehand is only an estimate.
+Schedule URLs need not be in the corpus. `pin_days` on a capture, crawl or schedule
+pins each successful capture it produces and requires `organization:pins:write`.
+`pins.update` changes `days` (moving every capture's expiry by the difference) or
+the name; `schedules.update` changes `every_days` or the name. Both accept a fetched
+object or an ID with `expected_version`; conflicts are never retried. Deletion needs
+no version: deleting a pin removes future protection, not captures.
 
 Paginated lists return `Page[T]` (`items`, `next_cursor`). Pass cursors unchanged
 or use `iter()`; membership/invitation lists are bounded snapshots instead.
-Offset-based lists can shift during concurrent changes. Query history and arrivals
-use keyset cursors. UTC usage ranges have an exclusive end date, at most 93 days.
+Offset-based lists can shift during concurrent changes. Query history, request
+page feeds and scheduled capture feeds use opaque keyset cursors. UTC usage ranges have an exclusive end date, at most 93 days. Usage reports pages
+captured (broken down by capture, crawl or schedule), challenge-resolution pages and
+pinned capture-days.
 Query history is best-effort and expires after 30 days; it is not a billing ledger.
 
 `ApiError` includes HTTP status, code, optional request ID, validation fields and

{periplus_python_sdk-0.11.0 → periplus_python_sdk-0.13.0}/README.md

@@ -1,8 +1,9 @@
 # Periplus Python SDK
 
 Typed organization operations and SQL access through the Periplus HTTP API.
-The 0.11.0 platform interface requires the matching API release. It includes
-the source-snapshot metadata introduced in 0.10.0 alongside customer operations.
+The 0.12.0 platform interface requires the matching API release. It replaces the
+discovery, retention and monitoring namespaces with captures, crawls, pins and
+schedules, and includes the source-snapshot metadata introduced in 0.10.0.
 Install from PyPI:
 
 ```sh
@@ -26,7 +27,7 @@ Use HTTPS outside loopback development. Connect directly to the API origin,
 not the public marketing site.
 
 Version 0.9.0 requires personal API keys instead of database credentials. Create
-a key in the app's Settings → My API keys. It inherits your current access in
+a Developer key in the app's Access → SDK & API. It inherits your current access in
 that organization; SQL requires your membership to have `organization:sql:exec`.
 For local development, install `./clients/periplus-python-sdk` from the repository
 root and connect to `http://localhost:8000`.
@@ -35,9 +36,12 @@ root and connect to `http://localhost:8000`.
 returns typed columns/rows for read-only queries. `schema()` returns
 visible tables, column types/descriptions and helper documentation. All SQL uses
 `POST /api/v1/sql`; schema discovery uses `GET /api/v1/schema`. ClickHouse enforces
-permissions. The SDK never retries automatically, including failed queries.
+permissions. Buffered SQL reads retry HTTP 502, 503 and 504 up to twice with bounded
+backoff starting in 0.12.1. Set `sql_retries=0` to disable this, or choose up to three retries. Each
+attempt may observe a newer corpus snapshot. Mutations, transport failures and
+streamed queries are not retried automatically.
 
-Public HTML joins use `parse_id` and `node_index`; `document_id` identifies exact
+Public HTML joins use `capture_id` and `node_index`; `document_id` identifies exact
 raw bytes. Public shorthand uses the `public_v1` schema.
 
 In 0.10.0, `result.source_snapshot` is a typed `SourceSnapshot` containing
@@ -76,15 +80,16 @@ See [the public schema](../../docs/SCHEMA.md) and [query boundary](../../docs/QU
 
 ## Organization resources
 
-The same key selects your organization and inherits your live membership access.
+A Developer key selects your organization and uses your live membership access. Agent keys authenticate only to the hosted MCP endpoint, not this SDK.
 `Client` and `AsyncClient` expose the same namespaces:
 
 | Namespace | Operations |
 | --- | --- |
 | `identity`, `availability` | `get` |
-| `discovery` | `create`, `get`, `list`, `iter`, `arrivals`, `cancel` |
-| `retention`, `monitoring` | `create`, `preview`, `activate`, `get`, `list`, `iter`, `members`, `update`, `pause`, `resume`, `delete` |
-| `saved_queries` | `create`, `get`, `list`, `iter`, `rename`, `delete` |
+| `captures`, `crawls` | `create`, `get`, `list`, `iter`, `pages`, `cancel` |
+| `pins` | `create`, `get`, `list`, `iter`, `captures`, `update`, `delete` |
+| `schedules` | `create`, `get`, `list`, `iter`, `pages`, `captures`, `update`, `pause`, `resume`, `delete` |
+| `saved_queries` | `create`, `get`, `list`, `iter`, `update`, `rename`, `delete` |
 | `members` | `list`, `update_role`, `remove` |
 | `invitations` | `list`, `create`, `cancel` |
 | `api_keys` | `create`, `list`, `iter`, `revoke` |
@@ -92,30 +97,61 @@ The same key selects your organization and inherits your live membership access.
 | `query_history` | `list`, `iter`, `get`, `summary` |
 | `audit` | `list`, `iter` |
 
+Choose the resource by what you know and how long you need it:
+
+| Resource | Use it when |
+| --- | --- |
+| `captures` | You know the URLs (1–100) and need them in SQL now |
+| `crawls` | You know a starting point, not the URLs |
+| `pins` | You need exact captures for longer than seven days |
+| `schedules` | You need the same pages again later |
+
 ```python
 from periplus_sdk import Client
 
 with Client() as client:
-    preview = client.retention.preview(
+    capture = client.captures.create(urls=["https://example.com/pricing"])
+    capture = client.captures.get(capture, wait_seconds=30)
+    if capture.finished and capture.queryable:
+        for page in client.captures.pages(capture).items:
+            print(page.url, page.status, page.capture_id)
+
+    crawl = client.crawls.create(seeds=["https://example.com/docs/"], page_limit=200,
+                                 allowed_paths=["/docs/*"])
+
+    pin = client.pins.create(
         name="Research sources", days=90,
         sql="SELECT capture_id FROM captures WHERE domain(url) = ?",
         parameters=["example.com"],
     )
-    print(preview.id, preview.capture_count, preview.sample)
-    # Review the selection before calling:
-    # active = client.retention.activate(preview)
+    schedule = client.schedules.create(name="Pricing", every_days=7,
+                                       urls=["https://example.com/pricing"])
+    print(pin.captures, schedule.projected_pages_per_month)
 ```
 
-SQL previews persist inactive, frozen selections; activation never reruns SQL.
-Explicit IDs/URLs passed to `create` activate immediately. Monitoring URLs must
-already be known in the corpus. Use `members` and its `next_cursor` for complete
-membership: policy detail contains a sample. Updates/deletion accept a fetched
-`Policy` or an ID with `expected_version`; conflicts are never retried.
+Every capture is kept for seven days after collection unless a pin keeps it. A
+capture always fetches again and never returns an existing capture, so check
+coverage with SQL first. `request_id` (a capture or crawl `id`) is what you
+ordered; each page's `capture_id` is what the crawler produced and is the SQL key.
+`get(..., wait_seconds=N)` returns as soon as the request is finished and queryable,
+or after at most 30 seconds; the SDK never polls on its own.
+
+Pins and schedules accept explicit IDs/URLs or one read-only SQL query with
+parameters, and are active immediately. SQL runs once at creation and its exact
+result is locked in; running the same query beforehand is only an estimate.
+Schedule URLs need not be in the corpus. `pin_days` on a capture, crawl or schedule
+pins each successful capture it produces and requires `organization:pins:write`.
+`pins.update` changes `days` (moving every capture's expiry by the difference) or
+the name; `schedules.update` changes `every_days` or the name. Both accept a fetched
+object or an ID with `expected_version`; conflicts are never retried. Deletion needs
+no version: deleting a pin removes future protection, not captures.
 
 Paginated lists return `Page[T]` (`items`, `next_cursor`). Pass cursors unchanged
 or use `iter()`; membership/invitation lists are bounded snapshots instead.
-Offset-based lists can shift during concurrent changes. Query history and arrivals
-use keyset cursors. UTC usage ranges have an exclusive end date, at most 93 days.
+Offset-based lists can shift during concurrent changes. Query history, request
+page feeds and scheduled capture feeds use opaque keyset cursors. UTC usage ranges have an exclusive end date, at most 93 days. Usage reports pages
+captured (broken down by capture, crawl or schedule), challenge-resolution pages and
+pinned capture-days.
 Query history is best-effort and expires after 30 days; it is not a billing ledger.
 
 `ApiError` includes HTTP status, code, optional request ID, validation fields and

{periplus_python_sdk-0.11.0 → periplus_python_sdk-0.13.0}/licensing/THIRD_PARTY_NOTICES.md

@@ -7,7 +7,7 @@ The Periplus license does not replace these terms.
 
 ## Selectolax and Lexbor
 
-The backend pins Selectolax 0.4.11 (MIT) and its bundled Lexbor 3.1.0
+The backend pins Selectolax 0.4.12 (MIT) and its bundled Lexbor 3.1.0
 (Apache-2.0). The DOM adapter's read-only native layouts follow Lexbor's DOM and
 HTML interface headers. Selectolax retains its packaged MIT license; Periplus
 includes Lexbor's license and notice under `licensing/third-party/lexbor/`

{periplus_python_sdk-0.11.0 → periplus_python_sdk-0.13.0}/pyproject.toml

@@ -2,7 +2,7 @@
 license = "AGPL-3.0-only"
 license-files = ["licensing/LICENSE", "licensing/NOTICE", "licensing/*.md"]
 name = "periplus-python-sdk"
-version = "0.11.0"
+version = "0.13.0"
 description = "Typed Periplus platform client with SQL and notebook integration"
 readme = "README.md"
 requires-python = ">=3.11"

{periplus_python_sdk-0.11.0 → periplus_python_sdk-0.13.0}/src/periplus_python_sdk.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: periplus-python-sdk
-Version: 0.11.0
+Version: 0.13.0
 Summary: Typed Periplus platform client with SQL and notebook integration
 License-Expression: AGPL-3.0-only
 Project-URL: Repository, https://github.com/elei-io/periplus
@@ -21,8 +21,9 @@ Dynamic: license-file
 # Periplus Python SDK
 
 Typed organization operations and SQL access through the Periplus HTTP API.
-The 0.11.0 platform interface requires the matching API release. It includes
-the source-snapshot metadata introduced in 0.10.0 alongside customer operations.
+The 0.12.0 platform interface requires the matching API release. It replaces the
+discovery, retention and monitoring namespaces with captures, crawls, pins and
+schedules, and includes the source-snapshot metadata introduced in 0.10.0.
 Install from PyPI:
 
 ```sh
@@ -46,7 +47,7 @@ Use HTTPS outside loopback development. Connect directly to the API origin,
 not the public marketing site.
 
 Version 0.9.0 requires personal API keys instead of database credentials. Create
-a key in the app's Settings → My API keys. It inherits your current access in
+a Developer key in the app's Access → SDK & API. It inherits your current access in
 that organization; SQL requires your membership to have `organization:sql:exec`.
 For local development, install `./clients/periplus-python-sdk` from the repository
 root and connect to `http://localhost:8000`.
@@ -55,9 +56,12 @@ root and connect to `http://localhost:8000`.
 returns typed columns/rows for read-only queries. `schema()` returns
 visible tables, column types/descriptions and helper documentation. All SQL uses
 `POST /api/v1/sql`; schema discovery uses `GET /api/v1/schema`. ClickHouse enforces
-permissions. The SDK never retries automatically, including failed queries.
+permissions. Buffered SQL reads retry HTTP 502, 503 and 504 up to twice with bounded
+backoff starting in 0.12.1. Set `sql_retries=0` to disable this, or choose up to three retries. Each
+attempt may observe a newer corpus snapshot. Mutations, transport failures and
+streamed queries are not retried automatically.
 
-Public HTML joins use `parse_id` and `node_index`; `document_id` identifies exact
+Public HTML joins use `capture_id` and `node_index`; `document_id` identifies exact
 raw bytes. Public shorthand uses the `public_v1` schema.
 
 In 0.10.0, `result.source_snapshot` is a typed `SourceSnapshot` containing
@@ -96,15 +100,16 @@ See [the public schema](../../docs/SCHEMA.md) and [query boundary](../../docs/QU
 
 ## Organization resources
 
-The same key selects your organization and inherits your live membership access.
+A Developer key selects your organization and uses your live membership access. Agent keys authenticate only to the hosted MCP endpoint, not this SDK.
 `Client` and `AsyncClient` expose the same namespaces:
 
 | Namespace | Operations |
 | --- | --- |
 | `identity`, `availability` | `get` |
-| `discovery` | `create`, `get`, `list`, `iter`, `arrivals`, `cancel` |
-| `retention`, `monitoring` | `create`, `preview`, `activate`, `get`, `list`, `iter`, `members`, `update`, `pause`, `resume`, `delete` |
-| `saved_queries` | `create`, `get`, `list`, `iter`, `rename`, `delete` |
+| `captures`, `crawls` | `create`, `get`, `list`, `iter`, `pages`, `cancel` |
+| `pins` | `create`, `get`, `list`, `iter`, `captures`, `update`, `delete` |
+| `schedules` | `create`, `get`, `list`, `iter`, `pages`, `captures`, `update`, `pause`, `resume`, `delete` |
+| `saved_queries` | `create`, `get`, `list`, `iter`, `update`, `rename`, `delete` |
 | `members` | `list`, `update_role`, `remove` |
 | `invitations` | `list`, `create`, `cancel` |
 | `api_keys` | `create`, `list`, `iter`, `revoke` |
@@ -112,30 +117,61 @@ The same key selects your organization and inherits your live membership access.
 | `query_history` | `list`, `iter`, `get`, `summary` |
 | `audit` | `list`, `iter` |
 
+Choose the resource by what you know and how long you need it:
+
+| Resource | Use it when |
+| --- | --- |
+| `captures` | You know the URLs (1–100) and need them in SQL now |
+| `crawls` | You know a starting point, not the URLs |
+| `pins` | You need exact captures for longer than seven days |
+| `schedules` | You need the same pages again later |
+
 ```python
 from periplus_sdk import Client
 
 with Client() as client:
-    preview = client.retention.preview(
+    capture = client.captures.create(urls=["https://example.com/pricing"])
+    capture = client.captures.get(capture, wait_seconds=30)
+    if capture.finished and capture.queryable:
+        for page in client.captures.pages(capture).items:
+            print(page.url, page.status, page.capture_id)
+
+    crawl = client.crawls.create(seeds=["https://example.com/docs/"], page_limit=200,
+                                 allowed_paths=["/docs/*"])
+
+    pin = client.pins.create(
         name="Research sources", days=90,
         sql="SELECT capture_id FROM captures WHERE domain(url) = ?",
         parameters=["example.com"],
     )
-    print(preview.id, preview.capture_count, preview.sample)
-    # Review the selection before calling:
-    # active = client.retention.activate(preview)
+    schedule = client.schedules.create(name="Pricing", every_days=7,
+                                       urls=["https://example.com/pricing"])
+    print(pin.captures, schedule.projected_pages_per_month)
 ```
 
-SQL previews persist inactive, frozen selections; activation never reruns SQL.
-Explicit IDs/URLs passed to `create` activate immediately. Monitoring URLs must
-already be known in the corpus. Use `members` and its `next_cursor` for complete
-membership: policy detail contains a sample. Updates/deletion accept a fetched
-`Policy` or an ID with `expected_version`; conflicts are never retried.
+Every capture is kept for seven days after collection unless a pin keeps it. A
+capture always fetches again and never returns an existing capture, so check
+coverage with SQL first. `request_id` (a capture or crawl `id`) is what you
+ordered; each page's `capture_id` is what the crawler produced and is the SQL key.
+`get(..., wait_seconds=N)` returns as soon as the request is finished and queryable,
+or after at most 30 seconds; the SDK never polls on its own.
+
+Pins and schedules accept explicit IDs/URLs or one read-only SQL query with
+parameters, and are active immediately. SQL runs once at creation and its exact
+result is locked in; running the same query beforehand is only an estimate.
+Schedule URLs need not be in the corpus. `pin_days` on a capture, crawl or schedule
+pins each successful capture it produces and requires `organization:pins:write`.
+`pins.update` changes `days` (moving every capture's expiry by the difference) or
+the name; `schedules.update` changes `every_days` or the name. Both accept a fetched
+object or an ID with `expected_version`; conflicts are never retried. Deletion needs
+no version: deleting a pin removes future protection, not captures.
 
 Paginated lists return `Page[T]` (`items`, `next_cursor`). Pass cursors unchanged
 or use `iter()`; membership/invitation lists are bounded snapshots instead.
-Offset-based lists can shift during concurrent changes. Query history and arrivals
-use keyset cursors. UTC usage ranges have an exclusive end date, at most 93 days.
+Offset-based lists can shift during concurrent changes. Query history, request
+page feeds and scheduled capture feeds use opaque keyset cursors. UTC usage ranges have an exclusive end date, at most 93 days. Usage reports pages
+captured (broken down by capture, crawl or schedule), challenge-resolution pages and
+pinned capture-days.
 Query history is best-effort and expires after 30 days; it is not a billing ledger.
 
 `ApiError` includes HTTP status, code, optional request ID, validation fields and

{periplus_python_sdk-0.11.0 → periplus_python_sdk-0.13.0}/src/periplus_python_sdk.egg-info/SOURCES.txt

@@ -19,7 +19,6 @@ src/periplus_sdk/errors.py
 src/periplus_sdk/py.typed
 src/periplus_sdk/resources.py
 src/periplus_sdk/resources_types.py
-src/periplus_sdk/selection.py
 src/periplus_sdk/sql_api.py
 src/periplus_sdk/sqlalchemy.py
 src/periplus_sdk/stream.py

{periplus_python_sdk-0.11.0 → periplus_python_sdk-0.13.0}/src/periplus_sdk/__init__.py

@@ -3,9 +3,11 @@ from .dbapi import connect
 from .client import AsyncClient, Client
 from .errors import ApiError, ConfigurationError, PeriplusError, ResponseError, TransportError
 from .types import Diagnostic, PreparedQuery, QueryHelper, QueryHelpers, QueryResult, SourceSnapshot
-from .resources_types import Page, Policy, Discovery, Member, Invitation, ApiKey, CreatedApiKey, Identity, Usage
+from .resources_types import (FollowRule, QueryCondition, Page, Request, RequestPage, Pin, PinCapture, Schedule, SchedulePage, Member,
+                              Invitation, ApiKey, CreatedApiKey, Identity, Usage)
 
 __all__ = ["connect", "AsyncClient", "Client", "ApiError", "ConfigurationError", "PeriplusError",
            "ResponseError", "TransportError", "Diagnostic", "PreparedQuery", "QueryHelper",
-           "QueryHelpers", "QueryResult", "Page", "Policy", "Discovery", "Member", "Invitation",
+           "QueryHelpers", "QueryResult", "FollowRule", "QueryCondition", "Page", "Request", "RequestPage", "Pin", "PinCapture",
+           "Schedule", "SchedulePage", "Member", "Invitation",
            "ApiKey", "CreatedApiKey", "Identity", "Usage", "SourceSnapshot"]