Avalara opens Versori agentic integration fabric to partners

Avalara announced Versori by Avalara is available through the Avalara Developer Portal — an agentic integration fabric that plans, connects, builds, and deploys production-grade connectors to Avalara tax and compliance systems.

TECH desk — a billing system or an online store does not send a sale to tax software until a connector, a software bridge, moves the data, and that bridge has been specialized engineering. Avalara says four agents can plan, connect, build, and deploy a production connector in days.

What the release says the old work costs. Businesses implement and change a complex mix of ERP systems, billing platforms, e-commerce applications, and custom technology. ERP, enterprise resource planning, is the software that runs orders and the books. The release prints the letters. Those changes, the release says, create significant budgetary and staffing burdens, and can delay critical business outcomes. They can require significant specialized engineering and create cost overruns, complexity, and delays as businesses grow and their technology stacks evolve. Significant, and can, are the release’s hedges. The page does not print a dollar figure, a headcount, or a week count for that engineering. These lines are the release’s.

What Versori is supposed to change, in the release’s next paragraph. With Versori by Avalara, integration time and expense are no longer sticking points for these projects. AI agents do the complex research, analysis, and coding in a fraction of the time and cost of traditional integration tools. Rather than relying on generic code generation or rigid pre-built templates, Versori by Avalara’s specialized AI agents execute the integration lifecycle. A fraction is the release’s comparison. It does not print the numerator or the denominator. No longer sticking points is the company’s claim.

The four agents, and only those four. Versori by Avalara uses four core AI agents to guide developers from initial mapping to certified release. Plan analyzes endpoint schemas, API contracts, and compliance requirements to scope integration architecture. A schema, here, is the shape of the data a system sends or expects. An API contract is the set of rules for how one system asks another for that data. An endpoint is the address that request hits. The release prints the names. Connect establishes secure authentication and automated system-to-system handshakes across ERPs, billing engines, e-commerce systems, and custom databases. A handshake, here, is the two systems proving who they are and agreeing to exchange data. Build generates production-ready transformation logic, mapping rules, and error-handling code. Customers and partners retain access to the generated connector code and business logic. Deploy runs automated testing, validates against Avalara certification benchmarks, and publishes the live connector. The release does not print those benchmarks. Certified release is the span the release names, from the first mapping to a connector it says is certified. These four jobs are the release’s.

The chief executive, as a quote, not as a stopwatch. Hugo Sarrazin, chief executive officer at Avalara, said businesses should not have to spend significant engineering time just to connect tax and compliance to the systems where they already work. He said Versori by Avalara changes that equation. He said specialized AI agents can research, build, test, and deploy production-grade connectors in days, giving developers and partners a dramatically faster path to bring Avalara into virtually any enterprise system. He said that for customers that means less integration work, faster time to value, and greater freedom to use the technology that works for their business. In days, dramatically faster, virtually any, and greater freedom are his words. His verbs are research, build, test, and deploy. The four agent names are Plan, Connect, Build, and Deploy.

Who can open it today, and what the about box says the company is. Developers and partners can access Versori by Avalara today through the Avalara Developer Portal. Users can explore API documentation and enroll in hands-on Versori by Avalara training. Today is the release’s tense. The text this desk read does not print a portal URL, a training date, a training price, or a media email. The about box calls Avalara the agentic AI leader in global tax and compliance. For more than two decades, it says, Avalara’s trusted tax content, deep compliance expertise, proprietary data, and technology have helped customers succeed on a global scale. Proprietary means the company says it owns that data. Avalara now pairs that foundation with agentic AI to help businesses execute complex compliance work while keeping people in control. Keeping people in control is the about box’s sentence about that pairing. Avalara processes more than 54 billion AvaTax API calls annually and supports millions of businesses worldwide. AvaTax is Avalara’s tax-calculation service. An API call is one request from another company’s software to that service. More than 54 billion is the about box’s annual figure. The site it names is Avalara.com. SOURCE Avalara, Inc. Is the wire’s last line.

What the card shows, and what the release does not. The card is the Versori by Avalara Plan Agent getting-started screen, a white card in an orange margin. It reads Get Started with the Plan Agent, and “Tell us what you want to build and we’ll help you plan it.” Four steps sit on the screen: Describe your integration, Review the plan, Configure systems, and Build & deploy. Describe your integration is the step marked current. A prompt on the screen reads “I want to integrate my billing system with Avalara for tax compliance.” Two controls read Try an example and Start planning. The Versori wordmark and a by AVALARA badge are on the card. Those lines are the screen’s. The 24 Sep release does not print them. The screen’s four steps are not the four agent names. Build & deploy is one step on the screen. Build and Deploy are two agents in the release. The card has no date text.

Plain English for the rest of the card. A connector is a software bridge that moves data between two systems. Agentic means the software can carry out multi-step work, not only answer a chat. An integration fabric, here, is the release’s name for the layer that plans, connects, builds, and deploys those bridges into Avalara tax and compliance. ERP is the system that runs orders and the books. A schema is the shape of the data. An API contract is the rules for asking for it. A handshake is the two systems agreeing to exchange data. Certification benchmarks are the checks the release says Deploy runs. The page does not print the checks. In days is the subhead’s clock and Sarrazin’s clock. A fraction of the time and cost is the body’s comparison, with no ratio printed. 09:45 ET is 9:45 a.m. Eastern and 1:45 p.m. UTC. More than two decades, and more than 54 billion AvaTax API calls, and millions of businesses, are the about box. CRUSH is Avalara’s customer and partner conference. The release calls it flagship and says Versori was showcased there. It does not print a day or a city for that showcase on this wire. This filing is the 24 Sep announcement.