Ask AI & credits
Ask AI
What Ask AI does, what it doesn't, how to ask good questions, and what a degraded response means.
What Ask AI does
Every document in your library has a chat. Open a document and ask a question; Ask AI finds the most relevant passages in that document and writes an answer grounded in them, with the source passages listed under the answer so you can check them.
The chat remembers the conversation: follow-up questions like “when did that happen?” are understood in context. Your latest conversation for a document is restored when you come back; New chat starts a fresh thread.
What it doesn’t do
- It doesn’t search the web — answers come only from the document you’re chatting with.
- It doesn’t answer from your other documents; each chat is scoped to one document.
- It’s instructed to answer only from the document’s content and to say so when the document doesn’t contain the answer, rather than guessing.
As with any AI-generated text, verify important details against the cited passages.
Cost
Each question costs 2 credits. The credits are reserved when you send the question and only charged when an answer is actually generated and saved. Failed or degraded turns are not charged — the hold is released. See credits.
Degraded responses
Sometimes Ask AI replies that it couldn’t find enough support in the document to answer confidently. That means retrieval didn’t find passages relevant enough to ground an answer, so no answer was generated — and no credits were charged. It usually happens when the question is about something the document doesn’t cover, or is phrased too far from the document’s own wording.
Asking good questions
- Ask about what the document actually covers.
- Use specific wording — names, terms, and phrases from the document retrieve better than broad questions.
- Follow-ups are fine; the chat resolves references like “it” or “that section” from the conversation.
- Questions are capped at 2,000 characters.
Last updated: June 12, 2026
Need more help?
Email support@permanentrecord.ai. Include the page URL, what you expected, what happened instead, and roughly when it happened — that helps us find it fast.