axio-responses 0.1.0__tar.gz

axio_responses-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+.venv/
+__pycache__/
+*.pyc
+*.pyo
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+*.egg-info/
+dist/
+build/
+_build/
+.DS_Store
+*.sqlite
+*.db

axio_responses-0.1.0/PKG-INFO

@@ -0,0 +1,106 @@
+Metadata-Version: 2.5
+Name: axio-responses
+Version: 0.1.0
+Summary: The OpenAI Responses API as axio speaks it: request items in, StreamEvents out
+Project-URL: Documentation, https://docs.axio-agent.com
+Project-URL: Homepage, https://github.com/mosquito/axio-agent
+Project-URL: Repository, https://github.com/mosquito/axio-agent
+License: MIT
+Keywords: agent,llm,openai,responses,streaming
+Requires-Python: >=3.12
+Requires-Dist: axio
+Requires-Dist: axio-sse
+Description-Content-Type: text/markdown
+
+# axio-responses
+
+[![PyPI](https://img.shields.io/pypi/v/axio-responses)](https://pypi.org/project/axio-responses/)
+[![Python](https://img.shields.io/pypi/pyversions/axio-responses)](https://pypi.org/project/axio-responses/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+The OpenAI Responses API as [axio](https://github.com/mosquito/axio-agent) speaks it: request items
+in, `StreamEvent`s out.
+
+Both halves live here rather than in a transport because two transports speak this API — the public
+`/v1/responses` endpoint and the ChatGPT backend Codex uses. It knows nothing about HTTP and opens
+no connection.
+
+## Installation
+
+```bash
+pip install axio-responses
+```
+
+## Usage
+
+### Building the request
+
+<!-- name: test_readme_building_a_request -->
+```python
+from axio.blocks import TextBlock
+from axio.messages import Message
+from axio_responses import convert_messages, convert_tools
+
+messages, system, tools = [Message(role="user", content=[TextBlock(text="hi")])], "be brief", []
+
+instructions, items = convert_messages(messages, system)
+payload = {
+    "model": "gpt-5.6",
+    "instructions": instructions,
+    "input": items,
+    "stream": True,
+    "tools": convert_tools(tools),
+}
+assert payload["instructions"] == "be brief"
+```
+
+`convert_messages` returns the system prompt separately, because this API takes it as
+`instructions` rather than as a message. Tool calls and their outputs become `function_call` and
+`function_call_output` items beside the messages, not blocks inside them.
+
+### Reading the stream
+
+`Responses` is an `axio_sse.Reader`: one `@on(...)` method per event, dispatching on the payload's
+own `type`. Its class body names only the events it interprets. The API publishes one event family
+per tool it can run, so that set grows with the tools and not with the protocol; everything else is
+forwarded through `unmatched()` rather than dropped.
+
+<!-- name: test_readme_reading_the_stream -->
+```python
+from collections.abc import AsyncIterator
+
+import aiohttp
+from axio.events import StreamEvent
+from axio_responses import Responses
+
+
+async def stream(resp: aiohttp.ClientResponse) -> AsyncIterator[StreamEvent]:
+    turn = Responses()
+    async for made in turn.over(resp.content.iter_any(), until="[DONE]"):
+        yield made
+    yield turn.finished()
+```
+
+Events axio has no type for — the API's own hosted tools, its audio, its bookkeeping — travel as
+`ProviderEvent` under the provider's own name rather than being dropped.
+
+### Holding it against the schema
+
+<!-- name: test_readme_names_are_published -->
+```python
+from axio_responses import Responses
+
+PUBLISHED_EVENTS = {"response.output_text.delta", "response.completed", "response.refusal.delta"}
+
+# Every name the reader claims is one the schema publishes. A typo is a handler that never runs.
+assert Responses.names() >= PUBLISHED_EVENTS
+```
+
+`names()` answers what the reader claims, so a test can hold it against the union OpenAI publishes.
+The check is `<=`, not `==`: the reader deliberately names fewer events than the API sends. Reading
+with `strict=True` raises `UnknownEvent` on a name it does not claim, which is how a test fails on
+the day OpenAI adds one.
+
+## License
+
+MIT

axio_responses-0.1.0/README.md

@@ -0,0 +1,92 @@
+# axio-responses
+
+[![PyPI](https://img.shields.io/pypi/v/axio-responses)](https://pypi.org/project/axio-responses/)
+[![Python](https://img.shields.io/pypi/pyversions/axio-responses)](https://pypi.org/project/axio-responses/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+The OpenAI Responses API as [axio](https://github.com/mosquito/axio-agent) speaks it: request items
+in, `StreamEvent`s out.
+
+Both halves live here rather than in a transport because two transports speak this API — the public
+`/v1/responses` endpoint and the ChatGPT backend Codex uses. It knows nothing about HTTP and opens
+no connection.
+
+## Installation
+
+```bash
+pip install axio-responses
+```
+
+## Usage
+
+### Building the request
+
+<!-- name: test_readme_building_a_request -->
+```python
+from axio.blocks import TextBlock
+from axio.messages import Message
+from axio_responses import convert_messages, convert_tools
+
+messages, system, tools = [Message(role="user", content=[TextBlock(text="hi")])], "be brief", []
+
+instructions, items = convert_messages(messages, system)
+payload = {
+    "model": "gpt-5.6",
+    "instructions": instructions,
+    "input": items,
+    "stream": True,
+    "tools": convert_tools(tools),
+}
+assert payload["instructions"] == "be brief"
+```
+
+`convert_messages` returns the system prompt separately, because this API takes it as
+`instructions` rather than as a message. Tool calls and their outputs become `function_call` and
+`function_call_output` items beside the messages, not blocks inside them.
+
+### Reading the stream
+
+`Responses` is an `axio_sse.Reader`: one `@on(...)` method per event, dispatching on the payload's
+own `type`. Its class body names only the events it interprets. The API publishes one event family
+per tool it can run, so that set grows with the tools and not with the protocol; everything else is
+forwarded through `unmatched()` rather than dropped.
+
+<!-- name: test_readme_reading_the_stream -->
+```python
+from collections.abc import AsyncIterator
+
+import aiohttp
+from axio.events import StreamEvent
+from axio_responses import Responses
+
+
+async def stream(resp: aiohttp.ClientResponse) -> AsyncIterator[StreamEvent]:
+    turn = Responses()
+    async for made in turn.over(resp.content.iter_any(), until="[DONE]"):
+        yield made
+    yield turn.finished()
+```
+
+Events axio has no type for — the API's own hosted tools, its audio, its bookkeeping — travel as
+`ProviderEvent` under the provider's own name rather than being dropped.
+
+### Holding it against the schema
+
+<!-- name: test_readme_names_are_published -->
+```python
+from axio_responses import Responses
+
+PUBLISHED_EVENTS = {"response.output_text.delta", "response.completed", "response.refusal.delta"}
+
+# Every name the reader claims is one the schema publishes. A typo is a handler that never runs.
+assert Responses.names() >= PUBLISHED_EVENTS
+```
+
+`names()` answers what the reader claims, so a test can hold it against the union OpenAI publishes.
+The check is `<=`, not `==`: the reader deliberately names fewer events than the API sends. Reading
+with `strict=True` raises `UnknownEvent` on a name it does not claim, which is how a test fails on
+the day OpenAI adds one.
+
+## License
+
+MIT

axio_responses-0.1.0/pyproject.toml

@@ -0,0 +1,47 @@
+[project]
+name = "axio-responses"
+version = "0.1.0"
+description = "The OpenAI Responses API as axio speaks it: request items in, StreamEvents out"
+readme = "README.md"
+requires-python = ">=3.12"
+license = {text = "MIT"}
+keywords = ["openai", "responses", "llm", "agent", "streaming"]
+dependencies = ["axio", "axio-sse"]
+
+[project.urls]
+Documentation = "https://docs.axio-agent.com"
+Homepage = "https://github.com/mosquito/axio-agent"
+Repository = "https://github.com/mosquito/axio-agent"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/axio_responses"]
+
+[tool.pytest.ini_options]
+asyncio_mode = "auto"
+testpaths = ["tests", "README.md"]
+
+[tool.ruff]
+line-length = 119
+output-format = "concise"
+target-version = "py312"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP"]
+
+[tool.mypy]
+strict = true
+python_version = "3.12"
+
+[dependency-groups]
+dev = [
+    "pytest>=8",
+    "pytest-asyncio>=0.24",
+    "mypy>=1.14",
+    "ruff>=0.9",
+    "pytest-cov>=7.1.0",
+    "markdown-pytest>=0.6.0",
+]

axio_responses-0.1.0/src/axio_responses/__init__.py

@@ -0,0 +1,67 @@
+"""The OpenAI Responses API as axio speaks it.
+
+``convert_messages`` and ``convert_tools`` build the request. ``Responses`` reads the stream it
+answers with. Both halves are here rather than in a transport because two transports speak this
+API: the public ``/v1/responses`` endpoint and the ChatGPT backend Codex uses.
+"""
+
+from __future__ import annotations
+
+from .reader import (
+    Annotation,
+    AnnotationAdded,
+    AnnotationSource,
+    ArgumentsDelta,
+    ArgumentsDone,
+    Completed,
+    ContentPartDone,
+    Created,
+    Failed,
+    Incomplete,
+    IncompleteDetails,
+    InputDetails,
+    ItemAdded,
+    ItemDone,
+    OutputDetails,
+    OutputItem,
+    ReasoningDeltaEvent,
+    RefusalDeltaEvent,
+    ResponseError,
+    ResponseObject,
+    Responses,
+    ResponseUsage,
+    StreamFailure,
+    TextDeltaEvent,
+)
+from .request import STOP_REASONS, convert_messages, convert_tools, tool_output
+
+__all__ = [
+    "STOP_REASONS",
+    "Annotation",
+    "AnnotationAdded",
+    "AnnotationSource",
+    "ArgumentsDelta",
+    "ArgumentsDone",
+    "ContentPartDone",
+    "Completed",
+    "Created",
+    "Failed",
+    "Incomplete",
+    "IncompleteDetails",
+    "InputDetails",
+    "ItemAdded",
+    "ItemDone",
+    "OutputDetails",
+    "OutputItem",
+    "ReasoningDeltaEvent",
+    "RefusalDeltaEvent",
+    "ResponseError",
+    "ResponseObject",
+    "ResponseUsage",
+    "Responses",
+    "StreamFailure",
+    "TextDeltaEvent",
+    "convert_messages",
+    "convert_tools",
+    "tool_output",
+]