scavio-haystack 0.1.2__tar.gz → 0.1.4__tar.gz

{scavio_haystack-0.1.2 → scavio_haystack-0.1.4}/CHANGELOG.md

@@ -4,14 +4,26 @@ The version is derived from the git tag by `hatch-vcs`, and PyPI is published by
 the tag push. A heading here is therefore only real if a matching `vX.Y.Z` tag
 exists.
 
-## [Unreleased] — ships as v0.1.2
+## [v0.1.4]
+
+### Changed
+
+- README: most Instagram calls cost 2 credits (was 2-10).
+
+## [v0.1.3]
+
+### Changed
+
+- README: YouTube transcripts cost 5 credits (was 8).
+
+## [v0.1.2]
 
 > **Ledger correction.** Earlier revisions of this file carried `[v0.1.2]` and
 > `[v0.1.3]` headings. Neither version was ever tagged and neither reached PyPI,
 > which is still on `0.1.1` — the code they described has sat on `main`,
 > unreleased, since it was written. The two headings are collapsed into this one
 > entry, which ships as `v0.1.2` when the tag is cut. Nothing was published under
-> `0.1.3`; that version number does not exist and is not reserved.
+> `0.1.3` at the time; the later v0.1.3 above is an unrelated README release.
 
 ### Changed
 

{scavio_haystack-0.1.2 → scavio_haystack-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: scavio-haystack
-Version: 0.1.2
+Version: 0.1.4
 Summary: Haystack integration for Scavio Web Search
 Project-URL: Documentation, https://github.com/scavio-ai/haystack-scavio#readme
 Project-URL: Issues, https://github.com/scavio-ai/haystack-scavio/issues
@@ -53,7 +53,7 @@ That is the whole surface. A Haystack web search component has one job — turn
 endpoint on purpose rather than growing into a general-purpose API client.
 
 **Credits:** 1 credit per `run` / `run_async` call. Nothing here touches the endpoints that
-cost more (YouTube transcripts are 8, Instagram is 2-10, a LinkedIn job is 30) or the
+cost more (YouTube transcripts are 5, most Instagram calls are 2, a LinkedIn job is 30) or the
 body-priced ones, whose cost is a function of the request rather than a flat number
 (Walmart, Threads, Kuaishou and `extract`). A `ScavioWebSearch` pipeline is flat 1 credit
 per search.

{scavio_haystack-0.1.2 → scavio_haystack-0.1.4}/README.md

@@ -26,7 +26,7 @@ That is the whole surface. A Haystack web search component has one job — turn
 endpoint on purpose rather than growing into a general-purpose API client.
 
 **Credits:** 1 credit per `run` / `run_async` call. Nothing here touches the endpoints that
-cost more (YouTube transcripts are 8, Instagram is 2-10, a LinkedIn job is 30) or the
+cost more (YouTube transcripts are 5, most Instagram calls are 2, a LinkedIn job is 30) or the
 body-priced ones, whose cost is a function of the request rather than a flat number
 (Walmart, Threads, Kuaishou and `extract`). A `ScavioWebSearch` pipeline is flat 1 credit
 per search.