contractor

High-performance tensor index contractor

A new way for AI to search for data
View on GitHub
1GitHub stars

Go

What XERJ indexed

Snapshot

Whole repository

The whole repository at commit ff5f34f627 (2026-10-21).

Selected work

“Update to version 0.2.0”. 10 files, 528 lines in pkg/pipeline, scripts, cmd/contractor.

Licence

The repository

GPL-3.0

Checked by a person at the pinned commit.

The XERJ corpus

Approach only

The author agreed by email on 2026-10-22. Agents read it for how it works, not to copy it. Answers name the repo, the commit and the file:line.

in licence reviewnot in the hub yetsuggested use: approach only

Example questions

The prompt

Paste it into your AI agent. It clones izokina/contractor at the pinned commit and indexes it on your machine.

Search the GitHub repository izokina/contractor with XERJ (https://hub.xerj.org/corpus/izokina--contractor).
Run these in a shell, in order, and check each result before the next:
1. xerj --help  (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh
2. git clone https://github.com/izokina/contractor contractor && git -C contractor checkout ff5f34f627669d4920953c4bc8c0fbac5e377823
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./contractor --url http://127.0.0.1:9200 --prefix contractor --progress plain
5. xerj autoindex map --url http://127.0.0.1:9200
Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt
Licence: GPL-3.0. Read it for the approach only, do not copy code.

Related

Selected work and consent: the XERJ registry.