The PDF is read locally before any AI request
1into1 first opens the PDF in the browser and extracts page text locally. Pages with very little digital text can use the shared local English OCR fallback before the document text is assembled.
This separates document reading from the later AI network request.
Choose the endpoint that should receive the excerpt
The current interface includes presets for Groq, OpenAI, OpenRouter and DeepSeek, plus a Custom / Local option for an OpenAI-compatible endpoint such as a local model server.
Cloud providers normally require your own API key. A custom endpoint can be used without a key when the server itself does not require authorization.
Consent is required before the provider request starts
The Send workflow checks the data-sharing consent box before it performs the model lookup or chat request. Changing the file, provider or custom endpoint clears that consent so the destination must be approved again.
The browser Fetch API is what sends the request to the configured endpoint; there is no 1into1 AI relay in this component.
The document context is capped at 30,000 characters
Before building the system prompt, the current tool takes the extracted document text and keeps the first 30,000 characters. That excerpt becomes the document context supplied to the chosen model.
For long PDFs, later sections beyond that character limit are therefore not part of the current AI request unless the workflow is changed in a future version.
Treat the answer as an assistant response, not the source of record
The system instruction tells the model to answer from the provided excerpt and to say when the answer is not present, but that does not eliminate model error.
Check names, numbers, obligations, dates and other important conclusions against the original PDF before acting on them.
Official sources reviewed
- MDN — Fetch APIDocuments browser-side network requests using fetch, the mechanism the current AI workflow uses to call the configured endpoint.
- MDN — Window.sessionStorageExplains browser session storage, which the current component uses for the third-party API key.