Send the file.
Submit up to 20 MiB with your service key. The server inspects the bytes without executing the file or extracting archives.
03 / CLARITY FOR YOUR PRODUCT
One unfamiliar file.
A useful answer.
Give your product or assistant a way to identify files.
The browser desk works on its own, without an account.
THE SERVICE API
DEVELOPMENT BUILDGet a clear answer.
Receive the format, evidence and limits. Ask for a short preview when you need one. Security remains “not assessed.”
Count completed work.
Each completed inspection uses one credit. Failed inspections release it. Retrying the same request ID does not charge again.
A SMALL, DIRECT CONTRACT
Use HTTP or connect an assistant.
POST /v1/inspect identifies a file. GET /v1/usage shows your credit balance. /mcp exposes the same engine to compatible remote clients.
Reports are separate and created only when requested. There is no automatic certificate or public fingerprint registry.
POST /v1/check runs the AI file check on the service with a File Room key. Unlike the local plugin, this sends the file to the service.
KNOW WHERE YOUR FILE GOES
Your browser. Or an explicit service call.
The browser desk reads your file on your device. Using the API sends it to the File Room service. The application ledger records account IDs, random request IDs, times and credit status; it does not store file bytes, names, fingerprints or results. Hosting infrastructure and assistant providers have their own data handling.
This service API build has no public endpoint, self-service accounts or checkout. Its keys and credits are provisioned by an operator for development, and its pricing is not active. The AI file check in the local plugin is sold separately.
File Room is by Dark Vector Cognition. It identifies and previews supported formats; it does not scan for malware, sanitize files or certify safety.