Indexing & search for AI agents

Meet the retrieval layer your agents can trust.

Point JOZENU at almost any source — code, docs, PDFs, datasets, the web — and give every agent one API to retrieve, traverse, reason over, and cite it.

Sub-five-second search Cited, not guessed One interface, every source
jozenu / retrieve live index
gateway/middleware/limiter.go
Token-bucket limiter, per API key
Refills 100 tokens/sec; blocks at the edge before any handler runs.
cited · L42–L77
docs/platform/rate-limits.md
Published limits & burst policy
Defaults, 429 semantics, and the Retry-After contract.
cited · p. 3
answered in 3.4s 2 sources · compressed for context
One interface, every source

Index anything. Retrieve anything.
JOZENU does it all.

Source code, documentation, PDFs, datasets, the open web — point the system at it once and every agent shares the same fast, dependable way to find ground truth and quote it back, line by line.

universal search
workers/billing/retry.py
Exponential backoff, max 5 attempts
cited · L18
status.stripe.com · changelog
Idempotency-key guidance (live)
cited · web
runbooks/billing.pdf
On-call escalation for stuck jobs
cited · p. 7
3.1s across millions of pages small-model compressed

Universal search across everything you index

One query reaches every connected source at once and returns sub-five-second answers across millions of indexed pages and code files. Small models compress what comes back, so agents spend their context window on reasoning — not on wading through raw search dumps.

jozenu — cli
$ jozenu index ./ --deps
parsing manifests… package.json, go.mod, pyproject.toml
✓ 1,240 files · 38 dependencies resolved
✓ dependency trees indexed automatically
 
$ jozenu search "how are webhooks signed?"
→ crypto/webhooks.ts:64 HMAC-SHA256
→ docs/security.md cite p.2
$

Reach into your dependencies, not just your repo

JOZENU reads the manifest files you already commit and automatically indexes the project dependencies behind them — so an agent debugging a stack trace can search the library source itself, not a half-remembered version of it. Public datasets index the same way, behind the same single interface.

A single API for every agent

Retrieve, traverse, reason over, and cite — all through one endpoint. Whatever you indexed, every agent in your stack queries it the same way.

Breadth behind one door

Code, docs, PDFs, datasets, and the web sit side by side. No source-by-source glue code, no separate retrieval stack to maintain for each.

Built for response speed & cost

Sub-five-second answers and compact, compressed results mean lower token spend per call — accuracy and economy in the same request.

Always on, always grounded

Indexes nonstop. Retrieves nonstop.
Cites nonstop.

Retrieval reliability is the hardest part of making an agent trustworthy. JOZENU keeps your knowledge fresh, answers from the real files, and attaches a citation to every claim — so agents reach for ground truth instead of filling the gap with a guess.

Sync engine live
Local folders
~/work · 4 watched paths
indexing
Databases
analytics · read-only replica
synced
Chat history
team threads · personal KB
synced

A synchronization engine that never sleeps

Continuously index local folders, databases, and chat history into one searchable, personal knowledge base. New commits, new rows, new conversations — folded in as they happen, so an agent's answer reflects the state of the world right now.

contract-v3.pdf § 4 of 11
Termination requires 30 days' written notice. — cited p. 12, §8.2
Liability is capped at fees paid in the prior 12 months. — cited p. 14, §9.1

A document agent that reads, then proves it

Long PDFs and reports are read section by section, not skimmed and summarized. Every claim it returns carries the page number it came from — so a reviewer can jump straight to the source and confirm it in seconds.

Sandbox search · no pre-indexing, no embeddings ephemeral
Spin up env
Clone repo
Answer from real files
Tear down
Clones a public repository, answers from the real source, and disposes the environment — nothing left behind, nothing pre-built.

Search a repo you've never indexed — in a sandbox that cleans up after itself

Sandbox search spins up an ephemeral environment, clones a public repository, answers your query from the actual files, and tears the environment back down — no pre-indexing and no embeddings required. The same autonomy powers an on-demand repository-search subagent: hand it a question, and it goes and reads the code for you.

Your sources, your rules. Total control.

Decide exactly what JOZENU can reach, and exactly how your agents connect to it. The breadth lives behind one interface — you keep the switches.

Toggle what gets indexed

Source code
Documentation
PDFs
Datasets
The web
Chat history

Connect every agent, your way

API CLI MCP Skill Coding assistants
Indexed now
1,240 files
across 6 sources · refreshed live
Context shared
Resumes anywhere
histories, plans & sources handed to the next agent

Meet your agents where they already live

Reach JOZENU through an API, a command-line interface, a packaged skill, or the model-context protocol — and plug straight into the popular AI coding assistants your team already uses. Same index, same citations, whichever surface an agent speaks.

Hand off work without losing the thread

Context sharing saves conversation histories, plans, and the exact sources an agent relied on — so work can pause in one agent and resume in another with the full trail intact. No re-explaining, no lost ground truth.

Research mode

Less hallucination. More ground truth.

Research mode turns an indexed codebase into a dynamic tree the agent can query on demand — expanding only the branches a question actually needs. Instead of guessing past the edge of its context, the agent walks to the answer and brings back the proof. That's how JOZENU reduces hallucinations at the source.

Benchmarked where models fail mostWe test on newly released and beta interfaces — exactly the cases language models most often get wrong — and record the lowest error rate among the tools we evaluated.
Query on demand, not all at onceThe agent expands the tree branch by branch, so it reasons over the right slice of the codebase instead of drowning in the whole thing.

What we believe

Retrieval is the hardest part of making an AI agent trustworthy — so it's the part we obsess over.

An agent is only as reliable as the ground truth it can reach. Give it dependable access, and the fabrications fall away.

Every claim should arrive with a citation — a page, a file, a line. If it can't be pointed to, it shouldn't be asserted.

Breadth beats guesswork. Index the source instead of hoping the model happened to remember it.

The JOZENU thesis
code-review agent · run #418
Is this PR using the deprecated auth call?
agent → jozenu.retrieve()
docs · current release notes
authV1 removed — use authV2.verify()
fetched live
src/auth/session.ts:31
Still calls authV1 — flagged
needs change
Built for builders

Built for the agents you're already building.

JOZENU is made for developers and engineering teams shipping AI agents and workflows. Wherever an agent needs to be right rather than merely plausible, it reaches for the index — and comes back with a citation.

Code-review agents that stay current

Fetch the latest documentation as it reviews, so it flags deprecated calls and stale patterns against today's API — not last quarter's.

Legal-research agents over the statute

Index statutes and long documents, then answer with the exact section and page — the kind of provenance legal work depends on.

Community-forum & dataset search

Turn sprawling forums and public datasets into a queryable surface, so agents mine real answers from real threads and real data.

Tell us what you're building
Five ways in, one index

However your agents connect, the ground truth is the same.

API

Programmatic retrieve, traverse & cite

CLI

Index & search from the terminal

MCP

Model-context protocol, native

Skill

A packaged skill, drop-in

Coding assistants

Integrates with the popular ones

Talk to us

Finally, retrieval your agents can build on.

Tell us about the agents you're shipping and the sources they need to reach. We'll help you wire JOZENU into your stack — through the API, CLI, MCP, a packaged skill, or your coding assistant of choice.

Please enter your name.

Enter a valid email address.

Which sources do you need to index?

Let us know what you're hoping to do.

Opens in your email client and sends to hello@jozenu.com. Prefer to talk? Call (720) 309-8050.

Your message is ready to send

We've opened your email client with everything filled in — just hit send and it'll reach us at hello@jozenu.com. We read every note and reply personally.