repowise-dev
Repowise is an open-source (AGPL-3.0) codebase intelligence platform that indexes any repository once and serves both AI coding agents and the humans accountable for the code. It provides queryable architecture documentation, a dependency graph, git intelligence, architectural decisions, and ten MCP tools for Claude Code, Cursor, Cline, and Codex. For teams, it offers a defect‑validated code‑health score.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles repowise-dev the way a machine reads it — 57 machine-readable artifacts across 1 API, 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 — repowise-dev scores 66.0/100 (strong), with a separate agent-readiness read of 60/100 (agent native). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from repowise-dev's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/repowise-dev/"
title="repowise-dev on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/repowise-dev.svg"
alt="repowise-dev Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/repowise-dev/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/repowise-dev/"
title="repowise-dev on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/repowise-dev/card.svg"
alt="repowise-dev Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile repowise-dev
Each block below is one kind of artifact we hold for repowise-dev. 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 41
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.
repowise-dev Actions API
The actions API from repowise-dev — 3 operation(s) for actions.
repowise-dev Areas API
The areas API from repowise-dev — 3 operation(s) for areas.
repowise-dev Blast Radius API
The blast-radius API from repowise-dev — 1 operation(s) for blast-radius.
repowise-dev C4 API
The c4 API from repowise-dev — 7 operation(s) for c4.
repowise-dev Changes API
The changes API from repowise-dev — 4 operation(s) for changes.
repowise-dev Chat API
The chat API from repowise-dev — 9 operation(s) for chat.
repowise-dev Claude Md API
The claude-md API from repowise-dev — 2 operation(s) for claude-md.
repowise-dev Code Health API
The code-health API from repowise-dev — 24 operation(s) for code-health.
repowise-dev Costs API
The costs API from repowise-dev — 3 operation(s) for costs.
repowise-dev Coupling API
The coupling API from repowise-dev — 2 operation(s) for coupling.
repowise-dev Dead Code API
The dead-code API from repowise-dev — 4 operation(s) for dead-code.
repowise-dev Decisions API
The decisions API from repowise-dev — 10 operation(s) for decisions.
repowise-dev Doc Drift API
The doc-drift API from repowise-dev — 2 operation(s) for doc-drift.
repowise-dev Episodes API
The episodes API from repowise-dev — 4 operation(s) for episodes.
repowise-dev Events API
The events API from repowise-dev — 1 operation(s) for events.
repowise-dev External Systems API
The external-systems API from repowise-dev — 5 operation(s) for external-systems.
repowise-dev Feedback API
The feedback API from repowise-dev — 1 operation(s) for feedback.
repowise-dev Files API
The files API from repowise-dev — 2 operation(s) for files.
repowise-dev Git API
The git API from repowise-dev — 13 operation(s) for git.
repowise-dev Graph API
The graph API from repowise-dev — 15 operation(s) for graph.
repowise-dev Health API
The health API from repowise-dev — 3 operation(s) for health.
repowise-dev History API
The history API from repowise-dev — 1 operation(s) for history.
repowise-dev Jobs API
The jobs API from repowise-dev — 4 operation(s) for jobs.
repowise-dev Knowledge Map API
The knowledge-map API from repowise-dev — 1 operation(s) for knowledge-map.
repowise-dev MCP API
The mcp API from repowise-dev — 1 operation(s) for mcp.
repowise-dev Meta API
The meta API from repowise-dev — 2 operation(s) for meta.
repowise-dev Modules API
The modules API from repowise-dev — 2 operation(s) for modules.
repowise-dev Overview API
The overview API from repowise-dev — 1 operation(s) for overview.
repowise-dev Owners API
The owners API from repowise-dev — 4 operation(s) for owners.
repowise-dev Pages API
The pages API from repowise-dev — 6 operation(s) for pages.
repowise-dev Platform API
The platform API from repowise-dev — 2 operation(s) for platform.
repowise-dev Providers API
The providers API from repowise-dev — 5 operation(s) for providers.
repowise-dev Refactoring API
The refactoring API from repowise-dev — 11 operation(s) for refactoring.
repowise-dev Repos API
The repos API from repowise-dev — 12 operation(s) for repos.
repowise-dev Search API
The search API from repowise-dev — 1 operation(s) for search.
repowise-dev Security API
The security API from repowise-dev — 2 operation(s) for security.
repowise-dev Setup API
The setup API from repowise-dev — 5 operation(s) for setup.
repowise-dev Stats API
The stats API from repowise-dev — 1 operation(s) for stats.
repowise-dev Symbols API
The symbols API from repowise-dev — 4 operation(s) for symbols.
repowise-dev Webhooks API
The webhooks API from repowise-dev — 3 operation(s) for webhooks.
repowise-dev Workspace API
The workspace API from repowise-dev — 18 operation(s) for workspace.
Scroll within the panel for all 41 ·
Agent Skills 1
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
list-repos
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Repowise Dev Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Repowise Dev Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
repowise-dev API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CommitDetailResponse
JSON SCHEMADecisionRecordResponse
JSON SCHEMAGitMetadataResponse
JSON SCHEMARefactoringPlanDetailResponse
JSON SCHEMASavingsResponse
JSON SCHEMAWorkspaceExtractionDiagnostics
JSON SCHEMASecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 repowise-dev — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/repowise-dev · machine-readable index on apis.io
This is an independent, third-party profile of repowise-dev, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.