MCP and API
Your close data, in your own tools, on your terms.
Orion's records join the same MCP server and REST API as every Ferrata product. A token your company creates can read the close status, reconciliations, the cash forecast and the overview, within the same roles and record scope as a person, and can be rotated or revoked at any time.
- Record scope
- All entities
- Created by
- Owner
- Last used
- Nov 6, 9:20 am
What a token can read
Scoped to what it needs, and no more.
- Close
- The period, its tasks and their status, by entity.
- Reconciliations
- Each account's status, differences and sign-offs.
- Cash
- Bank balances and the 13 weeks ahead.
- Overview
- The figures on the CFO overview, with their period's state.
Rules every token follows
The same rules as a person.
Read only
A token reads. It cannot sign, post or change anything.
Scoped
To the records and record scope you choose.
Rotatable
Rotated or revoked at any time, by your Owner.
Recorded
Every token and bot connection shown in your activity log.
Connecting a tool
Turn it on, create a token, connect.
- 01
Turn on
Your Owner turns on external access for the company.
- 02
Create
A token with the scopes it needs.
- 03
Connect
Your assistant or tool over MCP, or your own code over the API.
- 04
Review
The activity log shows what each token read.
What Orion works out, and what is yours
Orion does the arithmetic. People sign.
Tokens are checked on every request on their own. Creating, scoping and revoking them is your Owner's.
Orion matches, ties and calculates on its own, from the records already in your foundation. Every journal posted, every difference written off, every reconciliation signed off and every period locked is a person's decision, recorded with their name. Orion never moves money.
Orion works it out
- Checks every request against the token's scopes
- Applies the same roles and record scope as a person
- Records what each token read
Always a person
- Turning external access on
- Creating or revoking a token
- Choosing each token's scopes
FAQ
MCP and API access, run end to end.
Can an outside tool change anything in Orion?
No. Tokens are read only. Signing off, posting a journal and locking a period happen only in Orion, by a person.
Who can create a token?
Your company's Owner, once external access is turned on. Each token is scoped to what it may read and can be rotated or revoked at any time.
Does a token see more than a person would?
No. A token follows the same roles and record scope as a person, so it sees only the entities and records you allow.
Is it the same server as the other Ferrata products?
Yes. Orion's records join the same MCP server and API as Atlas, Apex and Cortex, under the same rules, so one connection reads across the products your company has.
Is access recorded?
Yes. Every token and every connected bot appears in your activity log with what it read and when.
Related in Orion
- Your data stays yoursYour ledger, bank lines and payroll in your company's own database, with an append-only record of every change.View
- Roles and sign-offThe same four roles as every Ferrata product, preparers and reviewers on every task, and a sign-off order you set.View
- One foundationOrion reads what Atlas, Apex and Cortex already hold, with your GL, bank and payroll, in your company's own database.View
- IntegrationsSAP, NetSuite, Dynamics 365 and Rillet, your bank's statement lines and your payroll, with Atlas, Apex and Cortex on the same foundation.View
See Orion work on your own close.
Bring last month's close: the checklist, the reconciliations and the trial balance. We run it through Orion beside your team and show you where it would have tied, and give you an honest answer if the close is slow for a reason upstream that you should fix first.
Your close calendar, chart of accounts, thresholds, reviewers and sign-off order are yours, and they stay yours. Orion is configured to the way your team closes. You are not handing over a playbook or fitting into a template.