jev-ultralightspeed 0.1.0__tar.gz

jev_ultralightspeed-0.1.0/LICENSE

@@ -0,0 +1,210 @@
+jev-ultralightspeed
+Copyright 2026 Alex Kwon <ask@collapseindex.org>
+https://github.com/collapseindex/jev-ultralightspeed
+
+Licensed under the Apache License, Version 2.0. Full text follows.
+
+------------------------------------------------------------------------
+
+
+                                 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 2026 Alex Kwon <ask@collapseindex.org>
+
+   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.

jev_ultralightspeed-0.1.0/PKG-INFO

@@ -0,0 +1,240 @@
+Metadata-Version: 2.4
+Name: jev-ultralightspeed
+Version: 0.1.0
+Summary: A pile of text, one question about each: bulk classification with TypeSafe's Jev at 16x the throughput and 41% less money, same accuracy.
+Author-email: Alex Kwon <ask@collapseindex.org>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/collapseindex/jev-ultralightspeed
+Project-URL: Source, https://github.com/collapseindex/jev-ultralightspeed
+Keywords: jev,typesafe,llm,classification,throughput,batching
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: fast
+Requires-Dist: httpx[http2]>=0.27; extra == "fast"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: httpx[http2]>=0.27; extra == "dev"
+Dynamic: license-file
+
+# jev-ultralightspeed
+
+**v0.1.0** · Apache-2.0 · no required dependencies
+
+<img src="docs/infographic.png" alt="Faster, cheaper, same accuracy: hundreds of items a second against dozens, with agreement against human labels unchanged" width="100%" />
+
+**You have a pile of text and one question about each.** Fifty thousand support tickets to triage.
+A quarter of reviews to sort by sentiment. A month of logs to flag. A column to backfill on a table
+you already have. This answers the question for all of them, with
+[TypeSafe's Jev](https://typesafe.ai), in the time it takes to get a coffee.
+
+```python
+from jev_ultralightspeed import classify
+
+answers = classify(tickets, "Does this message need a human to act on it today?")
+urgent = [a.item for a in answers if a.yes]
+```
+
+**15.9x the throughput of one request per item, 41% less money, and the same accuracy.** Measured
+over 30,000 judgements against human labels, in one run, with a script in this repository.
+
+**Not for one item at a time.** If somebody is waiting on the answer, call the API directly: packing
+makes a single item slower, not faster. This is for a queue.
+
+Not affiliated with TypeSafe; the hedgehog is a parody and belongs to nobody.
+
+## The benchmark
+
+30,000 judgements over the 1,347 completions in
+[dinostomp's](https://github.com/collapseindex/dinostomp) `xstest-refusal` pod, labelled
+compliance, refusal or partial by two human annotators, each completion seen about 22 times. Two
+arms, identical but for the shape of the requests. This is not Jev against another model: it is
+**jev-1.13.0 against itself**, same question, same items, same criteria.
+
+| | regular jev | jev + ultralightspeed |
+| --- | ---: | ---: |
+| throughput | 41.1 items/s | **653.4 items/s** |
+| wall clock | 12 min 11 s | **46 seconds** |
+| requests | 30,000 | 942 |
+| cost | $0.729 | **$0.430** |
+| agreement with the human labels | 89.3% (89.0 to 89.7) | **89.2% (88.9 to 89.6)** |
+| same answer across an item's repeats | 99.6% | 98.0% |
+| failed | 0 | 0 |
+| retried | 1 | 63 |
+
+**15.9x the throughput, 41% less money, and the accuracy is the same**: 89.3% against 89.2%, with
+30,000 judgements behind each figure and the intervals sitting on top of each other.
+
+```bash
+pip install "jev-ultralightspeed[fast]"
+git clone https://github.com/collapseindex/dinostomp.git ../dinostomp
+TYPESAFE_API_KEY=... python bench_eval.py            # about 13 minutes, about $1.20
+```
+
+Three things in that table are worth reading twice.
+
+**The baseline is not slow.** It is one item per request with the same eight requests in flight, so
+the 15.9x is against a client that is already parallel. Against an actual sequential loop it is far
+larger and far less interesting.
+
+**Sixty-three retries, and nothing failed.** Packing 32 deep with 8 in flight does hit transient
+limits at volume. The client backs off and sends them again, which is why this arm came in at 653
+items/s rather than the 800 it reaches on short bursts. Retries are counted in `usage.retries`, so
+this is a number rather than an absence of complaints.
+
+**Aggregate accuracy is identical; individual answers are slightly less repeatable.** Ask about the
+same completion 22 times and the unpacked client gives the same label 99.6% of the time, the packed
+one 98.0%. So pack freely when you want the total, and keep the pack size fixed when you are
+comparing item by item across runs.
+
+Shorter items do better than this on every axis, because the per-item text is a smaller share of
+each request: a million synthetic support messages (138 tokens each) ran at 1,135 items/s, 14.7
+minutes and $4.99 for the lot, over 31,400 requests with nothing retried. `soak.py --items 1000000`
+reproduces that, and it is a different corpus, so it is a footnote here rather than a headline.
+
+## How
+
+Nothing clever. Four things the obvious loop does not do, in order of how much they gave:
+
+1. **Pack.** Several items go in one request as `item_1..item_N`, each with its own question that
+   names the item it judges. One round trip covers thirty-two items, and the shared overhead is paid
+   once instead of thirty-two times. This is where both the speed and the token saving come from.
+2. **Parallel.** Several packed requests in flight, under a sliding-window limiter set below
+   TypeSafe's published 1,200 requests a minute.
+3. **One connection, kept open, multiplexed.** With httpx and h2 installed, every request in flight
+   shares a single HTTP/2 connection on one event loop, which measured about twice a thread per
+   connection on HTTP/1.1; keeping it open between calls rather than rebuilding it per batch was
+   worth another 2.5x. The transport idea is lifted from
+   [browser-use/jev-ultrafast](https://github.com/browser-use/jev-ultrafast), who got there first.
+4. **Never ask twice.** Identical text within a batch is asked once; a bounded cache keyed by model,
+   question and text answers repeats for free.
+
+## Install
+
+```bash
+pip install "jev-ultralightspeed[fast] @ git+https://github.com/collapseindex/jev-ultralightspeed"
+export TYPESAFE_API_KEY=...
+```
+
+The `[fast]` extra pulls in httpx and h2, which measured about twice the standard library path.
+Without it the client still works on the standard library alone:
+
+```bash
+pip install "git+https://github.com/collapseindex/jev-ultralightspeed"
+```
+
+Not on PyPI yet.
+
+## Use
+
+```python
+from jev_ultralightspeed import Client
+
+client = Client(pack=8, workers=8)     # the defaults are pack=8, workers=4
+client.warm()                          # open the connections before the work arrives
+
+answers = client.classify(
+    messages,
+    "Does this message need a human to act on it today?",
+    criteria={"true": "something is broken or costing money right now",
+              "false": "a question or a thank-you that can wait"},
+    on_progress=lambda done, total: print(f"{done}/{total}", end="\r"),
+)
+
+for answer in answers:
+    print(answer.label, round(answer.p, 2), answer.item[:60])
+
+print(client.usage)     # 256 items in 1.16s (221.1/s, 32 requests, 156 tokens/item, $0.00166)
+```
+
+Pick-one questions work the same way:
+
+```python
+answers = classify(tickets, "Which team should handle this?", options={
+    "billing": "payments, invoices, refunds",
+    "technical": "errors, outages, integrations",
+    "account": "logins, passwords, security",
+})
+```
+
+Every answer carries `item`, `label`, `p`, `distribution`, `confidence` and `kind`, and comes back in
+the order you passed the items in, however the requests were shuffled to get there.
+
+### Knobs
+
+| argument | default | what it does |
+| --- | --- | --- |
+| `pack` | 8 | items per request. Higher is faster and cheaper, and slower per request. On short items: pack 8 does 320 items/s, pack 32 does 1,130. |
+| `workers` | 4 | requests in flight. |
+| `transport` | `auto` | `http2` when httpx is installed, otherwise `threads`. |
+| `requests_per_minute` | 1000 | the ceiling the limiter holds, under TypeSafe's published 1,200. |
+| `cache` | True | answer repeats from memory, keyed by model, question and text. |
+| `model` | `jev-latest` | passed straight through. |
+| `url` | the Jev endpoint | point it at a gateway or a mock. |
+
+## What it does not do
+
+- **It does not change your question.** The only difference between a packed question and a single
+  one is the sentence naming which item to judge. There is no bitstring trick and no compressed
+  output format, because Jev returns a structured probability per question rather than generated
+  text: the output is already about twenty tokens per request.
+- **It does not cache across processes.** The cache lives in the client, in memory, bounded at
+  10,000 entries.
+- **It does not hide failures.** Retries cover 429, 500, 502, 503, 504 and 529 with backoff; anything
+  else is raised with what the API said.
+- **It is not an eval harness.** It makes a judge fast, not trustworthy. See Related below.
+
+## Development
+
+```bash
+pip install pytest
+python -m pytest tests -q        # 21 tests, no network, no key needed
+
+TYPESAFE_API_KEY=... python bench_eval.py            # the table above, ~13 min, ~$1.20
+TYPESAFE_API_KEY=... python bench.py --items 256     # pack and concurrency sweep, ~5 cents
+TYPESAFE_API_KEY=... python soak.py --items 100000   # sustained load, ~50 cents
+```
+
+The tests replace the one method that talks to the API, so the packing, the deduplication, the cache,
+the ordering, the limiter and the error paths are all checked offline.
+
+## Related
+
+Three tools, one workflow, all Apache-2.0:
+
+Costs are input tokens at TypeSafe's published $0.042 per million for jev-1.13.0, which is the only
+rate they list; output tokens are counted but not priced. Every dollar figure here was checked
+against the account balance after the run.
+
+- **[dinostomp](https://github.com/collapseindex/dinostomp)** is the harness the benchmark above was
+  measured against: pods of labelled items, pre-registered thresholds, a checks registry and a
+  findings ledger. It is where you go when the question is whether a judge is any good, not how
+  fast it runs. The 1,347 labelled completions in the table are one of its audit pods.
+- **[jev-builder](https://collapseindex.github.io/jev-builder/)** writes the request in the first
+  place: paste your text, describe the question, and get something you can paste here.
+- **jev-ultralightspeed**, this repository, is for when the question already works and there are a
+  million rows waiting.
+
+If any of it saves you an afternoon, [sponsorship](https://github.com/sponsors/collapseindex) keeps
+it maintained. Not required, and nothing here is gated.
+
+## Security
+
+The key comes from your environment, goes to one endpoint and is never logged, printed, put in an
+exception or written to disk. What the library sends, what it keeps in memory, and what it does not
+protect you from: [SECURITY.md](SECURITY.md).
+
+## Contributing
+
+Issues and pull requests are welcome. The rules that matter: no required dependencies, never log the
+key, and a performance claim needs a measurement rather than an opinion about how HTTP works. See
+[CONTRIBUTING.md](CONTRIBUTING.md).
+
+## License
+
+[Apache-2.0](LICENSE). Not affiliated with TypeSafe.

jev_ultralightspeed-0.1.0/README.md

@@ -0,0 +1,216 @@
+# jev-ultralightspeed
+
+**v0.1.0** · Apache-2.0 · no required dependencies
+
+<img src="docs/infographic.png" alt="Faster, cheaper, same accuracy: hundreds of items a second against dozens, with agreement against human labels unchanged" width="100%" />
+
+**You have a pile of text and one question about each.** Fifty thousand support tickets to triage.
+A quarter of reviews to sort by sentiment. A month of logs to flag. A column to backfill on a table
+you already have. This answers the question for all of them, with
+[TypeSafe's Jev](https://typesafe.ai), in the time it takes to get a coffee.
+
+```python
+from jev_ultralightspeed import classify
+
+answers = classify(tickets, "Does this message need a human to act on it today?")
+urgent = [a.item for a in answers if a.yes]
+```
+
+**15.9x the throughput of one request per item, 41% less money, and the same accuracy.** Measured
+over 30,000 judgements against human labels, in one run, with a script in this repository.
+
+**Not for one item at a time.** If somebody is waiting on the answer, call the API directly: packing
+makes a single item slower, not faster. This is for a queue.
+
+Not affiliated with TypeSafe; the hedgehog is a parody and belongs to nobody.
+
+## The benchmark
+
+30,000 judgements over the 1,347 completions in
+[dinostomp's](https://github.com/collapseindex/dinostomp) `xstest-refusal` pod, labelled
+compliance, refusal or partial by two human annotators, each completion seen about 22 times. Two
+arms, identical but for the shape of the requests. This is not Jev against another model: it is
+**jev-1.13.0 against itself**, same question, same items, same criteria.
+
+| | regular jev | jev + ultralightspeed |
+| --- | ---: | ---: |
+| throughput | 41.1 items/s | **653.4 items/s** |
+| wall clock | 12 min 11 s | **46 seconds** |
+| requests | 30,000 | 942 |
+| cost | $0.729 | **$0.430** |
+| agreement with the human labels | 89.3% (89.0 to 89.7) | **89.2% (88.9 to 89.6)** |
+| same answer across an item's repeats | 99.6% | 98.0% |
+| failed | 0 | 0 |
+| retried | 1 | 63 |
+
+**15.9x the throughput, 41% less money, and the accuracy is the same**: 89.3% against 89.2%, with
+30,000 judgements behind each figure and the intervals sitting on top of each other.
+
+```bash
+pip install "jev-ultralightspeed[fast]"
+git clone https://github.com/collapseindex/dinostomp.git ../dinostomp
+TYPESAFE_API_KEY=... python bench_eval.py            # about 13 minutes, about $1.20
+```
+
+Three things in that table are worth reading twice.
+
+**The baseline is not slow.** It is one item per request with the same eight requests in flight, so
+the 15.9x is against a client that is already parallel. Against an actual sequential loop it is far
+larger and far less interesting.
+
+**Sixty-three retries, and nothing failed.** Packing 32 deep with 8 in flight does hit transient
+limits at volume. The client backs off and sends them again, which is why this arm came in at 653
+items/s rather than the 800 it reaches on short bursts. Retries are counted in `usage.retries`, so
+this is a number rather than an absence of complaints.
+
+**Aggregate accuracy is identical; individual answers are slightly less repeatable.** Ask about the
+same completion 22 times and the unpacked client gives the same label 99.6% of the time, the packed
+one 98.0%. So pack freely when you want the total, and keep the pack size fixed when you are
+comparing item by item across runs.
+
+Shorter items do better than this on every axis, because the per-item text is a smaller share of
+each request: a million synthetic support messages (138 tokens each) ran at 1,135 items/s, 14.7
+minutes and $4.99 for the lot, over 31,400 requests with nothing retried. `soak.py --items 1000000`
+reproduces that, and it is a different corpus, so it is a footnote here rather than a headline.
+
+## How
+
+Nothing clever. Four things the obvious loop does not do, in order of how much they gave:
+
+1. **Pack.** Several items go in one request as `item_1..item_N`, each with its own question that
+   names the item it judges. One round trip covers thirty-two items, and the shared overhead is paid
+   once instead of thirty-two times. This is where both the speed and the token saving come from.
+2. **Parallel.** Several packed requests in flight, under a sliding-window limiter set below
+   TypeSafe's published 1,200 requests a minute.
+3. **One connection, kept open, multiplexed.** With httpx and h2 installed, every request in flight
+   shares a single HTTP/2 connection on one event loop, which measured about twice a thread per
+   connection on HTTP/1.1; keeping it open between calls rather than rebuilding it per batch was
+   worth another 2.5x. The transport idea is lifted from
+   [browser-use/jev-ultrafast](https://github.com/browser-use/jev-ultrafast), who got there first.
+4. **Never ask twice.** Identical text within a batch is asked once; a bounded cache keyed by model,
+   question and text answers repeats for free.
+
+## Install
+
+```bash
+pip install "jev-ultralightspeed[fast] @ git+https://github.com/collapseindex/jev-ultralightspeed"
+export TYPESAFE_API_KEY=...
+```
+
+The `[fast]` extra pulls in httpx and h2, which measured about twice the standard library path.
+Without it the client still works on the standard library alone:
+
+```bash
+pip install "git+https://github.com/collapseindex/jev-ultralightspeed"
+```
+
+Not on PyPI yet.
+
+## Use
+
+```python
+from jev_ultralightspeed import Client
+
+client = Client(pack=8, workers=8)     # the defaults are pack=8, workers=4
+client.warm()                          # open the connections before the work arrives
+
+answers = client.classify(
+    messages,
+    "Does this message need a human to act on it today?",
+    criteria={"true": "something is broken or costing money right now",
+              "false": "a question or a thank-you that can wait"},
+    on_progress=lambda done, total: print(f"{done}/{total}", end="\r"),
+)
+
+for answer in answers:
+    print(answer.label, round(answer.p, 2), answer.item[:60])
+
+print(client.usage)     # 256 items in 1.16s (221.1/s, 32 requests, 156 tokens/item, $0.00166)
+```
+
+Pick-one questions work the same way:
+
+```python
+answers = classify(tickets, "Which team should handle this?", options={
+    "billing": "payments, invoices, refunds",
+    "technical": "errors, outages, integrations",
+    "account": "logins, passwords, security",
+})
+```
+
+Every answer carries `item`, `label`, `p`, `distribution`, `confidence` and `kind`, and comes back in
+the order you passed the items in, however the requests were shuffled to get there.
+
+### Knobs
+
+| argument | default | what it does |
+| --- | --- | --- |
+| `pack` | 8 | items per request. Higher is faster and cheaper, and slower per request. On short items: pack 8 does 320 items/s, pack 32 does 1,130. |
+| `workers` | 4 | requests in flight. |
+| `transport` | `auto` | `http2` when httpx is installed, otherwise `threads`. |
+| `requests_per_minute` | 1000 | the ceiling the limiter holds, under TypeSafe's published 1,200. |
+| `cache` | True | answer repeats from memory, keyed by model, question and text. |
+| `model` | `jev-latest` | passed straight through. |
+| `url` | the Jev endpoint | point it at a gateway or a mock. |
+
+## What it does not do
+
+- **It does not change your question.** The only difference between a packed question and a single
+  one is the sentence naming which item to judge. There is no bitstring trick and no compressed
+  output format, because Jev returns a structured probability per question rather than generated
+  text: the output is already about twenty tokens per request.
+- **It does not cache across processes.** The cache lives in the client, in memory, bounded at
+  10,000 entries.
+- **It does not hide failures.** Retries cover 429, 500, 502, 503, 504 and 529 with backoff; anything
+  else is raised with what the API said.
+- **It is not an eval harness.** It makes a judge fast, not trustworthy. See Related below.
+
+## Development
+
+```bash
+pip install pytest
+python -m pytest tests -q        # 21 tests, no network, no key needed
+
+TYPESAFE_API_KEY=... python bench_eval.py            # the table above, ~13 min, ~$1.20
+TYPESAFE_API_KEY=... python bench.py --items 256     # pack and concurrency sweep, ~5 cents
+TYPESAFE_API_KEY=... python soak.py --items 100000   # sustained load, ~50 cents
+```
+
+The tests replace the one method that talks to the API, so the packing, the deduplication, the cache,
+the ordering, the limiter and the error paths are all checked offline.
+
+## Related
+
+Three tools, one workflow, all Apache-2.0:
+
+Costs are input tokens at TypeSafe's published $0.042 per million for jev-1.13.0, which is the only
+rate they list; output tokens are counted but not priced. Every dollar figure here was checked
+against the account balance after the run.
+
+- **[dinostomp](https://github.com/collapseindex/dinostomp)** is the harness the benchmark above was
+  measured against: pods of labelled items, pre-registered thresholds, a checks registry and a
+  findings ledger. It is where you go when the question is whether a judge is any good, not how
+  fast it runs. The 1,347 labelled completions in the table are one of its audit pods.
+- **[jev-builder](https://collapseindex.github.io/jev-builder/)** writes the request in the first
+  place: paste your text, describe the question, and get something you can paste here.
+- **jev-ultralightspeed**, this repository, is for when the question already works and there are a
+  million rows waiting.
+
+If any of it saves you an afternoon, [sponsorship](https://github.com/sponsors/collapseindex) keeps
+it maintained. Not required, and nothing here is gated.
+
+## Security
+
+The key comes from your environment, goes to one endpoint and is never logged, printed, put in an
+exception or written to disk. What the library sends, what it keeps in memory, and what it does not
+protect you from: [SECURITY.md](SECURITY.md).
+
+## Contributing
+
+Issues and pull requests are welcome. The rules that matter: no required dependencies, never log the
+key, and a performance claim needs a measurement rather than an opinion about how HTTP works. See
+[CONTRIBUTING.md](CONTRIBUTING.md).
+
+## License
+
+[Apache-2.0](LICENSE). Not affiliated with TypeSafe.