API

Use Repokit through direct HTTP requests.

Start on repokit.co/api for the product overview. Use the raw API base URL only for actual HTTP + JSON requests.

Page intent

Use this page as the human-facing API overview, then use the base URL below when you send real requests from a client or workflow.

POST /find_relevant_filesBearer token

Request

{
  "repository_id": "<repository_id>",
  "query": "add repo verification before API access",
  "top_k": 3
}

files

path · score · confidence · explanations

1. apps/api/auth/verifyRepo.ts

score 0.97medium

explanations[0]: RECENT_EDIT · ownership check and readiness gate

2. lib/github/claim-repository.ts

score 0.84medium

explanations[0]: PATH_MATCH · claim and verification handshake

Metadata

request_id

feda8a88...

repository_id

gh-1189094555

model_version

lightgbm-lambdamart-v1

candidate_universe_size

156

latency_ms

42

runtime

active runtime object

Base URL

https://api.repokit.co

Primary endpoint

https://api.repokit.co/find_relevant_files

Feedback endpoint

https://api.repokit.co/find_relevant_files/feedback

What this page is for

Repokit provides repository-aware retrieval inside one repository.

This page is the human-facing API product page. The raw hostnames below are for technical request targets, not for marketing navigation.

What you can do today

  • List the repositories enabled for your token.
  • Inspect presets for one repository.
  • Call find_relevant_files on a ready repository.
  • Submit feedback tied to a request_id.

Fastest verification path

  • Activate a supported repository.
  • Wait until it reaches ready.
  • Issue a verification token.
  • Call find_relevant_files.
  • Compare results with actual files you inspect.

Quick request example

find_relevant_filesbash
curl -sS \
  -H "Authorization: Bearer <your_token>" \
  -H "Content-Type: application/json" \
  https://api.repokit.co/find_relevant_files \
  -d '{
    "repository_id": "<repository_id>",
    "query": "fix request validation error in routing",
    "active_files": ["app/routing.py"],
    "recent_files": ["tests/test_routing.py"],
    "failing_tests": ["tests/test_routing.py"],
    "top_k": 5
  }'

What a response gives you

  • A request_id for tracking and feedback.
  • A ranked files list with scores, confidence, and explanations.
  • Runtime metadata for inspection.
  • Latency and candidate-universe details.

When to use the API

  • You want direct HTTP requests.
  • You are building backend or editor integrations.
  • You want structured control over requests.