Arcvue
Integrations & interoperability
Arcvue connects to the systems you run, and your data is always yours to take.
Your bank, cards, bill pay and payroll, the ERP you run today, federal data sources, and the AI provider you choose. Everything Arcvue holds for you can be read through an open API or exported whole.
| Area | Systems | What comes across |
|---|---|---|
| Banking | Plaid, Mercury | Accounts, balances and transactions |
| Corporate cards | Ramp | Card transactions and how each was coded |
| Bill pay | BILL (Bill.com), Ramp | Vendor bills and payments |
| Payroll and HR | Insperity; Remote People for staff in locations Insperity does not serve | Payroll, employees and leave |
| Benefits | Unum | Premium statements, by covered employee |
| E-signature | SignWell | Contracts out for signature, and the executed copy back |
| The ERP you run today | UNANET, Deltek Costpoint, Sage Intacct, JAMIS, Microsoft Dynamics 365 / GovCon365, Intuit QuickBooks Online; QuickBooks Desktop and PROCAS by file | Your ledger history, contracts, projects, invoices and labor |
| CRM and pipeline | Salesforce, UNANET CRM, Microsoft Dynamics 365 | Opportunities and pipeline |
| Federal sources | SAM.gov, FPDS, USAspending.gov, GSA CALC+ | Opportunities, awards, wage determinations and labor-rate benchmarks |
| Tax filing | IRS IRIS | 1099 information returns, filed electronically |
| Microsoft 365 | Reports and alerts, sent from your own mailbox | |
| AI models | Anthropic, Google, OpenAI, Azure OpenAI | The provider you choose, on your own API key |
The complete list, with exactly what each connection receives, is our Sub-Processor Register.
Every connection is one you authorize, on your own account.
You connect each system with your own account at that provider, or at your bank. Credentials are held in a dedicated secrets vault, never in a database, and are never shared between customers.
Everything a connection brings in keeps a record of where it came from. Open an entry in your books and the bank line, bill or payroll run behind it opens with it.
Arcvue’s AI runs on the provider you choose.
Choose Anthropic (Claude), Google (Gemini), OpenAI, or Azure OpenAI, and enter your own API key in Admin. You hold the account and the bill, and Admin shows you what Arcvue uses.
It works the other way too. Connect Arcvue to your own Claude account as a connector, sign in once, and work your opportunity screening queue from the assistant you already have open.
Arcvue is not tied to any one AI company. The provider is a setting, not a dependency.
Your data is never locked in.
Your history comes in from the ERP you run today. While you are a customer, the API reads anything Arcvue holds for you. If you leave, we hand over a complete export of your data, as a SQLite database or CSV, within thirty days of your request—open formats any analyst can read with free tools.
We are committed to interoperability and portability. Arcvue fits the back office you already run, and you can leave with everything you put in.
The API is open, documented, and held to the same controls as the product.
The Arcvue Public API is REST over HTTPS, with a published OpenAPI reference. It reads accounting, FP&A, pipeline and opportunity data, and sends webhooks when something changes.
Every key is scoped and denied by default, reads only its own company’s data, and logs each read before any data is returned. Anything written through the API arrives as a proposal a person confirms. Nothing posts to your ledger on its own.
Build a direct integration with Arcvue.
If your product serves government contractors and you want a direct API integration, write to info@arcvue.ai. Tell us what your product does, which data it needs, and which way it moves.
Product and company names on this page are trademarks of their respective owners. Arcvue uses them only to identify the systems it connects to; their use implies no endorsement by, or partnership with, any of those companies.