Scienter is self-hosted software, not a hosted service you sign up for — there’s no account, no click-through agreement, and no vendor-operated production environment for the core product. This page describes the practical terms of running it rather than a SaaS contract, and is not a substitute for reading the repository’s actual license grants.

​
Licensing

The repository does not currently ship a single top-level LICENSE file. Individual packages declare their own terms in their own package.json — for example @scienter/sdk-execution and @scienter/alpha-ledger are marked MIT, while @scienter/mcp-server is marked UNLICENSED. Where a package doesn’t declare a license, don’t assume you have one. If you intend to redistribute, fork, or build a commercial product on this code, confirm the licensing terms directly with the repository maintainers first — this page does not grant rights the repository itself doesn’t.

​
Running the software

Scienter runs on your own infrastructure, using your own API keys where applicable (Helius, exchange data providers, LLM providers for the institutional council, SnapTrade for brokerage data, your own Telegram bot token). You are responsible for:
  • complying with the terms of service of every third-party API Scienter calls on your behalf;
  • securing any private keys you configure (Hyperliquid execution key, relayer key, SnapTrade credentials);
  • complying with the laws of your own jurisdiction regarding automated trading tools, if you enable execution.

​
The Enterprise Wallet API

If you issue and distribute gcx_-prefixed API keys to third parties (via python -m ghostcopy.tiers.enterprise issue), you are operating that access yourself — Scienter does not host or bill this for you. Standard terms worth setting explicitly if you do this commercially: keys are your responsibility to rotate and revoke, quota exhaustion returns 429 rather than degraded data (see Errors), and the underlying server has no TLS or public-internet hardening on its own — whatever you put in front of it is what actually enforces access control.

​
No warranty

As stated in full in Disclaimers: Scienter is provided “as is.” Scoped-signature execution, where you choose to deploy and use it, has not been independently audited and is not deployed to any network as of this writing.

​
Changes

This documentation describes the software as it exists in the repository at the time each page was last updated. Where documentation and code disagree, the code — and the repository’s own internal docs under docs/ and compliance/ — are authoritative.
Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.