Sourcebot
Sourcebot is a self-hosted code understanding platform built by Taqla Inc. that helps developers and AI agents search, navigate, and understand large enterprise codebases. It indexes every repository across GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit, and Gitea and runs entirely inside your own infrastructure, so source code never leaves your deployment. Alongside a fast regex- and symbol-aware code search UI with file explorer and git history/blame, Sourcebot ships "Ask Sourcebot" natural-language codebase Q&A and an agent code context layer (an MCP server) that gives coding agents like Cursor and Claude Code grounded context across every repo. Its public REST API exposes search, symbol navigation, repository listing, git history/blame/diff, and enterprise user/audit endpoints, secured with API keys (and EE OAuth for agent clients). Free self-hosted Basic tier, paid Pro tier for AI and enterprise security.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Sourcebot the way a machine reads it — 9 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sourcebot scores 51.5/100 (developing), with a separate agent-readiness read of 52/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Sourcebot
Each block below is one kind of artifact we hold for Sourcebot. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Sourcebot Enterprise (EE) API
Enterprise endpoints for user management and audit logging.
Sourcebot Git API
Git history, diff, and file content endpoints.
Sourcebot Repositories API
Repository listing and metadata endpoints.
Sourcebot Search & Navigation API
Code search and symbol navigation endpoints.
Sourcebot System API
System health and version endpoints.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sourcebot-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Sourcebot — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/sourcebot · machine-readable index on apis.io