# Use a workbook's formulas to compute a result

> Use a workbook's formulas to compute a result: 2 companies fully do it, 8 with a limit, 10 carry the tag. Every listing in Spreadsheets & operational tables with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/spreadsheets.calculate/
- Markdown: https://www.anchorterminal.com/niches/spreadsheets.calculate/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/spreadsheets.calculate/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/spreadsheets.calculate/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 8 | 10 | 7 | 2 |

## What counts as done

Inputs written and recalculated outputs read in the same session, with formulas evaluated by the product rather than stored as text, and the shared file left unchanged when asked.

How agents ask for it: run these inputs through our pricing model; what does the calculator give for these numbers; add a total column; recalculate the forecast

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Grist (Grist Labs Inc.)**: Python formulas are evaluated by Grist on write, and POST /docs/{id}/fork makes a personal copy to set inputs and read outputs without changing the original document.
- **Microsoft Excel (Microsoft Graph workbook API) (Microsoft Corporation)**: createSession with persistChanges false returns a non-persistent session, so inputs written and outputs read in that session use Excel's calculation and leave the file unchanged; /functions also exposes Excel functions directly.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Airtable (Formagrid Inc (doing business as Airtable))**: Formula fields are computed by Airtable, so writing input fields and reading the formula field works. There is no non-persistent mode, so inputs are saved to the shared base.
- **Baserow (Baserow B.V.)**: Formula fields are evaluated by Baserow, so writing inputs and reading the formula column works, but there is no non-persistent mode, so the inputs change the shared table.
- **Coda (Superhuman Docs) (Superhuman Platform Inc. (parent of Coda Project LLC))**: Coda evaluates formulas, and GET /docs/{id}/formulas reads named formula results after inputs are written to rows or controls. Inputs persist to the shared doc, and writes are queued with reads from a snapshot.
- **Google Sheets API (Google LLC)**: valueInputOption USER_ENTERED parses formulas so Sheets evaluates them (RAW stores them as text), and a read returns the computed values. Inputs are saved to the shared file; there is no non-persistent session.
- **NocoDB (NocoDB Inc (doing business as NocoDB))**: Formula fields are computed by NocoDB and returned on read after inputs are written, but inputs persist to the shared table; there is no non-persistent mode.
- **SeaTable (SeaTable GmbH)**: Formula columns are computed by SeaTable and read back after inputs are written, but inputs persist to the shared base; Create Snapshot exists but there is no non-persistent session.
- **Smartsheet API + MCP (Smartsheet Inc.)**: A cell's formula property is evaluated by Smartsheet and read back as the computed value, with errors in the response rather than the status code. Inputs persist to the shared sheet; no non-persistent mode exists.
- **Teable (Teable AI, Inc.)**: Formula fields are computed by Teable and read back after inputs are written, but inputs persist to the shared table; undo exists but no non-persistent session.

## What stops agents finishing

- formula written with RAW input stored as text
- calculation in a shared file collides with other users

## Around it

Before: spreadsheets.read-table. After: document-extraction.summarise, email.send.

## Where this comes from

Weight 7 of 100 in Spreadsheets & operational tables: 2 of 35 accounts (SharePoint calculation workbooks through Graph); thin, set by hand

As data: https://www.anchorterminal.com/api/v1/use-cases/spreadsheets.calculate.json, or the MCP tool get_use_case with id spreadsheets.calculate. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
