Cornerstones Help

CLI Guide

Command flow, local setup, and result-contract rules.

Copy this to your agent Help first 
python -m pip install cornerstones-client
cornerstones-client --help
cornerstones-client guide
CLI Guide Public-safe onboarding

Cornerstones Help

The public-safe cornerstones-client discovery path is:

  1. python -m pip install cornerstones-client
  2. cornerstones-client --help

Copy those two lines into the agent. The agent can then choose guide, changelog, auth, trial, or verify from the help output instead of following a long manual checklist.

Use those entrypoints before drilling into deeper implementation or operator materials.

Command surface

cornerstones-client auth set-base-url --base-url https://your-cornerstones-portal
cornerstones-client auth set-api-base-url --api-base-url https://your-cornerstones-api
cornerstones-client trial start
cornerstones-client trial token
cornerstones-client guide
cornerstones-client changelog
cornerstones-client auth login --api-key <issued-api-key>
cornerstones-client verify
cornerstones-client auth status

The client stores local state in the user config directory as cornerstones-client/config.json, including portal URL, API URL, API key, trial cookie, and trial token.

Result-contract rules

When you consume CLI or API output, always inspect:

  • provenance
  • degraded
  • fallback
  • not_implemented

Do not assume every surface is fully live. Some responses stay intentionally explicit about scope or availability.

First install

python -m pip install cornerstones-client
cornerstones-client --help

Managed workflow shape behind the thin client

The current public client focuses on onboarding, discovery, and auth verification. The broader managed workflow it points you toward still looks like:

  • candidate generation first, not a full-market export
  • use bounded stocks universe presets when you want a reusable starting set
  • run stocks optionability as an authenticated optionability check before options work
  • treat earnings, filings, and corporate actions as event-risk workflow inputs

Those remain managed product surfaces even though the public package intentionally stays thinner than the full runtime command plane today.

Stocks surfaces

  • stocks screener and bounded stocks universe presets are authenticated candidate-generation inputs.
  • stocks optionability is a bounded authenticated eligibility read. Use it as an explicit optionability check before options work. Treat optionable=null plus degraded or fallback as explicit uncertainty, not a silent guess.
  • Treat stocks earnings, stocks filings, and stocks corporate-actions as event-risk workflow inputs anchored in the underlying corporate record.

Onboarding truth

  • auth set-base-url persists the portal URL in local client config.
  • auth set-api-base-url persists the API URL in local client config.
  • auth login stores an issued API key in local client config.
  • help discovery is the public-safe first step.
  • guide and changelog automatically request a short-lived discovery token if no full API key is present yet.
  • verify is intentionally stricter and still requires a real issued API key.
  • This is not a browser sign-in, hosted account session, or account-management UI.

Current package truth

  • Pro means broader authenticated read and context coverage.
  • Max means narrower premium-depth slices.
  • cornerstones-client is live on PyPI and intentionally thinner than the full managed service surface.
  • The full service CLI still uses cornerstones ... commands such as cornerstones context fx --symbol EURUSD; the thin public client focuses on help-led discovery, portal/API config, trials, and verification.
  • Hosted Google/GitHub sign-in, dashboard access, and billing checkout are live on the managed portal, even though the thin client remains the default public-safe onboarding path.
  • Website price and quota labels are configurable through public plan environment variables, so packaging can change without code edits.