Skip to content

An API under the same rules. A key is an agent.

A request made with an API key or through the MCP server is treated as an agent’s request. The same rules apply, and it can’t approve a draft.

In early access today. The AI model isn’t switched on yet. Field updates come from built-in rules, which pick up only sentences that state a value outright. What works today

What’s there. Two ways in, one set of rules.

A REST API
The REST API lists a workspace’s objects, reads and writes records, runs the agent’s tools, and reads the ledger of changes, with undo and redo.
An MCP server
The MCP server is one address that speaks Streamable HTTP. It offers the agent’s tools and five of its own: list objects, list records, get a record, list changes and undo a change.
Keys you can narrow
Owners and admins create keys in Settings → API keys. A key is shown once and stored as a hash. It acts as the member who created it, narrowed to its scope.
A limit you can read
Every response says what the key’s limit is and how much of it is left this minute. A request over the limit is refused with the number of seconds to wait.
Every write on the record
A change made through the API or the MCP server is recorded in the ledger with its source, and can be undone like any other change.
No approval from outside
A tool that needs a person’s confirmation is not applied when it is called with a key. The call returns what was proposed, and a person confirms it in Fonsent.

Three calls. Each one only reads.

Create a key in Settings → API keys. A read-only key is enough for these. To keep it out of your shell history, run read -s FONSENT_KEY, paste the key and press Enter.

  1. List the objects

    What the workspace holds: each object with its fields and relationships.

    curl -H "Authorization: Bearer $FONSENT_KEY" \
      https://app.fonsent.com/api/v1/objects
  2. Read records

    Records of one object, up to the limit you give. The object’s name comes from the first call.

    curl -H "Authorization: Bearer $FONSENT_KEY" \
      "https://app.fonsent.com/api/v1/records/opportunities?limit=5"
  3. Read the ledger

    The latest changes, newest first, whoever or whatever made them.

    curl -H "Authorization: Bearer $FONSENT_KEY" \
      "https://app.fonsent.com/api/v1/actions?limit=10"

Enforced

A key is an agent.

Fonsent reads freely and makes small, reversible changes on its own, each recorded with an Undo. Deleting, merging, bulk stage changes and new automations are drafted for a person. Email is always a draft.

Approve a draft
Never. Only a person can.
Send email
A draft, always. It waits in For review.
Delete, merge, bulk stage changes, new automations
Proposed, for a person to confirm in Fonsent.
Small, reversible changes
Made with an editor key, recorded, and undoable.
A read-only key
Reads, and nothing else.

Not here yet

  • There is no SDK, no command-line tool and no published API reference yet.
  • The three calls on this page were written from the app’s code and were not run against production before this page went out.
  • Until there is a reference, start from the three calls above and from the list of tools the API returns.

Questions

Can a key approve a draft?

No. A request made with an API key or through the MCP server is treated as an agent’s request, and an agent can’t approve a draft.

Who can create a key?

Owners and admins, in Settings → API keys. A key is shown once.

What happens when a key goes over its limit?

The request is refused with the number of seconds to wait. Each key is limited to 120 requests a minute.

Can I undo a change made through the API?

Yes. It is recorded in the ledger with its source, and can be undone like any other change.

Start with your own records.

Create an account, import a CSV or a few emails, and read the first proposals with their quotes. An import is one change you can undo.

Early access. No payment details are asked for.