Skip to main content
This quickstart gives an agent or developer a working path in five minutes. The product order is CLI first, HTTP API second, SDK / Agent SDK third, and MCP last as a compatibility adapter.
  1. install the CLI
  2. run a public market query
  3. pull world state
  4. inspect one market
  5. discover the full command manifest

​
1. Install

Check that the binary is available:

​
2. Configure auth when you need account data

or set an API key:
Public market and world-state reads do not require an API key. Account, portfolio, thesis, intent, and exchange-related reads do.

​
3. Query prediction markets

The result should be one JSON document containing normalized Kalshi and Polymarket markets, implied probabilities, related contracts, source context, traditional-market anchors, and next actions. HTTP equivalent:

​
4. Read world state

Use the full snapshot at session start. Use deltas inside a long-running loop. HTTP equivalents:

​
5. Inspect a market

Returns market metadata, price, liquidity, indicators, regime state, related surfaces, and follow-up URLs. HTTP equivalent:

​
6. Pull account context

sf me returns a bounded boot context. Use sf feed, sf intent list, and sf portfolio ... when the agent needs a narrower user-scoped read.

​
7. Pull portfolio history

Portfolio reads are scoped to the authenticated user.

​
8. Discover tools before acting

Agents should use the manifest to see each command’s args, options, auth requirements, policy tags, side-effect level, and JSON support.

​
Minimal agent loop

If you want a surface-specific first run, use the CLI quickstart, API quickstart, SDK quickstart, or Agent SDK quickstart. Use MCP only when your client specifically requires MCP. If authenticated: