BrainGraph, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your BrainGraph account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Artificial Intelligence
- Connects with a key
- 10 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What BrainGraph is
BrainGraph builds a searchable knowledge graph from documents, recordings, web pages, and other source material for grounded AI workflows.
You paste in a key from your own BrainGraph account. It is kept encrypted, and you can withdraw it from inside BrainGraph whenever you like.
One message in, the work done in BrainGraph.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in BrainGraph. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own BrainGraph account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in BrainGraph
These are the ready-made tools your AI employee already has in BrainGraph. It is not limited to them, but it never has to be taught these.
- Get Document ProgressGet the current transcription, processing, and analysis status for a BrainGraph document. Poll until transcript.status is analyzed; analysis is null while processing is incomplete.
- Ingest Web PageFetch readable content from a public web page and queue it for BrainGraph ingestion. This creates persistent data and consumes upload and URL-submission quota. After a timeout or o
- Ingest YouTube VideoSubmit a YouTube video for metadata, transcript, and speaker processing; the result may only confirm that processing was queued. This creates persistent data and consumes upload an
- List BrainsList the connected BrainGraph account's knowledge brains and identify the default brain for filtering or targeting other tools.
- List DocumentsList BrainGraph documents newest first, optionally filtering by filename or notes, failed ingestion status, and brain. Returns one page at a time.
- List Graph PatternsFind recurring relationship-chain patterns in the connected BrainGraph knowledge graph, subject to a minimum occurrence count.
- Resolve EntityResolve an entity name to a canonical BrainGraph record. If there is no single match, return an explicit ambiguous or not-found result rather than treating it as an HTTP error.
- Search BrainSearch facts in the connected account's BrainGraph knowledge graph using a natural-language question, optionally restricted to selected brains.
- Transcribe AudioUpload an audio file or submit a direct public audio URL for diarized transcription and graph ingestion. This creates persistent data and consumes upload and transcription allowanc
- Upload DocumentUpload a document file supplied by the caller or plain text and queue it for BrainGraph ingestion. This creates persistent data and consumes the account's upload allowance. After a
You stay the boss of your BrainGraph account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own BrainGraph account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in BrainGraph is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in BrainGraph and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about BrainGraph
- Can an AI employee really work inside BrainGraph?
- Yes. It signs in to your own BrainGraph account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of BrainGraph?
- No. Nothing moves and nothing is replaced. Your records stay in BrainGraph, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my BrainGraph account?
- You paste in a key from your own BrainGraph account. It is kept encrypted, and you can withdraw it from inside BrainGraph whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in BrainGraph?
- It has 10 ready-made tools in BrainGraph today, among them Get Document Progress, Ingest Web Page and Ingest YouTube Video. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use BrainGraph and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in BrainGraph and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in BrainGraph?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in BrainGraph is written down with what it did and when.