Skip to main content

solari-sdk

Python client for the SOLARI API — creator and brand intelligence across Instagram and TikTok, plus Meta Threads profiles and posts. Standard library only; Python 3.9+; ships py.typed.

pip install solari-sdk

Quickstart

from solari_sdk import Solari

solari = Solari()  # reads SOLARI_TOKEN; or Solari(token="...")

hits = solari.tools.catalog.instagram.account.search(query="nike", limit=3)
brand = solari.tools.insight.instagram.brand.overview(username="nike")
thread = solari.tools.fetch.threads.post(url="https://www.threads.com/@zuck/post/Ddt7cL5EfUG")
tools = solari.list_tools()

For Threads, solari.tools.fetch.threads.account.search(query=...) finds handles by name and .post.search(query=...) returns Threads' top posts for a keyword (both live on every call, one page, not cached); .account(username=...), .posts(username=..., limit=...), and .post(url=...) (or code=...) read the profile, its newest posts, or one post with its first replies straight from the response. A first collection takes 5 to 30 seconds; repeat calls within an hour return the stored copy unless refresh=True.

For TikTok live search, solari.tools.fetch.tiktok.account.search(query=...) finds accounts by name and .post.search(query=...) finds videos by keyword, in TikTok's own order (live on every call, not cached, nothing stored). When has_more is true, pass next_cursor back as cursor= with the same query for the next page. Account hits carry account_id when already in the catalog, else .account(username=...) adds one; .post(url=...) collects and stores a video hit.

Follower and engagement trends: solari.tools.catalog.instagram.account.history(username=..., since=...) returns follower, following, and post counts at each collection (captured_at) plus current.collected_at, and solari.tools.catalog.instagram.content.history(username=..., posted_since=...) (or post_ids=, slugs=, urls=) returns each post's like, comment, play, and reshare counts over time. One point per UTC day by default (granularity="all" for every collection); gaps between points are normal.

Create an API key on your SOLARI My page (long-lived, solari_sk_…, shown once), or mint a short-lived token with solari auth token on a machine signed in to the solari CLI.

Typed tools

solari.tools is generated from the SOLARI tool registry: every tool is a real method with keyword-only, typed parameters (Literal[...] for enums), so pyright and mypy catch a missing required argument, a misspelled keyword, or a wrong enum value before anything runs, and your editor completes the paths.

solari.tools.catalog.instagram.account.search(query="nike", query_type="bio")
solari.tools.catalog.instagram.account.search(limit=3)  # type checker: missing "query"
solari.tools.catalog.instagram.account.search(query="nike", query_type="fuzzy")  # type checker: not a Literal value

Tool responses are JSON (Any) whose shape is documented per tool at solari.sh/docs.

solari.call(name, arguments=None, **kwargs) runs any tool by name, including the per-account solari_apps_* tools that are not in the generated catalog; solari.dynamic.<any>.<path>(**kwargs) spells such a call as a path without type checking.

API

  • Solari(token=None, base_url="https://solari.sh", timeout=150, user_agent=None, transport=None)
  • tools.<family>.<platform>.<group>.<name>(**kwargs) — typed tool calls; segments mirror the solari_ tool names.
  • call(name, arguments=None, **kwargs) — run a tool by name and get its JSON payload back.
  • list_tools() — every tool the signed-in account can call, with its JSON input schema.
  • get_tool(name) — one tool.
  • me() — the identity behind the token.
  • dynamic — untyped path proxy for tools that are not in the generated catalog.
  • SOLARI_TOOL_NAMES, SolariTools — the generated catalog.

Errors raise SolariError with status, code, message, tool, retry_after_seconds, and a retryable property (429, 502, 503, 504).

Development

python3 -m unittest discover -s tests -v
uvx pyright
uvx mypy --strict solari_sdk tests/typed_usage.py

solari_sdk/_tools.py is produced from the MCP worker's tool registry by pnpm run sdk:generate in cf-workers/solari-mcp; CI fails when it is stale.

Metadata

Release files for solari-sdk 0.2.12

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for solari-sdk 0.2.12
File Size Uploaded
solari_sdk-0.2.12.tar.gz 26.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for solari-sdk 0.2.12
File Interpreter ABI Platform
solari_sdk-0.2.12-py3-none-any.whl Python 3 none any Details

Total release size: 50.2 kB

Release files / solari_sdk-0.2.12.tar.gz

Download URL solari_sdk-0.2.12.tar.gz
Size 26.6 kB
Tags Source
SHA-256 checksum
How to use checksums
d88d3beeacf70c535e0c6975af459d0c5aeabc88d14666a9dadc7c758b3ab646
BLAKE2b-256 checksum
How to use checksums
506ecfc9b15db855ca3ce8513cbac85438af7e99cf168f0091ce1f1817a4083d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log

Release files / solari_sdk-0.2.12-py3-none-any.whl

Download URL solari_sdk-0.2.12-py3-none-any.whl
Size 23.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
59114635e548f1d576de74b4fdd4a88e143924f85ac0ab3168e190f86ddd1758
BLAKE2b-256 checksum
How to use checksums
02953a1aedabaebf9c4a2d2434542763199b1265195661b3d993c635ee7ef1e1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.15

2 release files

0.2.14

2 release files

0.2.13

2 release files

This release

0.2.12 This release

2 release files

0.2.11

2 release files

0.2.10

2 release files

0.2.9

2 release files

0.2.8

2 release files

0.2.7

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page