Legacy systems, AI agents, and the automation problems nobody talks about.
A real MCP session, start to finish: initialize, tools/list, tools/call. What an AI agent sees when a website becomes a tool, and what stays hidden from it.
UiPath is the RPA market leader for desktop automation. For web portals it's brittle, slow, and expensive to maintain. Here's when each approach makes sense.
Browser automation is the standard approach to portal automation. It's also flagged by bot detection, breaks on DOM changes, and runs 10-20x slower than request-layer.
Computer use agents are compelling in demos. In production, they run at human speed, fail unpredictably on enterprise portals, and require full desktop environments to scale.
MCP lets AI agents discover and call tools. If your legacy portals can be exposed as MCP tools, your agents can actually do enterprise work — not just answer questions about it.
Guidewire's Integration Framework covers a fraction of what's in the UI. Here's how insurance teams automate claims status, document retrieval, and policy lookup without browser scripts.
Workday's public API covers HR data. It doesn't cover procurements, approvals, and the operational workflows your teams run every day. Here's how to automate those.
SAP's official integration paths require months of middleware work. Fiori communicates through OData over HTTP — the same requests the browser sends, directly accessible.
Integration Hub is a separate license. Table API setup takes weeks. ServiceNow's web interface calls the same APIs — and they're accessible with the right session credentials.
Regulatory portals almost never have APIs, are mandatory to use, and consume significant staff time for repetitive lookups. Request-layer automation is the only practical answer.
Agencies work with dozens of carrier portals. None have APIs. Here's how teams automate COI retrieval, policy status, and quote tracking across the carrier ecosystem.
Claims portals — Guidewire, Duck Creek, legacy home-grown systems — were built before APIs were a requirement. Here's how teams automate them without browser scripts.
Claims systems, carrier portals, state DOI databases, and policy admin platforms all require manual navigation. Here's how insurance teams are making them programmable.
Payer portals, prior auth platforms, credentialing databases, EHR operational workflows — none built for automation. Here's how healthcare operations teams are changing that.
Custodian portals, regulatory filing systems, clearing firm interfaces — the infrastructure of financial operations has no APIs. Here's how teams automate against them.
FMCSA, carrier portals, load boards, customs systems — logistics operations depend on portals that weren't built for automation. Here's how freight teams are changing that.
FDA submission portals, Veeva workflows, distributor portals, DEA CSOS — pharmaceutical operations run on systems with limited programmatic access. Here's how to automate them.
County assessor databases, MLS portals, title platforms, municipal permit systems — real estate data is fragmented across portals. Here's how to make them programmable.
OEM supplier portals, EDI gaps, quality document portals, environmental reporting systems — manufacturing operations run on portals that have no APIs for the workflows that matter.
Rippling's API covers basic HR and IT data. Onboarding sequences, device management, and app provisioning workflows are UI-driven with no API equivalent. Here's how to automate them.
SuiteScript requires NetSuite developers and admin access. Finance and ops teams need approval status, saved search results, and vendor data — without the development overhead.
ADP's API is limited to data exports. Payroll reconciliation, time and attendance, benefits enrollment tracking — the operational workflows HR teams run daily are portal-only.
Coupa's API handles POs and invoices. It doesn't handle approval queue monitoring, supplier compliance tracking, and spend analytics that procurement teams navigate manually.
Concur's API handles expense data exports. The approval workflows, policy exception monitoring, and department spend tracking that finance controllers need are UI-driven.
Epic's FHIR APIs cover clinical data exchange. Revenue cycle, denial management, prior auth tracking, and scheduling admin workflows require navigating Epic's Hyperspace manually.
Oracle Integration Cloud requires licensing and months of setup. Finance and ops teams need approval status, invoice matching, and supplier data without the middleware overhead.
Veeva's APIs cover document metadata and basic CRM records. Regulatory submission workflows, vault approval cycles, and field team operations require navigating the UI.
BambooHR's API covers employee records. Onboarding task management, approval workflows, performance review cycles, and compliance reporting require navigating the UI manually.
Power Automate requires premium licensing and runs in Microsoft's cloud. Approval queues, period close checklists, and on-premises Dynamics deployments are all left uncovered.
UKG's APIs have uneven coverage. Schedule exception management, overtime approval queues, and multi-location timecard compliance workflows are all managed through the UI.
Court filing portals, state bar databases, docket management systems, and regulatory agency portals — legal operations run on systems with no programmatic access. Here's how to change that.
FERC portals, ISO/RTO systems, interconnection queues, and state utility commission filing platforms — energy operations run on portals that were never designed for automation.
Permitting portals, lien databases, VMS platforms, subcontractor compliance systems — construction operations depend on systems built for inspectors and clerks, not software.
VMS portals, background check platforms, state unemployment systems, E-Verify, and payroll funding portals — staffing operations run on systems with no programmatic access.
Salesforce has extensive APIs — but approval processes, Experience Cloud portals, and custom Lightning apps still require navigating the UI. Here's how to automate them without Apex.
Procore's API covers project records. RFI workflows, submittal review cycles, and owner-hosted instances still require UI navigation — including when GCs have no API credentials.
Yardi's API coverage is limited and inconsistently available. Lease approvals, vendor payment status, and portfolio-level reporting require navigating the UI manually.
PeopleSoft's Integration Broker requires PeopleCode expertise. Heavily customized PeopleSoft breaks standard integration paths entirely. Here's how operations teams automate it.
Dayforce's API covers basic employee data. Payroll approval workflows, timesheet exception management, and multi-country compliance reporting require navigating the UI.
Blackbaud's SKY API covers donor records and gifts. Grant tracking workflows, major gift cultivation stages, and cross-database reporting between RE NXT and FE NXT require UI navigation.
Student information systems, NSLDS, federal grant portals, accreditation databases, and state reporting platforms — higher education operations run on systems with no programmatic access.
Grant management portals, foundation databases, state charity registration systems across 40+ states, and federal reporting platforms — nonprofit teams are doing too much manual portal work.
SAM.gov, state procurement portals, FEMA reimbursement systems, federal grant reporting — government operations run on legacy systems with no APIs. On-prem execution is the only option.
Retailer vendor portals, retail media platforms, marketplace seller dashboards, and chargebacks — retail operations depend on systems with inconsistent API access from the supplier side.