Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.simplefunctions.dev/llms.txt

Use this file to discover all available pages before exploring further.

​
What is SimpleFunctions?

A software platform that turns prediction markets into structured state for agents, trading desks, and research workflows. CLI, public APIs, MCP server, web terminal, and a Mac panel — all on the same backing data.

​
Is SimpleFunctions a broker?

No. SF is a software platform. Trading routes through Kalshi (CFTC-registered DCM) and Polymarket; SF never holds customer funds. See Compliance.

​
How do I get an API key?

sf login
Or visit simplefunctions.dev/dashboard/keys. See API keys.

​
Can I use the CLI without trading?

Yes. The CLI works without any exchange credentials. You only need Kalshi/Polymarket keys to trade. Read APIs, theses, watchlist, and alerts all work without exchange auth.

​
What’s the difference between sf agent and the MCP server?

Same tools, different transport.
  • sf agent runs an LLM locally (or against OpenRouter) inside a TUI. Tools execute as subprocesses.
  • MCP exposes the same tools to your existing LLM client (Claude Desktop, Cursor, etc.) over Server-Sent Events.
Choose sf agent when you want a self-contained TUI. Choose MCP when you want SF tools inside your existing chat UI.

​
Do you support Polymarket?

Yes — read APIs return both Kalshi and Polymarket. Trading via Polymarket requires a wallet connection (web terminal) or wallet credentials in the CLI.

​
What models does the agent use?

Default: anthropic/claude-sonnet-4.6 via OpenRouter. Override with --model <slug> or defaultModel in your CLI config. Portfolio autopilot defaults to the same.

​
Can SF call my LLM?

Not directly. SF calls its own LLM gateway (OpenRouter). If you want SF tools inside your LLM, use MCP — your LLM client connects to the SF MCP server.

​
How do I run portfolio autopilot 24/7?

sf portfolio enable
Walks you through encryption, schedule, execution mode, and strategies. The Trigger.dev runner picks up your schedule and runs ticks server-side. You don’t need a long-running local process.

​
Where do I see my portfolio history?

sf portfolio status
sf portfolio history --json --ticks 20
Or visit app.simplefunctions.dev/dashboard/portfolio for the visual surface.

​
Can I export my data?

Email patrick@simplefunctions.dev. Self-serve export is on the roadmap.

​
How do I report a bug?

Email patrick@simplefunctions.dev or open an issue on the public CLI repo at github.com/simplefunctions/cli.

​
See also

Troubleshooting

Concrete error fixes.

Compliance

Regulatory posture and disclaimers.