Context graphs for agents
that need to reason.

Turns multimodal data into queryable knowledge graphs. Agents can traverse relationships, reason across sources, and cite the evidence.

OpenGraph AI works with coding agents.

Build graphs, inspect what each file contains, and ask questions answered from the graph with cited evidence.

Give your coding agent a connected view of your workspace instead of another pile of isolated search results.

More context.
Less overhead.

Works inside your agent.

Prompt naturally. OpenGraph builds and queries the connected context behind the answer.

Example output

Answers that follow the edges.

The agent hops across typed relations to the frame that shows it, instead of guessing from the closest caption.

Example output

Where did I leave my phone, and what was next to it?

Robot camera frame ep03_step-010: a phone and a glass of tea on a kitchen island beside a laptop, under a wall clock that reads 09:41.
ep03_step-010.jpg
  1. phone on_top_of kitchen_island
  2. phone next_to glass_mug
  3. phone seen_in ep03_step-010.jpg

Every link carries a score.

Extraction records how sure it was about each node and edge, from 0 to 1. Raise the bar to see which links hold up.

Example output

Robot camera frame ep03_step-040: a laptop, potted plant, mouse, and fruit basket on a kitchen counter, with a tablet, clock, kettle, and coffee machine behind them.
ep03_step-040.jpg1600 × 1067
0.60

7 of 8 objects and 6 of 8 relations kept. Weakest relation kept: digital_clock behind tablet, 0.64.

Every node points back to its source.

Pick a source type to see the box, sentence, or cell a node was extracted from.

Example output

Robot camera frame ep03_step-025, with a box drawn around the fruit basket on the counter.
ep03_step-025.jpg1600 × 1067
type
"object"
label
"fruit_basket"
bounding_box
[0.71, 0.49, 0.29, 0.31]
confidence
0.95
seen_in
["ep03_step-010", "ep03_step-025", "ep03_step-040"]

From raw context to a queryable graph.

Start from the terminal, connect your sources, and query the same graph from the interface your agent already uses.

opengraph — CLI

CLI

Build, inspect, and query a graph from your terminal. Good for scripts, CI, and a first look at your data.

Questions, answered.

What OpenGraph AI does today, where your data goes, and how to start building.

Still have a question? Ask us directly or dig into the docs.

What is OpenGraph AI?

OpenGraph AI is an open-source context layer for AI agents. It turns your files into knowledge graphs of entities, the relationships between them, and the source each one came from, then gives agents tools to query those graphs over MCP or a CLI.

It ships as separate packages per data type. OpenGraph Image and OpenGraph Text are on PyPI; OpenGraph Table is in preview.

How is this different from vector search or RAG?

Vector search finds passages that look similar to a question. A graph stores explicit, typed relationships, so an agent can follow on_top_of, acquired, or part_of edges across several steps and keep the evidence attached at every hop.

They work well together: retrieve broadly with embeddings, then use the graph to resolve relationships and cite sources. Read how context graphs work.

What kinds of data can it handle today?
  • Images (photos, screenshots, video frames) with OpenGraph Image
  • Documents (.txt, .md, .pdf) with OpenGraph Text
  • Tables (CSV, TSV, Excel, and photos of tables) with OpenGraph Table, in preview

Audio and video files aren't read directly yet. For video, sample frames into a folder and build an image graph from them.

Which agents and tools does it work with?

Any MCP-compatible client, including Claude Code, Claude Desktop, and Cursor. Register a server once and the agent picks the right tools on its own:

claude mcp add opengraph-image -- opengraph-image-mcp

There is also a CLI for scripts and CI, and every build writes a plain graph.json you can load in your own code.

Does my data leave my machine?

Building and querying a graph call your model provider, currently Claude through the Anthropic API, so source content is sent there for extraction. The graph itself is written to a local opengraph-out/ folder next to your data, and you decide where it goes from there.

Check your provider's data terms before processing anything sensitive.

What does it cost? Do I need an API key?

The packages are free and open source under the Apache-2.0 license. Extraction and querying use Claude, so you need an Anthropic API key set as ANTHROPIC_API_KEY, and that usage is billed by Anthropic. Build cost grows with the number of files you process.

How do I check where an answer came from?

Every node keeps a link to its source. Image objects list the images they were seen in, text claims link to the document that states them, and table values keep their file, sheet, and cell.

Ask the agent to show its evidence, or call get_image_entities or get_document_entities to inspect everything extracted from a single file.

How do I get started?

Install the image package and build a graph from any folder of pictures:

pip install opengraph-image
opengraph-image build ./photos

The quickstart walks through the rest. To see a finished graph first, open the live robot-memory sample; it needs no install.

Can I contribute or request a feature?

Yes. Issues and pull requests are welcome on GitHub. New test images, extraction edge cases, and documentation fixes all help. To talk an idea through first, join the Discord or email team@opengraphai.io.

The open context layer for reasoning agents.

OpenGraph AI turns tables, text, images, audio, and video into queryable knowledge graphs, so agents can reason over the relationships in your data and retrieve the evidence behind an answer. The first packages cover images, documents, and tables.

Open by design.

One context layer, designed to fit the stack you already trust.

  • Yours to run. Apache-2.0 packages that run on your machine. The graph is a local JSON file you own.
  • Connect every signal. Images, documents, and tables each build a graph today, with every node tied to the file it came from. Audio and video are next.
  • Fits your stack. graph.json loads straight into NetworkX, so it drops into the pipelines and notebooks you already run.
  • One interface for context. Agents reach the graph through MCP tools, the same way they reach everything else.

Talk to us

Building something on top of OpenGraph AI? Tell us about it. We read every message and reply.