APIs or browsers for AI agents

An original English research case on choosing an execution route for recurring business workflows.

Choose a route for the business operation it must complete, then specify what proves completion and how an uncertain result can be recovered. Supported APIs, deterministic DOM automation, and visual model interaction expose different contracts and operating work. New API coverage can remove a gap without making migration economical.

Material	What it contains
Research brief	Question, intended reader, scope and outline.
Initial draft	The complete original English first draft.
Final report	The revised article, including the conditional migration recommendation.
Sources and reading notes	Eleven primary English sources, relevant reading scopes and limits.
Claims	Facts, interpretations, design judgments and counterexamples.
Reviews and revision	Both complete reviews, the original negative verdict and the accepted correction.
Provenance	Article and response hashes and the limits of the record.

Written in English from primary English documentation read on 10 October 2026. The support-ticket workflow is hypothetical and the cost model is unmeasured; no production deployment or comparative performance experiment was conducted. This is a use case, not a with/without-toolkit evaluation.

Historical Chinese office-agent case · Its English translation