Agent-native

Sage Intacct AI Gateway

Sage's official MCP server and REST API layer that lets outside AI tools read Sage Intacct data under its roles and permissions, with the MCP held to read-only.

sage.com/en-us/sage-business-cloud/intacct/product-capabilities/platform/ai-gateway · founded 2025-11 (announced 2025-11-04 at Sage Future for Partners, Barcelona) · Sage Group: Newcastle upon Tyne, UK; Sage Intacct: San Jose, California · researched 2026-10-10

Scope: A governed endpoint that gives external AI clients (Claude, other MCP clients, custom agents, Amazon Bedrock apps) real-time read access to Intacct's GL, AP, AR, cash management, purchasing and order entry through MCP, beside full read and write through the REST API for applications built to use it. It is separate from Sage Copilot, the AI inside Intacct, and does not move data out of Intacct or keep any record of its own.
Backing: The Sage Group plc (London Stock Exchange). FY25 (to 2025-09-30): ARR GBP 2,574m, up 11%; underlying revenue GBP 2,513m, up 10%. Sage acquired Intacct in 2017 for $850m.
Serves: mid-market, enterprise, accountants
Covers: ledger, invoicing, spend, close, reporting, integration
To ownpurse: Design cousin. An incumbent that chose read-only for agents by policy and kept writes on a separate, governed REST path. That is half of ownpurse's stance (agents read freely); ownpurse adds the other half, a sealed package a person approves before anything is written, and a record the owner holds. Intacct is also a likely future source.

What it is

The Sage Intacct AI Gateway is Sage’s sanctioned door for outside AI tools into Intacct, its cloud financials product for mid-market companies. Sage announced it on 4 November 2025 at Sage Future for Partners as the first phase of “AI Developer Solutions”: an MCP server built on Intacct’s REST API, developed with AWS (Amazon Bedrock and AgentCore). Sage’s product page calls it a governed, auditable endpoint where role-based permissions decide what AI applications can see and do. It is separate from Sage Copilot, the assistant built into Intacct.

How it works

The gateway has two halves. The MCP server gives real-time, read-only access to the general ledger, payables, receivables, cash management, purchasing and order entry. Beside it, the REST API “can support full access for applications designed and governed to use them” (Blytheco). Partners quoting Sage are plain about the policy: “read access only, governed by Sage Intacct roles and permissions”. An AI application cannot post transactions, alter records or change balances (Baker Tilly, September 2026). CBIZ said in July 2026 that it was available to all customers and partners.

Setup is not one click. An administrator enables the gateway and scopes a user and role, and Intacct is not in Anthropic’s connector directory (Audit Friendly).

Data and access

Sage now recommends REST and ships new objects only there (developer.intacct.com). The older XML Web Services need a developer licence and sender id arranged through an account manager, and concurrency is capped per company with queued requests (Web Services). Partners report project accounting and fixed assets still lean on XML, so coverage there is thinner. Data stays in Sage’s cloud; bulk extracts go through the Data Delivery Service. Pricing is negotiated; third-party estimates of $9,000 to $75,000 a year disagree widely. CBIZ reports Finance AI at no cost to customers through May 2027.

Agents

This is an incumbent choosing read-only for agents on purpose. The upside is clear: a finance team can let Claude or ChatGPT answer questions over live books without fearing a stray posting. Baker Tilly names what read-only does not fix: data reaching an unvetted AI provider, retention of prompts, misread answers, roles that grant too much, and output mistaken for audit evidence. There is no approval step because there is nothing to approve over MCP; writes go to custom REST applications governed only by their credentials.

Customers

Intacct reviews average 4.3 out of 5 on G2 (about 4,000 reviews) and Capterra (606 to 684 reviews in 2026). Users praise multi-entity consolidation and dimensional reporting; they complain about cost, the learning curve and support. In its FY25 results, Sage reported annual recurring revenue of £2,574m, up 11%, and named Intacct as a driver of 12% North America growth. Sage does not publish an Intacct customer count.

History

Intacct was founded in 1999 in San Jose and bought by Sage in 2017 for $850m (Wikipedia). The REST API reached general availability in 2025, the gateway followed that November, and Sage has said it will bring certified third-party agents into Copilot.

For ownpurse

Intacct is a design cousin and a likely future source. Sage reached the same first rule as ownpurse: agents read freely. It stopped there, so an agent can describe a problem but cannot propose the journal that fixes it, and every write goes through a bespoke integration with no review step. ownpurse fills that gap. Agents draft a sealed package, a person approves it, and both the reads and the attempt are kept in a record on the owner’s machine. The read-only stance also tells you what finance teams in the mid-market will accept: start from the line “it cannot change your books” and earn trust from there.

Data and access

Public API: Yes. REST (recommended; new objects ship only on REST), legacy XML Web Services, and MCP via the AI Gateway
Auth: Web Services sender id and password authorised per company for the XML API; access for AI clients runs through a Sage Intacct user and role. OAuth details for the MCP not confirmed.
Limits: Concurrent gateway connections limited per company id, excess requests queued first in, first out; Sage's example: of 100 concurrent requests about 5 run while the rest wait about 5 seconds. Guidance: queries under 1,000 records per page, under 100 records per write; 15-minute timeout on large requests.
What access costs: Web Services licence priced through the account manager (not published). CBIZ reports Finance AI available to all customers at no cost through May 2027; whether that covers the gateway is not confirmed.
Export: REST and XML query APIs, saved reports, and the Data Delivery Service for bulk extracts.
Notes: Partners report project accounting and fixed assets still lean on the XML API, so agent coverage there is thinner.

Price

Model: Annual subscription, negotiated per module and user through Sage or a partner; prices not published.
Entry: Third-party estimates put entry at about $9,000-12,000 a year for one user and core financials (2026; not from Sage).
Top: Reseller and buyer-platform estimates of $25,000-75,000 a year for typical mid-market deployments, plus $10,000-200,000 implementation (2026; not from Sage).
Notes: All Intacct price figures come from resellers and aggregators that disagree widely; treat as rough.

Agents

MCP: official
AI features: AI Gateway (MCP plus REST) for outside agents; Sage Copilot inside Intacct for invoice processing, natural-language questions, close task tracking and anomaly flags; a Sage and AWS programme on Amazon Bedrock and AgentCore; plans to bring certified third-party agents into Copilot.
Agent writes: Not through MCP: partners quoting Sage say it gives read access only, governed by Intacct roles and permissions. Writes are possible through the REST API for applications designed and governed to use it.
Approval: No approval gate; the control is policy and permissions. The MCP is read-only, and anything an application writes through REST is limited only by the role behind its credentials.
Notes: Baker Tilly warns that the connection is only as narrow as the identity behind it, that read-only access does nothing about data leaving for an unvetted AI provider, and that AI output is not audit evidence.

Integration and customers

Connects to: AI clients: Claude and other MCP clients, custom agents on any LLM via REST, Amazon Bedrock apps. Intacct itself has a large marketplace of partner integrations (count not confirmed). Third parties such as CData also sell read-only Intacct MCP connectors.
Notes: Setup is partner-led: an administrator enables the gateway and scopes a user and role before an agent can connect.
Scale: Sage cites Intacct as a main driver of 12% North America revenue growth in FY25; cloud-native revenue GBP 885m, up 23%. No Intacct customer count published.
Ratings: G2 4.3/5 from about 4,075-4,096 reviews; Capterra 4.3/5 from 606 (March 2026) to 684 (May 2026) reviews.
What customers say: Reviewers praise automation, multi-entity consolidation and dimensional reporting; they complain about cost, a learning curve, a dated interface and hard-to-reach support. No independent reviews of the AI Gateway yet.

Timeline

1999
Intacct founded in San Jose as one of the first cloud accounting applications
2017-07
Sage Group acquires Intacct for $850m
2025
Intacct REST API generally available (2025 Release 1)
2025-11-04
Sage launches AI Developer Solutions at Sage Future for Partners; the Intacct AI Gateway, an MCP server on the REST API, is the first phase, with AWS Bedrock and AgentCore
2025-11-19
Sage FY25 results: ARR GBP 2,574m, up 11%, with Intacct named as a growth driver
2026-07-09
CBIZ: gateway available to all customers and partners; MCP read-only across AP, AR, GL, cash, purchasing and order entry
2026-09-01
Baker Tilly guidance for finance leaders on the read-only MCP and its risks

Borrow and avoid

Borrow: State the agent policy in one plain sentence (MCP reads, REST writes) and enforce it in the product rather than in prompts; scope agent access to an existing role so permissions are the ones finance already audits; publish the coverage boundary by module.
Avoid: Read-only as the whole answer, which leaves agents unable to propose anything and pushes writes to bespoke integrations with no review step; licence and partner gating that make a sanctioned agent connection slower to set up than an unofficial one.

Sources

Not confirmed against a primary source

Sage's own wording of the read-only policy: sage.com and developer.sage.com returned 403 to direct fetches, so the read-only claim rests on partners quoting Sage (Baker Tilly, CBIZ, Blytheco) and search summaries of the product page
Authentication method for the MCP server (OAuth or a Web Services user)
Exact general availability date of the MCP server (announced for November 2025; 'available to all customers' by July 2026)
Whether the gateway or MCP carries any charge, and whether the 'no cost through May 2027' offer covers it
MCP tool list and object coverage
Claim that project accounting and fixed assets rely on the XML API (single secondary source)
Intacct customer count and marketplace integration count
All Intacct price figures (resellers and aggregators only)

On the spectrum

0 to 4. The grey tick is ownpurse.

Custody: 1
Where it runs: 0
History: 1
Openness: 1
Breadth: 2
Autonomy: 1
Agent-ready: 3
Easy to connect: 2
Market: 3

See it on the map

Also in agent-native

ownpurse is not affiliated with Sage Intacct AI Gateway or any company named here. Names are their owners' trademarks. Figures come from the company's own pages and the press, as linked, as of 2026-10-10; scores are our reading of them against the definitions in the landscape. This is not legal or financial advice.