FAQ
Short answers to common questions about Felspar.
Is Felspar an agent?
No. Felspar doesn’t run agents, call tools or write content. Your agents gather evidence and act; Felspar decides from your approved policy and proves what it decided.
Does Felspar use AI to make decisions?
It uses a model for one narrow step: reading a text excerpt and saying which of your policy’s defined answers it matches, above a confidence threshold. The decision itself (applying your rules) is plain code. The same evidence and the same release always give the same decision, and replaying a decision calls no model.
What happens when the evidence isn’t good enough?
The question stays open and the result says so: which question, why, where your policy says to look, and whether to retry or escalate. Felspar never guesses.
Why must agents send exact quotes and not labels?
A label is the agent’s judgment. Felspar’s job is to apply the company’s judgment, so it needs what the source actually said. Exact quotes also make every decision checkable: a reviewer can see the words behind each answer.
Can an assistant approve a pack for me?
No. Approving and releasing are your own click on the Felspar web app. No MCP tool, assistant or agent key can do either.
What happens to agents when I release a new version?
Agents following the job on Latest use it on their next call. Agents pinned to an earlier release stay where they are until you move them.
What happens when someone edits the policy Doc?
Felspar notices within about 5 minutes and marks the source changed. Agents keep using the approved release. A person decides whether the edit needs a new release. See Source changes.
Can I see what a change would do before releasing it?
Yes. A backtest re-decides your recent real cases under the proposal and lists which would change, and which agents would get the release.
Which documents can I connect?
Google Docs. Notion pages are in beta. Each person connects their own account; Felspar sees only the documents people pick.
Which assistants and agent frameworks work?
For authoring: ChatGPT and Claude, with the Felspar plugin or as a custom connector. For agents: any MCP client, any HTTP client, and ready adapters for Eve, the Claude Agent SDK and the OpenAI Agents SDK. See Integrations.
Is there a TypeScript SDK?
Yes: @felspar/sdk on npm, under Apache-2.0. It connects an Eve agent in two lines, includes a typed REST client, the pre-action gate with adapters for Eve, the Claude Agent SDK and the OpenAI Agents SDK, and the Felspar agent skill (npx @felspar/sdk skill). The modules under draft/ may change between minor versions until 1.0. The REST API works from any language.
How long is my data kept?
Decisions and their evidence: 30 days. Released packs: as long as they serve, then 90 days. Unreleased drafts: 30 days. See Security, privacy and data.
Does a receipt prove we’re compliant?
No. A receipt proves Felspar made a decision from given evidence under a given release. It isn’t legal approval, certification, or proof the evidence was true.
Can Felspar govern an agent that doesn’t call it?
No. Felspar only governs agents and tools that ask it. Use the pre-action gate so tools that act can’t run without a verified decision.
How do I get access?
Sign in at app.felspar.ai. Felspar is invitation-only for now; if you have no workspace, the sign-in page offers a request-access form. You can also write to hello@felspar.ai.
Is there a Slack app?
Not yet. See Slack.