> ## 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.

# FAQ

> Frequently asked questions about SimpleFunctions, the CLI, APIs, MCP adapter, autopilot, and Polymarket support.

## What is SimpleFunctions?

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

## Is SimpleFunctions a broker?

No. SimpleFunctions is a software platform. Trading routes through Kalshi (CFTC-registered DCM) and Polymarket; SimpleFunctions never holds customer funds. See [Compliance](/enterprise/compliance).

## How do I get an API key?

```bash theme={null}
sf login
```

Or visit `simplefunctions.dev/dashboard/keys`. See [API keys](/enterprise/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 backing surface, different transport.

* **`sf agent`** is the primary local agent surface. It runs an LLM locally (or against OpenRouter) inside a TUI. Tools execute as subprocesses.
* **MCP** is the compatibility adapter for existing LLM clients (Claude Desktop, Cursor, etc.) over Server-Sent Events.

Choose `sf agent` when you want a self-contained TUI. Choose the HTTP APIs for remote services. Choose MCP only when you want SimpleFunctions tools inside an MCP-compatible 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 SimpleFunctions call my LLM?

Not directly. SimpleFunctions calls its own LLM gateway (OpenRouter). If you want SimpleFunctions inside your own LLM workflow, start with the CLI for local agents or the HTTP APIs for remote services. Use MCP only when your LLM client requires an MCP server.

## How do I run portfolio autopilot 24/7?

```bash theme={null}
sf portfolio enable
```

Walks you through encryption, schedule, execution mode, and strategies. The cloud tick 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?

```bash theme={null}
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` with reproduction steps and the output of `sf doctor`.

## See also

<CardGroup cols={2}>
  <Card title="Troubleshooting" href="/resources/troubleshooting">
    Concrete error fixes.
  </Card>

  <Card title="Compliance" href="/enterprise/compliance">
    Regulatory posture and disclaimers.
  </Card>
</CardGroup>
