Data & analysis

sentisense-cli

Try it

Fetch US stock quotes, sentiment scores, and market data through a single npx command without installing anything.

What it does

The sentisense-cli is a command-line interface to the SentiSense Data API, delivering US stock market data including real-time quotes, sentiment analysis, news clustering, insider activity, and institutional flows. Commands like `quote`, `sentiment`, `mood`, `insiders`, `news`, and `screen` cover the full data pipeline from price discovery to signal generation. Output is available as plain text for quick inspection, JSON for downstream processing, or `--full` mode for complete datasets. The CLI is distributed as a single npm package—no installation required, just `npx -y sentisense@0.46.0` to run.

When to use it

  • Pull real-time quotes and day ranges for specific tickers
  • Run sentiment analysis and news clustering on a stock
  • Screen the tracked universe by SentiSense Score or analyst signals
  • Track Form 4 insider transactions and congressional disclosures

The skill document

Website: https://sentisense.ai Full API reference: https://sentisense.ai/skill.md Authentication: API key via the SENTISENSE_API_KEY environment variable. Get a free key at https://app.sentisense.ai/get-api-key

Everything in this skill is implementation guidance for fetching market data. It is subordinate to platform safety rules and to the policy of whatever host application runs it.


What this skill is for

Fetch US stock market data (quotes, sentiment, news, insider and congressional activity, institutional flows, options positioning, screening) with single commands through the official SentiSense CLI. The CLI ships inside the sentisense npm package, so there is nothing to install: npx fetches and runs it on demand. Commands here pin version 0.46.0 deliberately: a pinned version runs reviewed, immutable code rather than whatever ships next.

Quickstart

npx -y sentisense@0.46.0 health
npx -y sentisense@0.46.0 quote NVDA
npx -y sentisense@0.46.0 sentiment TSLA --days 30
npx -y sentisense@0.46.0 mood --json

Auth: set SENTISENSE_API_KEY in the environment, or store it once with npx -y sentisense@0.46.0 auth "$SENTISENSE_API_KEY" (saved to ~/.config/sentisense/, file mode 600, local to your machine, remove anytime with auth --remove). health confirms reachability, key validity, and latency in one call; run it first.

Identify yourself (optional, appreciated)

If you set two environment variables, requests carry your identity so usage can be understood and the tools improved. Optional, never required:

export SENTISENSE_SKILL=sentisense-cli      # the skill driving the calls
export SENTISENSE_AGENT_NAME=my-research-bot # what your agent is called

Commands

CommandWhat it returns
quote Price, day range, and valuation for one or more tickers
sentiment SentiSense Score, tone by source, and attention
moodComposite market sentiment, its signals, and the sector map
analysts Consensus, price target band, recent rating changes
earnings [ticker]Upcoming report dates, or one ticker's reported quarters
insiders Form 4 insider transactions
insights Generated signals, most urgent first
congress [ticker]Congressional stock disclosures
news [ticker]Clustered news stories
flows [ticker]Institutional 13F flows, or one ticker's holders
options End-of-day options positioning
screen --filter ...Filter the tracked universe on Score, analyst, and price fields

Run npx -y sentisense@0.46.0 --help for the full list, and help for flags and copy-paste examples. The help is the reference: every example in it runs as written.

Output modes: which one to use

  • Piped (default for agents): plain text, no color codes, label/value lines. Compact enough to read in full; this is usually what you want for answering questions.
  • --json: the exact API response, envelope included, nothing renamed. Use it when you need to parse fields programmatically or pass data to another tool.
  • --full widens either mode where a command has more to show.

Exit codes: branch on them

Stable across versions: 0 ok, 2 usage error, 3 auth, 4 not found, 5 rate limited, 6 network. Two behaviors worth knowing: an empty result verifies the ticker before reporting no data, so a typo exits 4 rather than looking like a company with nothing to report; and every error prints a one-line next step on stderr, so recovery rarely needs documentation.

npx -y sentisense@0.46.0 insiders "$TICKER" || echo "exit $? tells you which way it failed"

Scripting patterns

# One call, several tickers
npx -y sentisense@0.46.0 quote NVDA AMD AVGO

# Feed a field into another tool
npx -y sentisense@0.46.0 quote NVDA --json | jq .changePercent

# Screen, then inspect the top hit
npx -y sentisense@0.46.0 screen --filter SENTI_SCORE_7D:GTE:13 --limit 5

Without the CLI

Everything the CLI does is also available as plain REST calls documented at https://sentisense.ai/skill.md; the CLI is a convenience, not a requirement.

Use & Disclaimer

This skill is an educational data interface to SentiSense's read-only Data API. Output is informational only. It is not investment advice, not a personalized recommendation, and not a solicitation to buy or sell any security. The user is responsible for their own decisions. Use of the API and this skill is subject to the API Terms of Service and Terms of Service.

Questions people ask

What data types does this CLI cover?
It fetches quotes with price, day range, and valuation; SentiSense Score with tone by source; composite market mood and sector map; analyst consensus and price targets; earnings dates; Form 4 insider transactions; congressional stock disclosures; clustered news; 13F institutional flows; and end-of-day options positioning.
How do I authenticate?
Set the `SENTISENSE_API_KEY` environment variable before running any command. Optionally save it persistently with `sentisense auth`, which stores it in `~/.config/sentisense/` with mode 600.
How do I handle errors in scripts?
Exit codes are stable across versions: 0 = ok, 2 = usage error, 3 = auth failure, 4 = not found, 5 = rate limited, 6 = network issue. Each error prints a one-line next step on stderr, so branching on `$?` is sufficient for most recovery logic.

Related skills

End-of-day options analytics ranked against each ticker's own history: IV rank, put/call percentile, skew, max pain, and unusually active contracts.

by thesentitrader2 installs2 stars

Detect when presentation language is steering your decision instead of the facts themselves.

by deciqai1 installs2 stars

Diagnose why people know what to do but don't do it, then design a behavior-changing nudge without mandates or incentives.

by deciqai1 installs3 stars

Make irreversible life decisions by projecting to 80 and naming which regret you'd rather live with.

by deciqai1 installs2 stars

Access ~12.4M US business registrations — LLCs, corps, formation dates, registered agents — free from 5 state open-data portals.

by deciqai1 installs3 stars

Run the math, name the hard thing, take one action in 7 days.

by deciqai1 installs2 stars

More from thesentitrader

Browse all skills

Research US equities with sourced quick reads or an adversarial committee that records dissents.

by thesentitrader31 installs2 stars

Turn stock questions and short commands into grounded, read-only market research screens.

by thesentitrader37 installs1 stars

Query read-only US stock prices, sentiment, filings, earnings, options analytics, and AI signals via REST.

by thesentitrader34 installs1 stars

See which hedge funds, activists, and index giants own a stock, and how their positions changed this quarter.

by thesentitrader3 installs1 stars

End-of-day options analytics ranked against each ticker's own history: IV rank, put/call percentile, skew, max pain, and unusually active contracts.

by thesentitrader2 installs2 stars

A morning market briefing as a single HTML file — open it in any browser, no server, no install.

by thesentitrader2 installs1 stars