Buildermark
Matches coding agent conversations to git commits to measure the percentage of code written by AI agents.
54 linking domains
Emerging
- For
- Development teams measuring how much code their AI coding agents generate
- Price
- Price not read
- Activity
- Maintainednothing dated on the site
- Company
- founding year not on record
- Runs as
- CLIDesktop app
- track percentage of each commit written by AI agents
- compare performance of different coding agents on your codebase
- aggregate agent metrics across your organization
- #1
JetBrains
Integrated development environments for Java, Python, JavaScript, C++, .NET and Kotlin with code analysis and debugging.
492kActive—2002 - #2
DeepSeek
Language model API for text generation and reasoning tasks.
490kActiveFrom $0.02 per use2023 - #3
Twilio
Sends and receives SMS, email, and voice messages through APIs and manages customer conversations with AI.
1.1MActiveFree plan2008 - #4
PostHog
Ingests product data and runs AI agents to investigate issues and recommend product improvements.
24.7knot readFree plan2020 - #5
AI Innovation Workspace
No description yet.
1.1MActive— - #6
Zayed Shield
No description yet.
30.9knot read—
What is Buildermark?
Matches coding agent conversations to git commits to measure the percentage of code written by AI agents.
Who is Buildermark for?
Development teams measuring how much code their AI coding agents generate
Do people use Buildermark?
Emerging.
Is Buildermark still maintained?
Maintained.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.