kedi-typesafe 0.1.0__tar.gz

kedi_typesafe-0.1.0/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer,
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

kedi_typesafe-0.1.0/.python-version

@@ -0,0 +1 @@
+3.12

kedi_typesafe-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Kedi Programming Language
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

kedi_typesafe-0.1.0/Makefile

@@ -0,0 +1,32 @@
+UV ?= uv
+
+.PHONY: format format-check lint ty basedpyright check tests coverage build prod
+
+format:
+	$(UV) run --group dev ruff check --fix .
+	$(UV) run --group dev ruff format .
+
+format-check:
+	$(UV) run --group dev ruff format --check .
+
+lint:
+	$(UV) run --group dev ruff check .
+
+ty:
+	$(UV) run --group dev ty check src
+
+basedpyright:
+	$(UV) run --group dev basedpyright
+
+check: lint format-check ty basedpyright
+
+tests:
+	$(UV) run --group dev pytest -m "not live"
+
+coverage:
+	$(UV) run --group dev pytest -m "not live" --cov --cov-branch --cov-fail-under=100
+
+build:
+	$(UV) build
+
+prod: check coverage build

kedi_typesafe-0.1.0/PKG-INFO

@@ -0,0 +1,181 @@
+Metadata-Version: 2.5
+Name: kedi-typesafe
+Version: 0.1.0
+Summary: TypeSafe AI integrations for Kedi
+Project-URL: Repository, https://github.com/kedi-lang/kedi-typesafe
+Project-URL: Issues, https://github.com/kedi-lang/kedi-typesafe/issues
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: pydantic-ai-slim==2.36.0
+Requires-Dist: typesafe-sdk==0.6.0
+Provides-Extra: all
+Requires-Dist: email-validator<3,>=2.3; extra == 'all'
+Requires-Dist: langchain==1.3.18; extra == 'all'
+Requires-Dist: phonenumbers<10,>=9; extra == 'all'
+Requires-Dist: pydantic-extra-types<3,>=2.10; extra == 'all'
+Provides-Extra: email
+Requires-Dist: email-validator<3,>=2.3; extra == 'email'
+Provides-Extra: langchain
+Requires-Dist: langchain==1.3.18; extra == 'langchain'
+Provides-Extra: phone
+Requires-Dist: phonenumbers<10,>=9; extra == 'phone'
+Requires-Dist: pydantic-extra-types<3,>=2.10; extra == 'phone'
+Description-Content-Type: text/markdown
+
+# kedi-typesafe
+
+Framework-native integrations for using TypeSafe AI's Jev models with Kedi's supported agent
+frameworks. Core Jev schema translation and the Pydantic AI and LangChain integrations ship as
+one `kedi-typesafe` package.
+
+## Pydantic AI
+
+Install the package and provide `TYPESAFE_API_KEY` in your environment:
+
+```bash
+pip install kedi-typesafe
+export TYPESAFE_API_KEY="your-key"
+```
+
+```python
+from typing import Literal
+
+from pydantic import BaseModel, Field
+from pydantic_ai import Agent
+
+from kedi_typesafe.integrations.pydantic import TypeSafeModel
+
+
+class Triage(BaseModel):
+    urgent: bool = Field(description="The request needs action today")
+    route: Literal["billing", "support", "other"] = Field(
+        description="Which team should handle the request?"
+    )
+
+
+model = TypeSafeModel("jev-latest")
+agent = Agent(model, output_type=Triage)
+result = agent.run_sync("I was charged twice. Please fix this today.")
+print(result.output)
+```
+
+The initial surface supports booleans, finite string `Literal`/`Enum` values, constrained text
+extraction, and flat Pydantic models composed of those fields. Pydantic's native `EmailStr` and
+`pydantic-extra-types` `PhoneNumber` schemas are recognized automatically. A JSON Schema `pattern`
+is treated as a regex candidate extractor; other string fields can provide an explicit field
+extractor:
+
+Install `kedi-typesafe[email]`, `kedi-typesafe[phone]`, or `kedi-typesafe[all]` when those optional
+Pydantic field types are used.
+
+```python
+from kedi_typesafe import RegexExtractor
+from kedi_typesafe.integrations.pydantic import TypeSafeModel
+
+model = TypeSafeModel(
+    text_extractors={"ticket_id": RegexExtractor(pattern=r"CASE-\d+")},
+)
+```
+
+Candidate extraction is deterministic and Jev only selects among values found in state, following
+TypeSafe's pre-parsed extraction pattern. Jev is not a free-form text-generation model, so
+unconstrained strings, tool calling, streaming, arbitrary numbers, nested models, and optional
+fields are rejected before a provider request is made.
+
+Boolean answers use Jev's Noul probability and a configurable threshold. The default decision is
+strictly `probability > 0.5`; the full probability remains available in model response metadata.
+
+## LangChain
+
+Install `kedi-typesafe[langchain]` and use the native structured-output surface:
+
+```python
+from typing import Literal
+
+from langchain.agents import create_agent
+from pydantic import BaseModel, Field
+
+from kedi_typesafe.integrations.langchain import TypeSafeChatModel
+
+
+class Triage(BaseModel):
+    urgent: bool = Field(description="The request needs action today")
+    route: Literal["billing", "support", "other"] = Field(
+        description="Which team should handle the request?"
+    )
+
+
+agent = create_agent(TypeSafeChatModel("jev-latest"), response_format=Triage)
+result = agent.invoke(
+    {"messages": [{"role": "user", "content": "I was charged twice. Fix this today."}]}
+)
+print(result["structured_response"])
+```
+
+`TypeSafeChatModel.with_structured_output(...)` is also supported for direct LangChain model use.
+The same Jev schema restrictions described above apply. Free-form invocation, function tools,
+media/tool history, stop sequences, and arbitrary model settings fail before a provider request.
+
+## Email and Phone Extraction
+
+Install the field validators:
+
+```bash
+pip install 'kedi-typesafe[email,phone]'
+```
+
+```python
+from pydantic import BaseModel, EmailStr, Field
+from pydantic_ai import Agent
+from pydantic_extra_types.phone_numbers import PhoneNumber
+
+from kedi_typesafe.integrations.pydantic import TypeSafeModel
+
+
+class Contact(BaseModel):
+    email: EmailStr = Field(description="The current support email, not the archived address")
+    phone: PhoneNumber = Field(description="The current support phone number")
+
+
+agent = Agent(TypeSafeModel(), output_type=Contact)
+result = agent.run_sync(
+    "Archived contact: old@example.com. Current support: help@example.com, +1 202-555-0100."
+)
+print(result.output)
+```
+
+Email and phone candidates are extracted from the supplied text automatically. Jev selects the
+candidate matching the field description; Pydantic then validates the result. Phone numbers use
+Pydantic's normalized format, for example `tel:+1-202-555-0100`. Provide international numbers
+with a country code. Missing candidates or a no-match answer raise an extraction error rather
+than inventing a value. All fields in this initial integration must be required.
+
+For LangChain, use the same `Contact` schema with
+`create_agent(TypeSafeChatModel(), response_format=Contact)` and install
+`kedi-typesafe[langchain,email,phone]`.
+
+## Runnable Examples
+
+After cloning this repository, run `uv sync --all-extras` and set `TYPESAFE_API_KEY`.
+
+| Example | Command |
+| --- | --- |
+| Pydantic classification | `uv run examples/pydantic_agent.py` |
+| LangChain classification | `uv run examples/langchain_agent.py` |
+| Pydantic email and phone | `uv run examples/pydantic_contacts.py` |
+| LangChain email and phone | `uv run examples/langchain_contacts.py` |
+
+These examples call the real TypeSafe API. An async context manager closes owned connections
+after use; it is optional for constructing the model. Reusing a model within the same event
+loop allows its HTTP connection to be reused.
+
+## Development
+
+```bash
+uv sync --all-extras --group dev
+make prod
+```
+
+Normal tests use deterministic typed fakes and never call TypeSafe. Live API validation is kept
+separate so CI and local quality gates do not consume credentials or incur cost.

kedi_typesafe-0.1.0/README.md

@@ -0,0 +1,156 @@
+# kedi-typesafe
+
+Framework-native integrations for using TypeSafe AI's Jev models with Kedi's supported agent
+frameworks. Core Jev schema translation and the Pydantic AI and LangChain integrations ship as
+one `kedi-typesafe` package.
+
+## Pydantic AI
+
+Install the package and provide `TYPESAFE_API_KEY` in your environment:
+
+```bash
+pip install kedi-typesafe
+export TYPESAFE_API_KEY="your-key"
+```
+
+```python
+from typing import Literal
+
+from pydantic import BaseModel, Field
+from pydantic_ai import Agent
+
+from kedi_typesafe.integrations.pydantic import TypeSafeModel
+
+
+class Triage(BaseModel):
+    urgent: bool = Field(description="The request needs action today")
+    route: Literal["billing", "support", "other"] = Field(
+        description="Which team should handle the request?"
+    )
+
+
+model = TypeSafeModel("jev-latest")
+agent = Agent(model, output_type=Triage)
+result = agent.run_sync("I was charged twice. Please fix this today.")
+print(result.output)
+```
+
+The initial surface supports booleans, finite string `Literal`/`Enum` values, constrained text
+extraction, and flat Pydantic models composed of those fields. Pydantic's native `EmailStr` and
+`pydantic-extra-types` `PhoneNumber` schemas are recognized automatically. A JSON Schema `pattern`
+is treated as a regex candidate extractor; other string fields can provide an explicit field
+extractor:
+
+Install `kedi-typesafe[email]`, `kedi-typesafe[phone]`, or `kedi-typesafe[all]` when those optional
+Pydantic field types are used.
+
+```python
+from kedi_typesafe import RegexExtractor
+from kedi_typesafe.integrations.pydantic import TypeSafeModel
+
+model = TypeSafeModel(
+    text_extractors={"ticket_id": RegexExtractor(pattern=r"CASE-\d+")},
+)
+```
+
+Candidate extraction is deterministic and Jev only selects among values found in state, following
+TypeSafe's pre-parsed extraction pattern. Jev is not a free-form text-generation model, so
+unconstrained strings, tool calling, streaming, arbitrary numbers, nested models, and optional
+fields are rejected before a provider request is made.
+
+Boolean answers use Jev's Noul probability and a configurable threshold. The default decision is
+strictly `probability > 0.5`; the full probability remains available in model response metadata.
+
+## LangChain
+
+Install `kedi-typesafe[langchain]` and use the native structured-output surface:
+
+```python
+from typing import Literal
+
+from langchain.agents import create_agent
+from pydantic import BaseModel, Field
+
+from kedi_typesafe.integrations.langchain import TypeSafeChatModel
+
+
+class Triage(BaseModel):
+    urgent: bool = Field(description="The request needs action today")
+    route: Literal["billing", "support", "other"] = Field(
+        description="Which team should handle the request?"
+    )
+
+
+agent = create_agent(TypeSafeChatModel("jev-latest"), response_format=Triage)
+result = agent.invoke(
+    {"messages": [{"role": "user", "content": "I was charged twice. Fix this today."}]}
+)
+print(result["structured_response"])
+```
+
+`TypeSafeChatModel.with_structured_output(...)` is also supported for direct LangChain model use.
+The same Jev schema restrictions described above apply. Free-form invocation, function tools,
+media/tool history, stop sequences, and arbitrary model settings fail before a provider request.
+
+## Email and Phone Extraction
+
+Install the field validators:
+
+```bash
+pip install 'kedi-typesafe[email,phone]'
+```
+
+```python
+from pydantic import BaseModel, EmailStr, Field
+from pydantic_ai import Agent
+from pydantic_extra_types.phone_numbers import PhoneNumber
+
+from kedi_typesafe.integrations.pydantic import TypeSafeModel
+
+
+class Contact(BaseModel):
+    email: EmailStr = Field(description="The current support email, not the archived address")
+    phone: PhoneNumber = Field(description="The current support phone number")
+
+
+agent = Agent(TypeSafeModel(), output_type=Contact)
+result = agent.run_sync(
+    "Archived contact: old@example.com. Current support: help@example.com, +1 202-555-0100."
+)
+print(result.output)
+```
+
+Email and phone candidates are extracted from the supplied text automatically. Jev selects the
+candidate matching the field description; Pydantic then validates the result. Phone numbers use
+Pydantic's normalized format, for example `tel:+1-202-555-0100`. Provide international numbers
+with a country code. Missing candidates or a no-match answer raise an extraction error rather
+than inventing a value. All fields in this initial integration must be required.
+
+For LangChain, use the same `Contact` schema with
+`create_agent(TypeSafeChatModel(), response_format=Contact)` and install
+`kedi-typesafe[langchain,email,phone]`.
+
+## Runnable Examples
+
+After cloning this repository, run `uv sync --all-extras` and set `TYPESAFE_API_KEY`.
+
+| Example | Command |
+| --- | --- |
+| Pydantic classification | `uv run examples/pydantic_agent.py` |
+| LangChain classification | `uv run examples/langchain_agent.py` |
+| Pydantic email and phone | `uv run examples/pydantic_contacts.py` |
+| LangChain email and phone | `uv run examples/langchain_contacts.py` |
+
+These examples call the real TypeSafe API. An async context manager closes owned connections
+after use; it is optional for constructing the model. Reusing a model within the same event
+loop allows its HTTP connection to be reused.
+
+## Development
+
+```bash
+uv sync --all-extras --group dev
+make prod
+```
+
+Normal tests use deterministic typed fakes and never call TypeSafe. Live API validation is kept
+separate so CI and local quality gates do not consume credentials or incur cost.

kedi_typesafe-0.1.0/examples/langchain_agent.py

@@ -0,0 +1,22 @@
+from typing import Literal
+
+from langchain.agents import create_agent
+from pydantic import BaseModel, Field
+
+from kedi_typesafe.integrations.langchain import TypeSafeChatModel
+
+
+class Triage(BaseModel):
+    urgent: bool = Field(description="The request needs action today")
+    route: Literal["billing", "support", "other"] = Field(
+        description="Which team should handle the request?"
+    )
+
+
+with TypeSafeChatModel("jev-latest") as model:
+    agent = create_agent(model, response_format=Triage)
+    result = agent.invoke(
+        {"messages": [{"role": "user", "content": "I was charged twice. Fix this today."}]}
+    )
+
+print(result["structured_response"])

kedi_typesafe-0.1.0/examples/langchain_contacts.py

@@ -0,0 +1,29 @@
+from langchain.agents import create_agent
+from pydantic import BaseModel, EmailStr, Field
+from pydantic_extra_types.phone_numbers import PhoneNumber
+
+from kedi_typesafe.integrations.langchain import TypeSafeChatModel
+
+
+class Contact(BaseModel):
+    email: EmailStr = Field(description="The current support email, not the archived address")
+    phone: PhoneNumber = Field(description="The current support phone number")
+
+
+with TypeSafeChatModel() as model:
+    agent = create_agent(model, response_format=Contact)
+    result = agent.invoke(
+        {
+            "messages": [
+                {
+                    "role": "user",
+                    "content": (
+                        "Archived contact: old@example.com. "
+                        "Current support: help@example.com, +1 202-555-0100."
+                    ),
+                }
+            ]
+        }
+    )
+    contact = Contact.model_validate(result["structured_response"])
+    print(contact.model_dump_json(indent=2))

kedi_typesafe-0.1.0/examples/pydantic_agent.py

@@ -0,0 +1,27 @@
+from __future__ import annotations
+
+import asyncio
+from typing import Literal
+
+from pydantic import BaseModel, Field
+from pydantic_ai import Agent
+
+from kedi_typesafe.integrations.pydantic import TypeSafeModel
+
+
+class Triage(BaseModel):
+    urgent: bool = Field(description="The request needs action today")
+    route: Literal["billing", "support", "other"] = Field(
+        description="Which team should handle the request?"
+    )
+
+
+async def main() -> None:
+    async with TypeSafeModel("jev-latest") as model:
+        agent = Agent(model, output_type=Triage)
+        result = await agent.run("I was charged twice. Please fix this today.")
+        print(result.output)
+
+
+if __name__ == "__main__":
+    asyncio.run(main())