Not a capability list. What follows is work somebody in your company does on a Monday, the size of model that is enough for it, and where it stops. The last part is the one most pages leave out.
Prepaid API credit · Swiss company · nothing used for training
Four common patterns, each one API call in the middle of something you already run. The companies and data in these examples are made up.
Your backend sends the visitor's question together with the relevant pages. The instructions say to answer only from them, and to say so when the answer is not there.
neurolism-mediumA script takes the text of each incoming invoice, asks for the fields as JSON and writes them where your bookkeeping expects them. One prompt instead of a template per supplier.
neurolism-smallEach new ticket goes through one short call that returns topic, urgency and team. Your helpdesk does the routing; the model only reads and labels.
neurolism-smallSend the matching sections of your handbook or wiki with the question and ask for the answer to cite them. People check the source instead of trusting a summary.
neurolism-largeThe same models and the same rules about your data. What changes is the documents on the desk. Here is what it does in each, and every case in detail under all use cases.
Clinics and practices run on documents: guidelines, referrals, lab reports, letters. Neurolism reads them, drafts the text and shows the passage it used, so the person who signs can check it in seconds.
Ask in plain language, get the passage from your own guideline and protocol documents, with the page it came from. No answer without a source.
Structured notes in, a draft out, in your house wording. Facts stay in the source document; what is missing stays visibly missing instead of being filled in.
Referrals, findings and forms arrive as PDF or scan. Read out the fields you need, sort them by type and hand them to the system that stores them.
The same information in German, French or Italian, and a version a patient can read, side by side with the original.
Where it stops. It does not diagnose and it does not decide on treatment. It reads documents, drafts text and points at the source. Everything that carries a signature stays with the person who signs it.
A business account is separate from a personal one: its own billing, its own keys, its own usage. What you reach it with is your choice.
An OpenAI-compatible endpoint. Most existing clients work after changing a base URL and a key. One key per environment, usage visible per key, prepaid credit so nothing runs up a bill you did not see.
Rates and the endpointFor teams who work in files rather than in a browser: it opens a folder on the machine, reads what is in it, and writes only with a confirmation. Nothing is uploaded that you did not attach.
DownloadBusiness accounts can run on our server in Switzerland. Written into the contract, not offered as a badge, and available on request rather than by default.
Where the servers areInvite colleagues by email. They sign in with their own password, under your account - no shared login, and no second bill for the same department.
You say who may join; the account belongs to them from the start and they set their own password. Creating accounts for people would mean you know their password, which is a different arrangement than it looks like.
Members cannot see or create API keys, top up credit, invite anyone or change the company. A key every member can read is a key that outlives the company - at everyone who was ever on the team.
A shared budget is not a shared inbox. Nobody reads anybody else’s conversations, the owner included. Sharing one is something you do on purpose.
One page shows who used how much, per day, per person and per key, and what is left on the account. No report to request and nothing to install.
Plus, Pro or Max at the normal price, paid by the company. You give each seat to a person in the team list, so nobody ends up on a paid plan you did not give them.
It works for one email address only. Forwarding it to somebody else does not let them in.
Credit is topped up in advance and drawn down per token actually used. No monthly minimum and no fee per key.
No. Content sent through a business account is not used for training, ours or anyone else's. It is a property of the product, not a setting somebody has to find and switch off.
On the standard plans, model inference runs with DigitalOcean in New York and the EU, and the application and database with a hosting provider in the United States. That is written out in full on the imprint page rather than summarised into a claim we cannot keep. Business accounts can run on our server in Switzerland on request.
The API runs on prepaid credit in Swiss francs, deducted per token actually reported by the model, with no monthly minimum and no per-key fee. Seats for the app (Plus, Pro, Max) cost the normal plan price. Every top-up produces an invoice with your VAT number on it.
It means a wrong answer is more likely to arrive as a refusal than as a confident paragraph. For support and legal work that is the difference between a person checking one answer and a person checking every answer.
Yes. Evidence is precomputed into an index rather than pushed through the request, so adding internal material is a build step and not a retraining run.
Lumen, in three sizes: Small for short work, Medium for most of it, Large from the Pro plan for long contexts and deep chains. In the app, people choose the size; an API request names it outright.
It is measured, not asserted. On a balanced set, cross-validated so that every case is judged by weights that never saw it: AUC 1.000, ECE 0.210, Brier 0.057. Sixteen cases is a start and not a calibration anybody should build a sign-off on, and we would rather write that here than let you find it out later.
Accounts that hold API keys use two-factor authentication by email. Members cannot see or create keys, top up credit or invite anyone - only the owner can. Keys are shown once and stored hashed, so a copy of our database is not a copy of your keys.
No. Register the company, top up credit, create a key. If you want a contract, a data processing agreement or an invoice on different terms, write to info@neurolism.com.
Three steps and no sales call. If you need a data processing agreement or an invoice on different terms, write to info@neurolism.com.
Compare plans