The file is checked before model use
AINA accepts supported PDF, PNG, JPEG, and WebP files within enforced size and count limits; the server verifies the real file type.
Use case · Files
Bring the file into the work, not into a separate tool.
AINA supports private PDFs and images with server-side validation, ownership checks, and capability-aware model selection. An account is required because guest sessions do not persist private files.
An account is required for private file storage.
Private files with working context Synthetic QA workspace
Start with real work
A useful first task beats a feature tour.
PDF review“Analyse this PDF and produce a concise brief of the obligations, risks, and questions I should resolve.”Account required
Screenshot“Explain what this screenshot shows, identify the likely issue, and suggest the next checks.”Account required
Evidence table“Extract the key claims from this file and organise the supporting evidence in a review table.”Account required
The AINA route
The model decision supports the work. It is not the work.
Ownership is part of every request
Files are stored privately and scoped to the account, conversation, or project allowed to use them.
The attachment becomes a real requirement
Images require vision support. Larger documents require sufficient context. Incompatible manual choices receive a clear alternative.
High-impact documents still need human checking
Verify quotes, page references, missing sections, and professional conclusions against the original file.
Trust boundary
Useful, with the limits made visible.
- Guest sessions cannot upload private files
- Supported inputs are PDFs and common image formats
- Account deletion includes attachment cleanup
Start with one useful outcome.
Create a Free account to use supported private files in the workspace.