getanyapi 0.66.0__tar.gz → 0.66.2__tar.gz

{getanyapi-0.66.0 → getanyapi-0.66.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: getanyapi
-Version: 0.66.0
+Version: 0.66.2
 Summary: Official typed Python SDK for AnyAPI: any API, one wallet, USD, no subscriptions.
 Project-URL: Homepage, https://getanyapi.com
 Project-URL: Documentation, https://getanyapi.com/docs

{getanyapi-0.66.0 → getanyapi-0.66.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "getanyapi"
-version = "0.66.0"
+version = "0.66.2"
 description = "Official typed Python SDK for AnyAPI: any API, one wallet, USD, no subscriptions."
 readme = "README.md"
 requires-python = ">=3.10"

{getanyapi-0.66.0 → getanyapi-0.66.2}/src/getanyapi/__init__.py

@@ -55,7 +55,7 @@ from .types import (
     unwrap,
 )
 
-__version__ = "0.66.0"
+__version__ = "0.66.2"
 
 __all__ = [
     # clients + top-level functions

{getanyapi-0.66.0 → getanyapi-0.66.2}/src/getanyapi/platforms/linkedin.py

@@ -4175,7 +4175,7 @@ class LinkedinNamespace:
         List the employees of a LinkedIn company by name or company URL, with
         optional job-title filtering.
 
-        Price: $0 per request plus $0.011 per result (maximum $0.11).
+        Price: $0.0032 per request plus $0.0048 per result (maximum $0.0512).
 
         Example:
             res = client.linkedin.company_employees(company="stripe", limit=3)
@@ -4585,7 +4585,9 @@ class LinkedinNamespace:
     ) -> RunResult[LinkedinSearchPostsData]:
         """LinkedIn Post Search
 
-        Search public LinkedIn posts by keyword (text, link, publish date).
+        Search public LinkedIn posts by keyword (text, link, publish date). Results
+        come from search-engine matches over public LinkedIn posts and work best
+        with English keywords.
 
         Price: $0.0012 per request.
 
@@ -4867,7 +4869,7 @@ class AsyncLinkedinNamespace:
         List the employees of a LinkedIn company by name or company URL, with
         optional job-title filtering.
 
-        Price: $0 per request plus $0.011 per result (maximum $0.11).
+        Price: $0.0032 per request plus $0.0048 per result (maximum $0.0512).
 
         Example:
             res = client.linkedin.company_employees(company="stripe", limit=3)
@@ -5277,7 +5279,9 @@ class AsyncLinkedinNamespace:
     ) -> RunResult[LinkedinSearchPostsData]:
         """LinkedIn Post Search
 
-        Search public LinkedIn posts by keyword (text, link, publish date).
+        Search public LinkedIn posts by keyword (text, link, publish date). Results
+        come from search-engine matches over public LinkedIn posts and work best
+        with English keywords.
 
         Price: $0.0012 per request.
 

{getanyapi-0.66.0 → getanyapi-0.66.2}/src/getanyapi/platforms/twitter.py

@@ -180,9 +180,9 @@ class TwitterSearchInput(TypedDict, total=False):
     preferLatencyUnderMs: NotRequired[int]
     """Optional; omit it and routing is unchanged, with the cheapest source serving. Prefer sources whose typical response time (median over the trailing 30 days, as published on this endpoint's lane health) is under this many milliseconds; among those, the cheapest serves. This can raise your price: when the cheapest source misses the target, a faster and dearer one serves, and you are quoted and charged its price. If no source is that fast the request is still served, by whichever source offers the best speed for its price - it is never refused for being slow. Sources we have not timed are tried last. This is a preference, not a guarantee: the median describes past requests and is not a ceiling on this one, and it excludes any wait this request itself asks for. On a paginated walk it applies to the first page only: later pages stay with the source that page chose, at the price it was quoted. Minimum: 1."""
     query: Required[str]
-    """Search query using X (Twitter) advanced-search syntax. IMPORTANT: bare terms are ANDed - a tweet must contain EVERY word, so a list of loosely related keywords matches nothing; use one short phrase or OR between alternatives (e.g. 'anyapi OR getanyapi'). You can embed X advanced-search operators directly in the query to filter results: from:username and to:username (author or recipient), since:YYYY-MM-DD and until:YYYY-MM-DD (date range), min_faves:N, min_retweets:N, min_replies:N (engagement floors), "exact phrase", -term to exclude, filter:media and filter:links and -filter:replies (content filters), lang:en, near:city, and geocode:lat,long,radius. Examples: 'from:OpenAI', 'AI agents min_faves:500 -filter:replies', 'nvidia since:2026-01-01 until:2026-03-01'. A query with no matches returns an empty items array; prefer the fewest words that identify the topic."""
+    """Search query using X (Twitter) advanced-search syntax. IMPORTANT: bare terms are ANDed - a tweet must contain EVERY word, so a list of loosely related keywords matches nothing; use one short phrase or OR between alternatives (e.g. 'anyapi OR getanyapi'). When an operator follows an OR list, put the list in parentheses, e.g. '(anyapi OR getanyapi) -filter:replies': without them X applies the operator to the last alternative only, so such a query is refused at no charge with the corrected query. You can embed X advanced-search operators directly in the query to filter results: from:username and to:username (author or recipient), since:YYYY-MM-DD and until:YYYY-MM-DD (date range), min_faves:N, min_retweets:N, min_replies:N (engagement floors), "exact phrase", -term to exclude, filter:media and filter:links and -filter:replies (content filters), lang:en, near:city, and geocode:lat,long,radius. Examples: 'from:OpenAI', 'AI agents min_faves:500 -filter:replies', 'nvidia since:2026-01-01 until:2026-03-01'. A query with no matches returns an empty items array; prefer the fewest words that identify the topic."""
     queryType: NotRequired[Literal["Latest", "Top", "Photos", "Videos"]]
-    """Result ranking: 'Latest', 'Top', 'Photos', or 'Videos' (e.g. Latest). Default: Latest."""
+    """Which posts to return: 'Latest' (newest first, the default), 'Top' (most popular), 'Photos' (newest posts with images), or 'Videos' (newest posts with video). Photos and Videos search your query as written with filter:images or filter:videos added after it, so they cost the same as a Latest search. Default: Latest."""
     requireFields: NotRequired[
         list[
             Literal[