Overview

Every way to connect to Felspar - for people who author policy and for agents that use it - and which to choose.

Felspar has one decision service with several thin front doors. Every surface uses the same access checks, the same releases and the same receipts; none of them holds its own copy of your policy.

For people who author policy

People sign in with their own Felspar login. From an assistant, that sign-in can never approve or release.

For agents and automations

Every agent needs a key from Register an agent.

Choosing between MCP and REST

• MCP suits agents whose model decides when to call Felspar. The four agent tools carry their own descriptions and request format, so the model learns the method from them, and list_jobs lets one agent pick between several jobs.
• REST suits code that runs a fixed sequence: get the brief, gather evidence, ask for the decision, verify the receipt, act.
• Many agents use both: MCP for the model’s decision calls, REST for the receipt check in the code that acts.

The method every agent follows

Whatever the surface:

1. Pick the job (with list_jobs if none is named) and get its requirements once.
2. For each question, look where the requirements say, and copy the shortest exact passage that answers it.
3. Ask for the decision with all the evidence in one request.
4. Report the outcome and its next step exactly. If not decided, follow retry or escalate. When the result carries an escalation, hand off by its id.
5. Before acting, verify the receipt.

The agent never decides, labels or guesses the outcome itself.