mppi-provider 0.1.0__tar.gz

mppi_provider-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_provider-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_provider-0.1.0/PKG-INFO

@@ -0,0 +1,149 @@
+Metadata-Version: 2.5
+Name: mppi-provider
+Version: 0.1.0
+Summary: MPPI provider 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 provider SDK for Python
+
+Version `0.1.0` supplies validated configuration, discovery, exact payment
+arithmetic, canonical chain evidence and native Complete/Control services.
+The Python runtime supports the paid request loop described below. Production
+release remains pending. Shared registry
+helpers and the Circle developer-controlled wallet adapter support provider
+setup and submission, verified through live Arc testnet registration, recipient
+binding, catalog publication, capture and close. The shared native
+[provider CLI](../../../docs/rust-cli.md) ships in the Rust package and supports
+Python integrations.
+
+Start with the [Python installation and paid-exchange walkthrough](../../../docs/python-quickstart.md).
+See [onboarding and wallets](../../../docs/python-onboarding.md) for the operator
+wallet, recipient proof, publication sequence and completed-rerun checks.
+
+```python
+from mppi_provider import CatalogRow, Rates, publish_catalog
+
+catalog = publish_catalog([CatalogRow("example/model", Rates(input=1_000_000, output=3_000_000))])
+```
+
+The provider supplies counts, requirements and definitive outcomes. MPPI computes
+and validates their payment meaning. Catalog publication here produces bytes;
+it does not make a registry transaction. Pure calculation helpers return immutable
+results. The runtime retains live payment state and signals the provider's execution
+hook when further work is no longer authorized.
+
+See [SDK interface definitions](../../../docs/sdk-interfaces.md) and the
+[protocol profile](../../../docs/protocol.md).
+
+The [runtime reference](../../../docs/python-runtime.md) includes configuration,
+HTTP host integration and evidence requirements.
+
+## Embedded provider runtime
+
+Construct `mppi_provider.runtime.Mppi(config, chain=..., contract=..., wallet=...,
+coverage=..., execution=...)` on the serving event-loop thread. Supply:
+
+- `ProviderConfig`: validated applied declarations and provider-selected timings.
+- `ChainFollower`: the shared follower of the selected verified deployment.
+  Its freshness and collection-margin timings must equal the validated config.
+- `ContractCalls`: the same MPPI domain and verified USDC funding domain.
+- `TransactionWallet`: the configured provider operator's execution capability.
+- `coverage`: an async callable `(PreparedRequest, RunContext) -> TokenCounts`.
+  Return the prepared prefill bound and at least the configured actual output
+  buffer; preparation performs no paid inference.
+- `execution`: an async iterator callable `(PreparedRequest, RunContext,
+  ProviderRuns, asyncio.Event) -> AsyncIterator[bytes]`. It yields original JSON
+  objects after the provider removes any upstream framing.
+
+Unauthenticated Control setup expires after 60 seconds. The optional constructor
+keyword `control_auth_timeout` sets a positive timeout in seconds, up to 3,600.
+Only successful signed session attachment removes this deadline; challenges and
+opening notices do not extend it. Authenticated Control streams may remain open.
+This server policy is independent of `payment.authorization_wait_ms` and applies
+even when a client omits its own RPC deadline.
+
+The execution integration uses `report_usage(context, cumulative_counts)` and
+`report_terminal(context, final_counts, RunStatus)` to supply facts. MPPI measures
+no tokens. A definitive final must follow actual provider-reported termination;
+iterator EOF, a disconnect and a cancellation signal do not substitute for it.
+For an upstream application error, report definitive FAILED usage when known and
+raise `UpstreamFailure(original_json_bytes, http_status=...)`.
+
+`require_coverage(context, remaining_tokens)` requests a complete desired remaining
+bound at the admitted run prices. It grants only when the combined session target
+fits the accepted voucher and confirmed deposit. An already larger reservation
+is retained. Only definitive final accounting releases unused coverage. During
+ordinary decode, report usage early enough for asynchronous voucher renewal,
+then request the next rolling output bound before consuming unreserved work.
+A rejected grant sets the event passed to execution. The provider terminates
+its actual job and reports final usage; a later voucher does not restart it.
+
+Pass `mppi_protocol.wire.GRPC_OPTIONS` when creating the host's `grpc.aio.server`.
+Call `register_grpc(server)` before starting that server, then await `start()` and
+check its `Readiness`. Publish `discovery(path)` responses through the host's
+HTTP stack on the same HTTPS origin. The host supplies TLS credentials, ingress
+and listener lifecycle. MPPI starts no listener and does not serve keyed `/v1`.
+An unavailable chain at startup returns not-ready while the follower retries.
+Discovery and the first-use baseline become available only after fresh identity
+evidence arrives; an outage does not establish empty session history.
+
+`sessions.settle(id)` captures cumulative actual usage and keeps the session open.
+`sessions.close(id)` preserves close intent, requests termination and verifies
+canonical closure before returning a confirmed result. Pending/unknown calls
+retain their original transaction identity; repeated calls reconcile it. The
+close intent has its own stable reference; confirming an earlier capture does
+not report that close as confirmed. The
+background schedule groups collection requests. `settleBatch(session_ids)`
+simulates the exact ordered call before wallet submission and reconciles each
+target independently. Unknown submission outcomes preserve their original
+identity; they never trigger a replacement capture.
+
+Call `shutdown(deadline)` with an absolute serving-loop monotonic deadline.
+It stops new grants, signals execution, processes available final reports and
+returns unresolved runs/operations. The caller stops its own gRPC server.
+Shutdown does not initiate escrow closure or invent final reports.
+
+## Payment-state ownership and recovery
+
+One `Mppi` instance holds the authoritative live payment state for its sessions.
+Its Complete and Control handlers may receive different backend connections;
+socket equality grants no authority. The provider must ensure every operation
+uses that same authoritative state. Independent processes do not share payment
+state through this SDK. Routing, worker coordination, durability and recovery
+remain provider responsibilities.
+
+A newly observed opening after startup can create first-use state under that
+ownership requirement. A historical opening after restart cannot establish zero
+usage. `await sessions.checkpoint(session_id)` exports detached
+`RecoveryEvidence` for provider-owned retention. `await sessions.recover(evidence)`
+revalidates the supplied run proofs, exact prices, accounting, reservations and
+canonical chain evidence before installing state. Missing private history returns
+`STATE_UNAVAILABLE`; invalid recovery leaves existing state unchanged. Recovery
+requires fresh Control authentication and never resumes old execution.
+Unresolved old execution prevents a ready replacement attachment.
+
+A known opening before its first authenticated attachment can be checkpointed
+at generation zero. This private evidence has no accepted voucher, usage, runs
+or reservations and remains unready. The provider must retain complete history;
+zero on-chain settlement alone cannot establish that it was unused. Recovery
+preserves any refund-only close intent and assigns no owner. Fresh authentication
+creates generation one; generation-zero snapshots are never valid on Control.
+
+Wallet adapters must durably bind an operation reference to its exact intended
+call and retain available wallet/transaction identifiers. These requirements do
+not add a provider database. The agent SDK supplies its own local checkpoint.
+The shared Circle developer-controlled wallet adapter and registry helpers
+provide the implemented onboarding and submission integration described above.
+
+## 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_provider-0.1.0/README.md

@@ -0,0 +1,139 @@
+# MPPI provider SDK for Python
+
+Version `0.1.0` supplies validated configuration, discovery, exact payment
+arithmetic, canonical chain evidence and native Complete/Control services.
+The Python runtime supports the paid request loop described below. Production
+release remains pending. Shared registry
+helpers and the Circle developer-controlled wallet adapter support provider
+setup and submission, verified through live Arc testnet registration, recipient
+binding, catalog publication, capture and close. The shared native
+[provider CLI](../../../docs/rust-cli.md) ships in the Rust package and supports
+Python integrations.
+
+Start with the [Python installation and paid-exchange walkthrough](../../../docs/python-quickstart.md).
+See [onboarding and wallets](../../../docs/python-onboarding.md) for the operator
+wallet, recipient proof, publication sequence and completed-rerun checks.
+
+```python
+from mppi_provider import CatalogRow, Rates, publish_catalog
+
+catalog = publish_catalog([CatalogRow("example/model", Rates(input=1_000_000, output=3_000_000))])
+```
+
+The provider supplies counts, requirements and definitive outcomes. MPPI computes
+and validates their payment meaning. Catalog publication here produces bytes;
+it does not make a registry transaction. Pure calculation helpers return immutable
+results. The runtime retains live payment state and signals the provider's execution
+hook when further work is no longer authorized.
+
+See [SDK interface definitions](../../../docs/sdk-interfaces.md) and the
+[protocol profile](../../../docs/protocol.md).
+
+The [runtime reference](../../../docs/python-runtime.md) includes configuration,
+HTTP host integration and evidence requirements.
+
+## Embedded provider runtime
+
+Construct `mppi_provider.runtime.Mppi(config, chain=..., contract=..., wallet=...,
+coverage=..., execution=...)` on the serving event-loop thread. Supply:
+
+- `ProviderConfig`: validated applied declarations and provider-selected timings.
+- `ChainFollower`: the shared follower of the selected verified deployment.
+  Its freshness and collection-margin timings must equal the validated config.
+- `ContractCalls`: the same MPPI domain and verified USDC funding domain.
+- `TransactionWallet`: the configured provider operator's execution capability.
+- `coverage`: an async callable `(PreparedRequest, RunContext) -> TokenCounts`.
+  Return the prepared prefill bound and at least the configured actual output
+  buffer; preparation performs no paid inference.
+- `execution`: an async iterator callable `(PreparedRequest, RunContext,
+  ProviderRuns, asyncio.Event) -> AsyncIterator[bytes]`. It yields original JSON
+  objects after the provider removes any upstream framing.
+
+Unauthenticated Control setup expires after 60 seconds. The optional constructor
+keyword `control_auth_timeout` sets a positive timeout in seconds, up to 3,600.
+Only successful signed session attachment removes this deadline; challenges and
+opening notices do not extend it. Authenticated Control streams may remain open.
+This server policy is independent of `payment.authorization_wait_ms` and applies
+even when a client omits its own RPC deadline.
+
+The execution integration uses `report_usage(context, cumulative_counts)` and
+`report_terminal(context, final_counts, RunStatus)` to supply facts. MPPI measures
+no tokens. A definitive final must follow actual provider-reported termination;
+iterator EOF, a disconnect and a cancellation signal do not substitute for it.
+For an upstream application error, report definitive FAILED usage when known and
+raise `UpstreamFailure(original_json_bytes, http_status=...)`.
+
+`require_coverage(context, remaining_tokens)` requests a complete desired remaining
+bound at the admitted run prices. It grants only when the combined session target
+fits the accepted voucher and confirmed deposit. An already larger reservation
+is retained. Only definitive final accounting releases unused coverage. During
+ordinary decode, report usage early enough for asynchronous voucher renewal,
+then request the next rolling output bound before consuming unreserved work.
+A rejected grant sets the event passed to execution. The provider terminates
+its actual job and reports final usage; a later voucher does not restart it.
+
+Pass `mppi_protocol.wire.GRPC_OPTIONS` when creating the host's `grpc.aio.server`.
+Call `register_grpc(server)` before starting that server, then await `start()` and
+check its `Readiness`. Publish `discovery(path)` responses through the host's
+HTTP stack on the same HTTPS origin. The host supplies TLS credentials, ingress
+and listener lifecycle. MPPI starts no listener and does not serve keyed `/v1`.
+An unavailable chain at startup returns not-ready while the follower retries.
+Discovery and the first-use baseline become available only after fresh identity
+evidence arrives; an outage does not establish empty session history.
+
+`sessions.settle(id)` captures cumulative actual usage and keeps the session open.
+`sessions.close(id)` preserves close intent, requests termination and verifies
+canonical closure before returning a confirmed result. Pending/unknown calls
+retain their original transaction identity; repeated calls reconcile it. The
+close intent has its own stable reference; confirming an earlier capture does
+not report that close as confirmed. The
+background schedule groups collection requests. `settleBatch(session_ids)`
+simulates the exact ordered call before wallet submission and reconciles each
+target independently. Unknown submission outcomes preserve their original
+identity; they never trigger a replacement capture.
+
+Call `shutdown(deadline)` with an absolute serving-loop monotonic deadline.
+It stops new grants, signals execution, processes available final reports and
+returns unresolved runs/operations. The caller stops its own gRPC server.
+Shutdown does not initiate escrow closure or invent final reports.
+
+## Payment-state ownership and recovery
+
+One `Mppi` instance holds the authoritative live payment state for its sessions.
+Its Complete and Control handlers may receive different backend connections;
+socket equality grants no authority. The provider must ensure every operation
+uses that same authoritative state. Independent processes do not share payment
+state through this SDK. Routing, worker coordination, durability and recovery
+remain provider responsibilities.
+
+A newly observed opening after startup can create first-use state under that
+ownership requirement. A historical opening after restart cannot establish zero
+usage. `await sessions.checkpoint(session_id)` exports detached
+`RecoveryEvidence` for provider-owned retention. `await sessions.recover(evidence)`
+revalidates the supplied run proofs, exact prices, accounting, reservations and
+canonical chain evidence before installing state. Missing private history returns
+`STATE_UNAVAILABLE`; invalid recovery leaves existing state unchanged. Recovery
+requires fresh Control authentication and never resumes old execution.
+Unresolved old execution prevents a ready replacement attachment.
+
+A known opening before its first authenticated attachment can be checkpointed
+at generation zero. This private evidence has no accepted voucher, usage, runs
+or reservations and remains unready. The provider must retain complete history;
+zero on-chain settlement alone cannot establish that it was unused. Recovery
+preserves any refund-only close intent and assigns no owner. Fresh authentication
+creates generation one; generation-zero snapshots are never valid on Control.
+
+Wallet adapters must durably bind an operation reference to its exact intended
+call and retain available wallet/transaction identifiers. These requirements do
+not add a provider database. The agent SDK supplies its own local checkpoint.
+The shared Circle developer-controlled wallet adapter and registry helpers
+provide the implemented onboarding and submission integration described above.
+
+## 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_provider-0.1.0/pyproject.toml

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

mppi_provider-0.1.0/src/mppi_provider/__init__.py

@@ -0,0 +1,81 @@
+"""MPPI provider payment runtime and public integration contracts."""
+
+from mppi_protocol import (
+    CatalogRow,
+    Rates,
+    RunAccounting,
+    RunStatus,
+    TokenCounts,
+    cumulative_usage,
+    publish_catalog,
+    report_transition,
+    required_coverage,
+)
+
+from .config import (
+    AdditionalService,
+    ChainConfig,
+    ConfigError,
+    ListenerConfig,
+    ModelConfig,
+    PaymentConfig,
+    ProviderConfig,
+    ProviderDetails,
+    ProviderIdentityConfig,
+    SettlementConfig,
+    UpstreamConfig,
+)
+from .discovery import DiscoveryDocuments
+from .hooks import HookError, Hooks, ObserverStats
+from .interfaces import (
+    CoverageProvider,
+    ExecutionProvider,
+    FinalAccountingResult,
+    PreparedRequest,
+    ProviderLifecycle,
+    ProviderRuns,
+    ProviderSessions,
+    RecoveryEvidence,
+    RecoveryOperation,
+    RecoveryRun,
+)
+from .runtime import Mppi, UpstreamFailure
+
+__all__ = [
+    "HookError",
+    "Hooks",
+    "ObserverStats",
+    "AdditionalService",
+    "ChainConfig",
+    "ConfigError",
+    "DiscoveryDocuments",
+    "ListenerConfig",
+    "ModelConfig",
+    "PaymentConfig",
+    "ProviderConfig",
+    "ProviderDetails",
+    "ProviderIdentityConfig",
+    "SettlementConfig",
+    "UpstreamConfig",
+    "CatalogRow",
+    "CoverageProvider",
+    "ExecutionProvider",
+    "FinalAccountingResult",
+    "Mppi",
+    "PreparedRequest",
+    "ProviderLifecycle",
+    "ProviderRuns",
+    "ProviderSessions",
+    "RecoveryEvidence",
+    "RecoveryOperation",
+    "RecoveryRun",
+    "Rates",
+    "RunAccounting",
+    "RunStatus",
+    "TokenCounts",
+    "UpstreamFailure",
+    "cumulative_usage",
+    "publish_catalog",
+    "report_transition",
+    "required_coverage",
+]