The CogniChem Assistant plans computational work from a plain-language request. It runs in the app; Use the Assistant is the quick start.
Confirm to run
The Assistant can read, look things up, check, and estimate, but it cannot start, cancel, or delete anything. When it has a plan it proposes a run, which appears as a plan card with the server's estimate. Only your Approve starts it:
- Approving checks the plan again and re-prices it at your current rates.
- If the price went up, nothing starts; the card shows the new price for you to approve.
- If your wallet can't cover it, nothing starts and the card stays pending.
- Otherwise the job or workflow starts exactly as if you had submitted it yourself, under your account.
Each card can be approved once, and expires after 30 minutes. Approving costs no tokens.
What it can look up
- CogniChem's catalog: tools, job schemas, workflow templates, and ports.
- Public databases: PubChem (compound names to structures), ChEMBL (molecules, targets, activities), Open Targets, UniProt, and the RCSB PDB, through CogniChem's lookup service. Results carry a link to their source record and licence.
- Method papers for each tool.
- Your results: the status of runs started from the conversation, and records from their output files.
Only names and IDs are sent to the public databases. ChEMBL similarity and substructure search need a structure (SMILES) to leave CogniChem, so they work only after you turn on structure search for that conversation. Files you attach stay in your artifact library: the Assistant passes them to tools by reference and never reads their contents into the conversation.
What it costs
Turns are charged to your wallet for the language-model tokens they use, at your plan's rates:
- Before a turn, CogniChem holds enough for the longest reply it could give (a turn can make several model calls, for example to use tools).
- After the turn you pay for the tokens actually used, and the rest of the hold is released.
- Stopping a turn, or closing the page during one, charges only for what was used so far. Turns that fail on the provider's side are not charged.
| Tokens | Basic | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Input | $0.70 | $0.50 | $0.40 | $0.30 |
| Cached input | $0.070 | $0.050 | $0.040 | $0.030 |
| Output | $4.20 | $3.00 | $2.40 | $1.80 |
| Tokens | Basic | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Input | $7.00 | $5.00 | $4.00 | $3.00 |
| Cached input | $0.700 | $0.500 | $0.400 | $0.300 |
| Output | $35.00 | $25.00 | $20.00 | $15.00 |
Limits
- Spend cap: each conversation can spend up to $1.00. When the next turn would pass it, the Assistant stops and asks; continuing raises that conversation's cap by $1.00.
- Time: a turn has 180 seconds in total, tool calls included. A turn cut off by the limit is charged for what it used and keeps its partial reply.
- Message length: up to 16,000 characters.
- Memory: each turn sends the model the most recent part of the conversation (about 12,000 tokens); older messages stay on screen but drop out of its context.
From code
The Assistant's API is under Assistant. It needs a signed-in access token (API keys are refused) and streams each turn as server-sent events. The Python SDK wraps it in client.chat.