Ipnops: agents that run operations
The business tools already do the work; what is missing is something that makes them work together. Ipnops connects payments, accounting, commerce and mail, and acts across them with permission, never ownership, inside limits the owner sets.
The most valuable agents of the next few years will not be the ones that write the best paragraph. They will be the ones that close the loop: take the payment, post the entry, answer the customer, chase the invoice, and say what they did. Most businesses already own every system needed for that work. What they lack is something that moves between those systems with permission, inside limits, and leaves a record.
Ipnops is that something. It runs payments, accounting, commerce and mail through agents that act inside limits the owner sets.
The work sits between the tools
Money, books, orders and mail live in separate systems that do not talk to each other. Someone copies data from one to the next by hand. A chat assistant can discuss the business, but it cannot process a payment or send an order. Linking the systems properly is a development project most businesses cannot staff.
That is where agent projects stall. Gartner expects over 40% of agentic AI projects to be cancelled by the end of 2027, citing escalating costs, unclear business value and inadequate risk controls. An agent that only talks has unclear value. An agent that acts without limits is a risk control failure. The useful position is in between: an agent that acts, within bounds a person set, across the tools the business already uses.
Permission, never ownership
Ipnops is granted permission to act in a business's accounts. It never takes ownership of them. You connect the accounts you already use, payments, books, shop and email, and Ipnops acts across them. Permissions can be withdrawn in one click.
The distinction matters to any executive who has been asked to migrate to a new platform. Nothing moves. The ledger stays in the accounting system, the orders stay in the shop, the mail stays on the business's own domain. Ipnops is the hands, not the filing cabinet. The connections listed include Stripe, PayPal, Square, Adyen, Xero, QuickBooks, NetSuite, Shopify, WooCommerce, Amazon, Google Workspace, Microsoft 365, Slack, WhatsApp Business and Praecise Inbox, and changing one connection does not break what is already set up.
Say the outcome, not the wiring
Ipnops is instructed in plain language. You describe the result you want, for example chasing every invoice more than fourteen days late, twice, and then telling you. There is no flow to draw and nothing to configure. A customer, a team member or a schedule triggers a task; Ipnops works out what needs to happen, checks that it is allowed, performs the action and logs each step.
Workflows run on a schedule or when an event occurs. They continue after the browser is closed, survive restarts and stop at a budget you set. A builder lets a team describe what should happen, change it by instruction and publish it for colleagues or customers.
Limits a person sets, a record a person can read
The broader market is converging on the same principle: an agent that spends must be able to prove a person authorised it. Google's Agent Payments Protocol, announced in September 2025, is built on signed mandates for exactly that reason.
Ipnops applies the principle at the level of the business. The owner sets spending limits, counterparties, frequency and which actions need approval. Anything outside the limits stops and asks. Every action is recorded in order: who requested it, what changed and what it cost. When the board or an auditor asks what the agents did last quarter, the answer is a record, not a reconstruction.
What works today, and what is coming
Ipnops is honest about where each capability stands, and so is this article. Its site lists nineteen jobs across six areas and marks each as working today or coming soon. Eleven work today with nothing but an account: customer answers that cite their sources and admit when they do not know, email that reads the inbox, answers simple messages and drafts the rest for review, AI visibility checks across nine assistants, and durable workflows and the builder.
The payments job, which reports what came in and issues refunds inside a limit, is marked coming soon, and the selling jobs for shops, orders and listings are not yet working. They open as each connection opens. Executives should plan on that sequence: answers, mail and workflows now, money and commerce as they arrive.
Who it is for
Ipnops is built for three sizes of organisation. Individuals use a few connections and let work run overnight. Businesses join the tools they already have, with limits that match how they operate. Enterprises run the same engine inside their own walls, with data kept where their rules require and every action recorded for audit.
Agencies and software companies can also offer Ipnops under their own name, brand, domain and pricing, with one account holding many clients, each kept separate. It is free to start, with nothing to install.
How it connects
Ipnops is the work layer of the Praecise suite, the part that turns agents into operations. It sends mail from the business's own domain and can create mailboxes through Praecise Inbox, so every message an agent sends is attributable and searchable. Agents that need to move money across borders or settle in stablecoins can use Skerry, where Bridge and Stripe perform the regulated acts under their own licences.
Underneath, agents and their backends run on Praecise Cloud, on machines Praecise owns and operates with Praecise Metal and Praecise Furcate. One Praecise account opens all of it.
Operations that report back
The promise of agents for a business is not conversation. It is work done, within limits, with a record. Ipnops makes the tools a business already pays for work together, and tells the owner what it did. Read more on the Ipnops page.
