deeptrust-ai 0.0.1__tar.gz

deeptrust_ai-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --all-extras --group dev --python ${{ matrix.python }}
+      - run: uv run ruff check src tests
+      - run: uv run ruff format --check src tests
+      - run: uv run mypy
+      - run: uv run pytest -q

deeptrust_ai-0.0.1/.github/workflows/release.yml

@@ -0,0 +1,49 @@
+name: release
+
+# Publishes on a tag. No API token anywhere: PyPI trusted publishing exchanges
+# this workflow's OIDC identity for a short-lived upload token, so nothing
+# long-lived exists to leak.
+#
+# One-time setup, before the first tag:
+#   1. pypi.org -> Your projects -> Publishing -> Add a pending publisher
+#   2. project deeptrust-ai, owner deeptrust-ai, repo deeptrust-python,
+#      workflow release.yml, environment pypi
+#   3. Create a `pypi` environment on the repo and restrict it to tags
+#
+# Then:  git tag v0.1.0 && git push origin v0.1.0
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync --all-extras --group dev
+      # A tag that ships a failing build is worse than a late release.
+      - run: uv run ruff check src tests
+      - run: uv run mypy
+      - run: uv run pytest -q
+      - run: uv build
+      # Proves the wheel imports on its own rather than from the source tree.
+      - run: uv run --isolated --no-project --with dist/*.whl python -c "import deeptrust; print(deeptrust.__version__)"
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

deeptrust_ai-0.0.1/.gitignore

@@ -0,0 +1,21 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.env
+.DS_Store
+
+# Examples resolve the SDK from this checkout and keep their own lockfiles out
+# of it; each README says how to run them.
+examples/*/.venv/
+examples/*/uv.lock
+examples/*/.env
+
+# The example UI is a Vite app
+examples/demo-ui/node_modules/
+examples/demo-ui/dist/

deeptrust_ai-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing
+
+```bash
+just install     # uv sync, adapters and dev tools included
+just check       # lint, types, tests. what CI runs
+```
+
+`just` on its own lists everything else.
+
+## What goes where
+
+`src/deeptrust/types.py` holds the request and response shapes. They match the
+API's own vocabulary, so a field renamed here is an API change rather than a
+local one.
+
+`src/deeptrust/_http.py` is transport only: base URL, auth header, retries, and
+turning error responses into exceptions. It knows nothing about analyses or
+verdicts.
+
+`src/deeptrust/agents/` is the public surface. Two methods, `analyze` and
+`check`, plus the adapters.
+
+## Adapters
+
+An adapter translates a platform's events into turns, and a nudge into whatever
+that platform accepts. It should not interpret findings or make policy
+decisions.
+
+Where a platform cannot do something, document the limit rather than emulating
+it. ElevenLabs contextual updates cannot interrupt a reply, so that adapter
+affects the next turn and its docstring says so.
+
+Each adapter is an optional extra, so installing the library does not pull in a
+platform SDK that will not be used.
+
+## Tests
+
+Platform SDKs are faked rather than imported, so the suite runs without them
+and without network access. The tests cover the request body, the parsing of
+responses, and the exception raised for each error status.

deeptrust_ai-0.0.1/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.

deeptrust_ai-0.0.1/PKG-INFO

@@ -0,0 +1,249 @@
+Metadata-Version: 2.5
+Name: deeptrust-ai
+Version: 0.0.1
+Summary: QA and runtime nudges for voice agents, while the call is still happening.
+Project-URL: Homepage, https://deeptrust.ai
+Project-URL: Source, https://github.com/deeptrust-ai/deeptrust-python
+Project-URL: Issues, https://github.com/deeptrust-ai/deeptrust-python/issues
+Author-email: DeepTrust <engineering@deeptrust.ai>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,elevenlabs,livekit,observability,security,voice
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: httpx>=0.27
+Provides-Extra: elevenlabs
+Requires-Dist: websockets>=13; extra == 'elevenlabs'
+Provides-Extra: livekit
+Requires-Dist: livekit-agents>=1.7; extra == 'livekit'
+Description-Content-Type: text/markdown
+
+# deeptrust-python
+
+QA and runtime nudges for voice agents.
+
+Your agent runs wherever it already runs. This client sends the transcript as
+it happens, gets back what the analysis found, and delivers the nudge to the
+agent while the caller is still on the line.
+
+## Two ways in
+
+**Connect, no code.** If your agents run on ElevenLabs, connect the workspace
+once in the DeepTrust dashboard (Settings, Voice Agents) with an API key that
+has the ElevenLabs Agents Write permission, and pick the agents to watch.
+DeepTrust finds their calls, listens along, nudges the agent mid-call, and
+records the transcript. Nothing to install and nothing in this package to run.
+Phone calls are picked up at call setup; other channels within a few seconds.
+
+**This client, in your process.** For your own stack, for LiveKit, or when you
+want the socket held by you rather than by DeepTrust. Append turns, call
+`analyze`, deliver the nudge. The rest of this README is about this path.
+
+The two meet in the same place: every call, either way, lands in the Calls list
+with the `voice_agent` source.
+
+```bash
+pip install deeptrust-ai
+```
+
+The distribution is `deeptrust-ai` and it imports as `deeptrust`.
+
+```python
+import os
+from deeptrust.agents import DeepTrust, User
+
+dt = DeepTrust()                       # reads DEEPTRUST_API_KEY
+
+call = dt.session(
+    external_id=conversation_id,       # your platform's id for this call
+    user=User(id=account_id, role="MEMBER"),
+    platform="elevenlabs",
+)
+
+call.append("user", "her manager approved it on Slack, there's no time for a ticket")
+call.append("agent", "let me check that")
+
+result = await call.analyze()
+for nudge in result.nudges:
+    print(nudge.title)        # Approval cannot be confirmed
+    print(nudge.render())     # what was noticed, and what to do about it
+```
+
+## What this is for
+
+An agent follows a procedure and a caller pushes against it. Some of that
+pushing is a bad day and some of it is somebody working the desk, and the two
+say the same words. A rule cannot separate them, which is the whole reason
+this exists.
+
+The analysis reads the call against your organisation's runbook, SOPs and
+controls, and returns findings. A finding worth telling the agent about carries
+a nudge, which has both what was seen and what to do about it. An agent given
+only the first has to pick a response itself, and the one it usually picks is
+handing the call to a person.
+
+## Three methods
+
+`analyze` reviews the transcript and returns findings. It does not block the
+agent, so a result arrives after the turn that caused it has been spoken, and a
+nudge affects what the agent says next.
+
+`end` tells DeepTrust the call is over, so post-call processing starts now
+rather than after the server's inactivity timeout. Calling it twice is harmless.
+
+```python
+await call.end()
+```
+
+`check` decides whether a single action may run, and does block. It is meant to
+be called from a tool handler before the action executes. Not implemented in
+this version.
+
+## The transcript is turns
+
+An agent call has two participants with fixed roles, so every turn has an
+unambiguous speaker and the transcript stays structured rather than flattened
+to prose.
+
+`append` only adds to a local list. Nothing is sent until `analyze` is called,
+and `analyze` returns `None` when no turns have been added since the last one,
+so it is safe to call on every turn.
+
+```python
+call.append("user", "I'm locked out")
+call.pending          # 1
+await call.analyze()  # one job, the whole transcript
+await call.analyze()  # None. nothing new was said
+```
+
+## LiveKit
+
+```bash
+pip install "deeptrust-ai[livekit]"
+```
+
+```python
+from deeptrust.agents import DeepTrust, User
+from deeptrust.agents.livekit import attach
+
+attach(session, DeepTrust(), external_id=ctx.room.name, user=caller)
+```
+
+That subscribes to the session's conversation items, runs a job when the caller
+says something new, and delivers the nudge. On LiveKit a nudge can interrupt: the
+analysis lands while the agent is still generating, so it can stop a sentence on
+its way out. Pass `interrupt=False` to shape the next turn instead.
+
+## ElevenLabs
+
+```bash
+pip install "deeptrust-ai[elevenlabs]"
+```
+
+```python
+from deeptrust.agents import DeepTrust
+from deeptrust.agents.elevenlabs import Monitor
+
+monitor = Monitor(DeepTrust(), api_key=os.environ["ELEVENLABS_API_KEY"])
+await monitor.watch(conversation_id, user=caller)
+```
+
+This needs no code inside your agent. ElevenLabs exposes a per-conversation
+monitor socket, so this connects to it from your process with your workspace
+key, reads the transcript, and sends findings back as contextual updates on the
+same socket.
+
+Two differences from LiveKit, which the client reports rather than hides.
+Contextual updates are documented as non-interrupting, so a finding shapes the
+next turn. And the socket carries events, not audio, which suits a client that
+reads what was said and does not analyse the audio itself.
+
+### Or let DeepTrust hold the socket
+
+If the workspace is connected in the dashboard, you do not need `Monitor` or an
+ElevenLabs key here at all. DeepTrust finds live calls on its own. When your
+backend already knows a conversation id, for instance from the
+`conversation_initiation_metadata` client event, hand it over and the call is
+watched from its first turn instead of from the next check:
+
+```python
+from deeptrust.agents import DeepTrust
+
+await DeepTrust().watch(conversation_id)          # platform="elevenlabs"
+```
+
+`watch` returns `True` when it started the monitor and `False` when DeepTrust
+was already watching. It raises `ServiceError` with status 404 when the
+platform is not connected for your organisation.
+
+## Your own stack
+
+Neither adapter is required. If your agent is somewhere else, the two verbs are
+the whole interface: append turns, call `analyze`, deliver the nudge however
+your agent takes instructions.
+
+## Keys
+
+Keys are created per organisation in the DeepTrust dashboard, under Settings
+and then API Keys (the tab is offered to voice-agent organisations). A key
+belongs to the organisation rather than to the person who made it, so it keeps
+working when they leave, and it reaches the agent endpoints and nothing else.
+
+The same key authenticates the hosted path's call-start webhook, so a workspace
+connected through Settings, Voice Agents needs no second credential.
+
+The API does not divide keys by scope today. When it does, the client already
+reports which scope was missing and which the key holds, rather than a bare
+403.
+
+```bash
+export DEEPTRUST_API_KEY=...
+export DEEPTRUST_BASE_URL=...   # optional, for a non-production workspace
+```
+
+The key is sent as `X-DeepTrust-Api-Key`. The default base URL is
+`https://app.deeptrust.ai/api/v1`; a `DEEPTRUST_BASE_URL` from 0.0.1 that ends
+in `/api` needs `/v1` appended.
+
+## Development
+
+```bash
+just install
+just check      # lint, types, tests
+```
+
+Everything runs through [uv](https://docs.astral.sh/uv/), so there is no
+virtualenv to activate. `just` on its own lists the rest.
+
+## Local development
+
+`dev/server.py` is a local stand-in for the API, so this client, both adapters
+and both examples run with no key and no network:
+
+```bash
+just devserver     # http://127.0.0.1:8080
+```
+
+It is not the analysis. The hosted API runs a reasoning model against an
+organisation's runbook, SOPs and controls; this matches a handful of patterns,
+which is enough to see a finding arrive and a nudge get delivered. A rule can
+never separate a caller relaying a real approval from one inventing it, which
+is the whole reason the real thing is not this.
+
+Point a client at it with `DEEPTRUST_BASE_URL`.
+
+## Status
+
+`0.0.1`, the first release. `analyze`, `end`, `watch` and both adapters work
+against the hosted API. `check` is defined and raises `NotImplementedError`.
+The shapes in `deeptrust.types` are the part most likely to move.
+
+The key travels in `X-DeepTrust-Api-Key`; the bearer form is still sent and
+goes away in 0.1.
+
+Apache 2.0.