mppi-agent 0.1.0__tar.gz

mppi_agent-0.1.0/.gitignore

@@ -0,0 +1,17 @@
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+*.egg-info/
+dist/
+target/
+out/
+cache/
+broadcast/
+.env
+.env.*
+!.env.example
+*.pem
+.DS_Store

mppi_agent-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

mppi_agent-0.1.0/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.5
+Name: mppi-agent
+Version: 0.1.0
+Summary: MPPI agent SDK: typed payment interfaces and exact primitives
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: mppi-protocol==0.1.0
+Description-Content-Type: text/markdown
+
+# MPPI agent SDK for Python
+
+Version `0.1.0` includes a synchronous `Client` with an owning background
+asyncio thread for native TLS gRPC Complete and Control. It verifies discovery,
+positive funding, fixed-signer attachment, signed run prices, cumulative vouchers,
+provider usage reports and canonical settlement/close evidence. The release is
+under development. The package includes resumable ERC-8004 onboarding and a
+Circle Agent Wallet adapter tested through live Arc testnet onboarding, funding,
+payment, authenticated reconnect and cooperative close.
+
+Start with the [Python installation and paid-exchange walkthrough](../../../docs/python-quickstart.md).
+See [onboarding and wallet setup](../../../docs/python-onboarding.md) for
+`mppi-agent onboard`, deployment profiles, wallet integration and rerun behavior.
+
+```python
+from mppi_agent import Rates, funding_amount
+
+assert funding_amount(1_000_000, Rates(input=1_000_000, output=3_000_000)) == 3_000_000
+```
+
+The result is six-decimal USDC base units. This calculation transfers no funds.
+The caller selects funding; actual usage retains its individual accepted rates.
+
+Construct `Client(provider, wallet=..., signer=..., chain=..., contract=...,
+checkpoint_path=..., signer_reference=..., initial_session_tokens=...)` with
+the shared `ChainFollower` and `ContractCalls` configured for the verified
+deployment. The funding wallet and fixed ECDSA signer are distinct capabilities.
+The caller supplies wallet integration; no login or key creation is implicit.
+
+- `sessions.open(provider, model=..., initial_session_tokens=...)` explicitly
+  prewarms a positively funded session. `chat.completions.create(...)` can open
+  lazily using the caller's configured positive funding choice.
+- `chat.completions.create(model=..., messages=..., stream=True)` returns an
+  iterator of original JSON bytes with `terminal` and `receipt` records.
+  `create_raw(payload, model=..., stream=...)` preserves original request bytes.
+- `accept_catalog(rate_card_hash)` explicitly accepts the exact fresh published
+  catalog for subsequent runs. Active and historical runs keep their prices.
+- `sessions.topUp(session_id, amount)` takes positive USDC base units. Funding
+  is explicit; low-credit guidance never triggers a wallet transfer.
+- `Client(..., on_low_credit=callback)` delivers validated `LowCredit` messages
+  to caller code in order, outside the Control event loop. Each message is a
+  detached copy. The caller may explicitly call `sessions.topUp`; the SDK adds
+  no funding policy. Keep callbacks bounded: an exception or full callback queue
+  fails the attachment. Queued callbacks are discarded when Control is lost;
+  an already running callback cannot be interrupted. Confirmed top-up rechecks
+  the retained voucher target against fresh chain funding.
+- `sessions.recover(session_id)` restores retained state and authenticates a new
+  Control generation. It neither funds a session nor replays inference. Current
+  observed prices still require explicit acceptance for later runs.
+- `sessions.close(session_id)` requests signed cooperative close. The explicit
+  `requestClose`, `withdraw`, `releaseIdle` and `reconcile` methods retain their
+  respective chain eligibility and evidence checks.
+- `Client.close()` and context-manager exit shut down local streams and return
+  unresolved work. They do not implicitly close a funded session.
+
+The checkpoint path is required and exclusively locked on macOS/Linux. Reuse
+it for the same payment scope across restarts. It contains descriptors, signed
+payment intent and operation references, with mode 0600; it contains no prompts
+or private signing key. Keep the recoverable signer credential in the supplied
+secret service. The client owns the supplied follower's lifecycle.
+
+An explicit open can continue the same retained, never-submitted opening intent
+while its authorization remains valid. A pending or unknown submission is
+reconciled using its original reference; it cannot create replacement funding.
+
+Retained session inspection and wallet-only exits restore from the checkpoint
+and verified chain state without requiring the provider's HTTP endpoint. A
+`CloseAccountingError` reports capture above validated usage while retaining
+the confirmed transaction in its `operation`; it does not imply a retry is safe.
+
+Queue bounds and wait timeouts are explicit constructor settings. Slow output
+consumption cannot grow its queue without bound; failed or cancelled inference
+is never automatically replayed. Transport errors can leave final accounting
+unresolved. Fresh cached chain evidence is required for new authorization.
+
+See [SDK interface definitions](../../../docs/sdk-interfaces.md) and the
+[protocol profile](../../../docs/protocol.md). The shared protocol dependency is
+an implementation support library, not a third role SDK.
+
+See [runtime building blocks](../../../docs/python-runtime.md) for the new APIs
+and their verification boundaries.
+
+## Application unit tests
+
+`mppi_agent.testing.MockProvider` runs the real generated Chat and Control gRPC
+services in-process on an ephemeral loopback port. Supply asynchronous handlers
+for the exact protobuf messages and errors your application should encounter:
+
+```python
+import asyncio
+from mppi.v1 import mppi_pb2 as pb
+from mppi_agent.testing import MockProvider
+
+
+async def complete(request, context):
+    yield pb.ChatChunk(payload=b'{"answer":"Inference successful"}')
+
+
+async def control(requests, context):
+    async for message in requests:
+        # A test script can inspect the request and yield its selected reply.
+        yield pb.ControlMessage(reconnect_challenge=pb.ReconnectChallenge(nonce=b"n" * 32))
+
+
+async def test_application():
+    async with MockProvider(completions=complete, control=control) as provider:
+        call = provider.chat.Completions(
+            pb.CompleteRequest(model="test/model", payload=b"{}"), timeout=2
+        )
+        assert (await call.read()).payload == b'{"answer":"Inference successful"}'
+
+
+asyncio.run(test_application())
+```
+
+The `chat` and `control` properties expose asynchronous generated stubs. Their
+RPCs accept normal gRPC deadlines; context exit closes the channel and cancels
+unfinished calls. Each instance is used once. Both handlers run on the test's
+event loop, so keep them asynchronous.
+
+Scripts control every reply, including omitted final reports and rejected
+requests. The helper implements no discovery, TLS, wallet, chain state or
+payment validation. It does not change `Client` verification or turn scripted
+messages into proof of settlement. Use deployed testnet integration for those
+boundaries. No provider package is needed to import this helper.
+
+## Lifecycle observers
+
+Pass `hooks=Hooks(...)` to the runtime/client for typed lifecycle observations.
+See the [hook payloads, ordering and bounds](../../../docs/lifecycle-hooks.md).
+
+## License
+
+Copyright 2026 MPPI contributors. Licensed under the [Apache License, Version 2.0](LICENSE).

mppi_agent-0.1.0/README.md

@@ -0,0 +1,134 @@
+# MPPI agent SDK for Python
+
+Version `0.1.0` includes a synchronous `Client` with an owning background
+asyncio thread for native TLS gRPC Complete and Control. It verifies discovery,
+positive funding, fixed-signer attachment, signed run prices, cumulative vouchers,
+provider usage reports and canonical settlement/close evidence. The release is
+under development. The package includes resumable ERC-8004 onboarding and a
+Circle Agent Wallet adapter tested through live Arc testnet onboarding, funding,
+payment, authenticated reconnect and cooperative close.
+
+Start with the [Python installation and paid-exchange walkthrough](../../../docs/python-quickstart.md).
+See [onboarding and wallet setup](../../../docs/python-onboarding.md) for
+`mppi-agent onboard`, deployment profiles, wallet integration and rerun behavior.
+
+```python
+from mppi_agent import Rates, funding_amount
+
+assert funding_amount(1_000_000, Rates(input=1_000_000, output=3_000_000)) == 3_000_000
+```
+
+The result is six-decimal USDC base units. This calculation transfers no funds.
+The caller selects funding; actual usage retains its individual accepted rates.
+
+Construct `Client(provider, wallet=..., signer=..., chain=..., contract=...,
+checkpoint_path=..., signer_reference=..., initial_session_tokens=...)` with
+the shared `ChainFollower` and `ContractCalls` configured for the verified
+deployment. The funding wallet and fixed ECDSA signer are distinct capabilities.
+The caller supplies wallet integration; no login or key creation is implicit.
+
+- `sessions.open(provider, model=..., initial_session_tokens=...)` explicitly
+  prewarms a positively funded session. `chat.completions.create(...)` can open
+  lazily using the caller's configured positive funding choice.
+- `chat.completions.create(model=..., messages=..., stream=True)` returns an
+  iterator of original JSON bytes with `terminal` and `receipt` records.
+  `create_raw(payload, model=..., stream=...)` preserves original request bytes.
+- `accept_catalog(rate_card_hash)` explicitly accepts the exact fresh published
+  catalog for subsequent runs. Active and historical runs keep their prices.
+- `sessions.topUp(session_id, amount)` takes positive USDC base units. Funding
+  is explicit; low-credit guidance never triggers a wallet transfer.
+- `Client(..., on_low_credit=callback)` delivers validated `LowCredit` messages
+  to caller code in order, outside the Control event loop. Each message is a
+  detached copy. The caller may explicitly call `sessions.topUp`; the SDK adds
+  no funding policy. Keep callbacks bounded: an exception or full callback queue
+  fails the attachment. Queued callbacks are discarded when Control is lost;
+  an already running callback cannot be interrupted. Confirmed top-up rechecks
+  the retained voucher target against fresh chain funding.
+- `sessions.recover(session_id)` restores retained state and authenticates a new
+  Control generation. It neither funds a session nor replays inference. Current
+  observed prices still require explicit acceptance for later runs.
+- `sessions.close(session_id)` requests signed cooperative close. The explicit
+  `requestClose`, `withdraw`, `releaseIdle` and `reconcile` methods retain their
+  respective chain eligibility and evidence checks.
+- `Client.close()` and context-manager exit shut down local streams and return
+  unresolved work. They do not implicitly close a funded session.
+
+The checkpoint path is required and exclusively locked on macOS/Linux. Reuse
+it for the same payment scope across restarts. It contains descriptors, signed
+payment intent and operation references, with mode 0600; it contains no prompts
+or private signing key. Keep the recoverable signer credential in the supplied
+secret service. The client owns the supplied follower's lifecycle.
+
+An explicit open can continue the same retained, never-submitted opening intent
+while its authorization remains valid. A pending or unknown submission is
+reconciled using its original reference; it cannot create replacement funding.
+
+Retained session inspection and wallet-only exits restore from the checkpoint
+and verified chain state without requiring the provider's HTTP endpoint. A
+`CloseAccountingError` reports capture above validated usage while retaining
+the confirmed transaction in its `operation`; it does not imply a retry is safe.
+
+Queue bounds and wait timeouts are explicit constructor settings. Slow output
+consumption cannot grow its queue without bound; failed or cancelled inference
+is never automatically replayed. Transport errors can leave final accounting
+unresolved. Fresh cached chain evidence is required for new authorization.
+
+See [SDK interface definitions](../../../docs/sdk-interfaces.md) and the
+[protocol profile](../../../docs/protocol.md). The shared protocol dependency is
+an implementation support library, not a third role SDK.
+
+See [runtime building blocks](../../../docs/python-runtime.md) for the new APIs
+and their verification boundaries.
+
+## Application unit tests
+
+`mppi_agent.testing.MockProvider` runs the real generated Chat and Control gRPC
+services in-process on an ephemeral loopback port. Supply asynchronous handlers
+for the exact protobuf messages and errors your application should encounter:
+
+```python
+import asyncio
+from mppi.v1 import mppi_pb2 as pb
+from mppi_agent.testing import MockProvider
+
+
+async def complete(request, context):
+    yield pb.ChatChunk(payload=b'{"answer":"Inference successful"}')
+
+
+async def control(requests, context):
+    async for message in requests:
+        # A test script can inspect the request and yield its selected reply.
+        yield pb.ControlMessage(reconnect_challenge=pb.ReconnectChallenge(nonce=b"n" * 32))
+
+
+async def test_application():
+    async with MockProvider(completions=complete, control=control) as provider:
+        call = provider.chat.Completions(
+            pb.CompleteRequest(model="test/model", payload=b"{}"), timeout=2
+        )
+        assert (await call.read()).payload == b'{"answer":"Inference successful"}'
+
+
+asyncio.run(test_application())
+```
+
+The `chat` and `control` properties expose asynchronous generated stubs. Their
+RPCs accept normal gRPC deadlines; context exit closes the channel and cancels
+unfinished calls. Each instance is used once. Both handlers run on the test's
+event loop, so keep them asynchronous.
+
+Scripts control every reply, including omitted final reports and rejected
+requests. The helper implements no discovery, TLS, wallet, chain state or
+payment validation. It does not change `Client` verification or turn scripted
+messages into proof of settlement. Use deployed testnet integration for those
+boundaries. No provider package is needed to import this helper.
+
+## Lifecycle observers
+
+Pass `hooks=Hooks(...)` to the runtime/client for typed lifecycle observations.
+See the [hook payloads, ordering and bounds](../../../docs/lifecycle-hooks.md).
+
+## License
+
+Copyright 2026 MPPI contributors. Licensed under the [Apache License, Version 2.0](LICENSE).

mppi_agent-0.1.0/pyproject.toml

@@ -0,0 +1,19 @@
+[build-system]
+requires = ["hatchling==1.32.4"]
+build-backend = "hatchling.build"
+
+[project]
+name = "mppi-agent"
+version = "0.1.0"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+description = "MPPI agent SDK: typed payment interfaces and exact primitives"
+readme = "README.md"
+requires-python = ">=3.12"
+dependencies = ["mppi-protocol==0.1.0"]
+
+[project.scripts]
+mppi-agent = "mppi_agent.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/mppi_agent"]

mppi_agent-0.1.0/src/mppi_agent/__init__.py

@@ -0,0 +1,53 @@
+"""MPPI agent payment and inference client."""
+
+from mppi_protocol import (
+    Catalog,
+    Rates,
+    TokenCounts,
+    funding_amount,
+    parse_catalog,
+    required_coverage,
+)
+from mppi_protocol.signing import LocalSessionSigner
+
+from .client import (
+    Client,
+    ClientError,
+    CloseAccountingError,
+    CompletionStream,
+    InferenceError,
+    PaymentError,
+)
+from .discovery import ProviderDiscovery, discover, verify_challenge
+from .hooks import HookError, Hooks, ObserverStats
+from .interfaces import AgentSessions, FundingWallet, OpenResult, SessionSigner
+from .onboarding import OnboardingError, OnboardingResult, onboard
+
+__all__ = [
+    "HookError",
+    "Hooks",
+    "ObserverStats",
+    "AgentSessions",
+    "Catalog",
+    "Client",
+    "ClientError",
+    "CloseAccountingError",
+    "CompletionStream",
+    "FundingWallet",
+    "LocalSessionSigner",
+    "InferenceError",
+    "OpenResult",
+    "OnboardingError",
+    "OnboardingResult",
+    "PaymentError",
+    "ProviderDiscovery",
+    "Rates",
+    "SessionSigner",
+    "TokenCounts",
+    "funding_amount",
+    "discover",
+    "parse_catalog",
+    "required_coverage",
+    "verify_challenge",
+    "onboard",
+]