Tipalti
Connect AI agents and workflows to Tipalti: payees, bills, purchase orders and payment status, with notifications as payees and payments change.
Book a demoTipalti for AI agents and workflows.
engini lets your AI agents and workflows work in Tipalti, the accounts payable and global payments platform: invite and onboard payees, read their status, create bills and purchase orders, follow each payment from scheduled to paid, and start a workflow when Tipalti reports a payee change or a payment. Supplier invoices move from the inbox and the ERP into Tipalti, and payments come back to the books. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in Tipalti. Every tool is one you allow or leave out.
The Tipalti tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read suppliers and their onboarding and payability status.
Read invoices in Tipalti and where each one stands.
Follow a payment from scheduled to paid.
Read purchase orders for matching.
Write
Bring a supplier into Tipalti onboarding, or change their details.
Enter a supplier invoice, coded to the GL.
Add a purchase order for matching.
Any endpoint
Call any Tipalti API, with the key added for you.
Triggers
A payee finished onboarding or changed.
A payment was scheduled, sent or failed.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Tipalti. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Tipalti connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Tipalti tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Tipalti and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Tipalti tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Tipalti through engini
{
"mcpServers": {
"engini-tipalti": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Tipalti connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Tipalti tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Tipalti. Agents and workflows, across systems.
Invoices from the inbox to Tipalti
A supplier invoice from email is read by an agent and created as a Tipalti bill, coded and ready for Tipalti's payment flow.
Suppliers onboarded once
A new vendor in NetSuite or Coupa gets a Tipalti invitation, and its tax and bank details stay in Tipalti.
Payments in the books
Paid bills post back to NetSuite, Sage Intacct or QuickBooks with the payment date and amount.
Payables on request
An agent answers what is due, what was paid and which suppliers are blocked. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Tipalti and another system engini connects is available.
You decide what each agent may do in Tipalti. engini enforces it on every call.
Only the tools you allow
A toolset lists the Tipalti tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Tipalti account and engini acts as that person, with their Tipalti permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Tipalti in three steps. Then decide what each agent may do.
Sign in to Tipalti
In Tipalti, get the API key for your payer account, sandbox first, then add a Tipalti connection with the payer name and key.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Tipalti from Claude, ChatGPT, Cursor or your own code.
Tipalti and engini. Straight answers.
Can an AI agent write to Tipalti, or only read?
Both. engini has tools to invite and update payees and to create bills and purchase orders. Payments run under Tipalti's own payment controls. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Can an agent send payments through Tipalti?
engini creates bills and follows payment status. Paying runs in Tipalti under its own payment controls and the permissions you set there.
Does the agent act as me in Tipalti?
It acts as the Tipalti payer account behind the API key. Every run is recorded under the person who started it.
Can a change in Tipalti start work?
Yes. Tipalti notifies engini when payees change and when payment status changes. A trigger starts a workflow, and that workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Tipalti API endpoint through the same connection, and give it only to the agents that need it.