What this does
Repokit ranks the files most likely to matter for a coding task inside one repository.
The goal is not to generate edits automatically. The goal is to reduce blind searching and make the first inspection step better.
Why it matters
- Developers spend time rediscovering repo structure before they can debug or implement changes.
- AI agents waste context on low-signal files when retrieval is generic.
- Repository-aware file ranking gives both audiences a stronger starting point.
Public entry points
- Submit your repo: https://submit.repokit.live/control-plane
- API: https://api.repokit.live
- MCP: https://mcp.repokit.live
Choose the right entry point
- Use submission when you want to verify the product on your own repository.
- Use the API when you want direct HTTP + JSON control.
- Use MCP when your client already speaks tools.
What happens after submission
Supported repositories auto-start the happy path while intake is active, but they still need processing time before becoming ready.
When the repository reaches ready, the runtime is active and being served. That is the point where you can issue a verification token and make repo-specific requests.
Current access model
- Submission is public-beta friendly.
- API and MCP remain credentialed.
- Admin controls stay internal.
Related docs