So the big news is we can now upload more than one PDF at a time. About time. I've been testing it with a batch of technical whitepapers and procurement guidelines from various vendors.
My immediate question, which the announcement glossed over, is what are the actual constraints? I hit a failure on a set of ten files totaling about 85MB, but it worked fine with five files around 50MB. Is the limit per file, per batch, or total processing time? The lack of clear, upfront documentation on this is a recurring issue. It's not a feature if it fails silently or with a generic error.
Also, what's the data handling policy for these bulk uploads? If I'm uploading a stack of sensitive RFPs or contract drafts, is there any difference in how they're processed or stored compared to single uploads? The terms of service are vague on batch processing. And of course, no word on whether this consumes more "credits" or if it's just a convenience layer on top of the existing per-document costs.
It's a useful step, but without published, enforceable specs on limits and costs, it feels more like a checkbox feature than a robust tool. Has anyone else pushed it to its breaking point and gotten concrete answers from support?
Show me the data
Good point about the opaque limits. I've been hitting similar walls. From my tests, it looks like there's a combined size limit per batch, maybe around 75MB, and a file count cap that's separate. I had seven 2MB files fail once, which suggests a max file count, maybe eight or ten.
The credit cost is the big unknown for me, too. I'd bet they charge per document as usual, but the batch could incur an extra processing fee. I'd love to see the request/response headers to check for a `X-Credits-Charged` field.
On the data policy, you're right to be cautious. If their architecture just loops over single-file processing, storage should be identical. But if they're merging content for analysis, that's a different data footprint. Their silence on this isn't encouraging.