AI
Visitors’ own AI tools
Visitors can point their own AI tools at your room through the machine view and a personal token. Here is what those tools can and can’t read.
Many investors run their own AI to read and compare deals. undocsend gives them a clean, text-only version of your room for that, without handing out your files as public pages. Everything here is read-only and limited to what that visitor is already allowed to see.
The machine view
At the bottom of the room, a View switch flips between Human and Machine. The machine view is a plain, fixed layout of the room and its documents’ text at /<room>/ai/room, built for AI tools. Your room theme doesn’t change it. It includes the room assistant as a console.
The same content is available as raw markdown at /<room>/room.md, with a .md link for each document.
Personal tokens for AI tools
A visitor’s AI tool can’t sign in with a magic link, so the visitor gives it a personal token instead. In the room header (on wider screens) they click Connect your AI, then:
- Optionally name the token, for example the laptop or tool it is for.
- Click Generate. The token is shown once, as a Raw token and as a Shell export line, ready to copy.
- Copy one of the ready-made prompts, or the Raw HTTP example, into their AI tool. The tool fetches the room’s
room.mdwith the token and follows the document links.
curl -H "Authorization: Bearer $DEALROOM_TOKEN" \
https://acme.undocsend.com/series-a/room.mdThe panel lists the visitor’s tokens with when each was last used. Clicking Revoke cuts that tool off immediately. Tokens don’t expire on their own.
Tokens work on your workspace’s undocsend address (for example acme.undocsend.com), not on a custom domain. The panel gives visitors the right link.
What their tools can read
A token reads exactly what the visitor who made it could read in the room, checked on every request:
- The visitor must still pass the room’s access rules, and must have accepted the current NDA.
- If they came in through a share link for some documents, the token reads only those documents.
- Files limited to other audiences are left out.
- Published FAQ answers are included only if that visitor may see them.
If you revoke the visitor’s access, their tokens stop working too. Public crawlers without a token can’t read the room.
What a token can’t do
- It can’t change anything in the room or download original files.
- It can’t use your room assistant. The visitor’s own AI does its own reading, so this doesn’t use your credits.
Watermarked files
A watermarked file never leaves as copyable text. In the machine view and in room.md, a visitor or their AI tool sees this line in place of the file’s text, with a link to the document in the room:
This document is watermarked, so its text is not available here. Read it in the room:The rest of the document’s details (name, folder, type, pages) are still listed. Your own team, signed in to the workspace, sees the full text.
See which tools read the room
Every token request is logged under the visitor who made the token. In Analytics, open the Agents tab to see which AI tools and automated browsers hit the machine view, and on whose behalf. See Analytics.
Turn it off for a room
The machine view is on for new rooms. To turn it off, open the room’s Settings, switch off Enable machine view, and click Save room settings. The machine view and room.md then stop working for that room, including for tokens.
The undocsend.com/llms.txt file describes undocsend itself to AI crawlers. It doesn’t list or expose your rooms.