support/mechanism/config for external parsing apis

[rawwerks]

i haven't benchmarked the competition in a while, but last time i needed pdf parsing, i felt that llamaparse from llamaindex was the best. this is an external api.

is there a way to include the option of specific external parsers in the workflow?

i might be mis-interpreting the your goals, but it seems to me that you don't really want to compete with any of these specialized unstructured=>structured tools, you simply want attachments to allow many options via a simple, streamlined interface...

[MaximeRivest]

You are not mis-interpreting the goals for attachments, we want the 'best' default presenters to have the 'best' prompt possible by default. HOWEVER, I want the default to not require: api keys, internet connection, gpus. But this is the defaults, we should definitely let users turn on other presenters.

I have everything setup for dsl in the string, like:

Attachments("mypdf.pdf[engine: llamaparse]")

Would be easy to add.

I think that a capability to change the dsl defaults would also be great.

Any toughts?!

[rawwerks]

i think we are aligned. the default should not need external suppliers, but it would be great to be able to add your favorite 3rd party engine for specific steps in a flow.