The framing as a default choice, rather than a permanent one, is what makes this convincing. Reusing existing views, PL/SQL, and authorization schemes is a real saving — building the agent loop, confirmations, and chat UI from scratch is a lot of plumbing for a feature whose value is in the tools and validation, not the framework. Your PDF sales order example is the key detail for me: calling the agent from PL/SQL and validating its output there keeps the business rules where they already live, so the agent is a caller, not a new source of truth. To answer your closing question, the limitation that would push me elsewhere is the one you name second: waiting on an Oracle fix for a missing provider feature. If a workflow needed a capability the framework simply does not expose — say a particular tool-calling pattern or streaming behavior — and there was no clean workaround, that is when the maintenance cost of a separate framework starts to look worth paying. Until that point, staying inside APEX seems the right trade.