Etherscan partners with GitMyABI to turn verified contracts into installable npm packages

Building on Ethereum smart contracts has always involved a quietly annoying step: wrangling ABIs. An ABI, or Application Binary Interface, is essentially the instruction manual that tells your code how to talk to a deployed contract. Getting one typically meant copying JSON blobs from block explorers, pasting them into your project, and hoping nothing changed upstream. Etherscan’s new integration with GitMyABI is designed to make that entire ritual obsolete.

The partnership, surfaced through Etherscan’s “Cards” tab on verified contract pages, lets developers convert any verified contract ABI into an installable npm package with full TypeScript bindings in a single click. No context-switching, no manual file management, no prayer-based version control.

What GitMyABI actually does

GitMyABI is a developer platform built by AxLabs, a Swiss Web3 firm. It launched in beta on February 7, 2025, with a focused mission: automate the entire lifecycle of ABI management for EVM-compatible chains.

The tool handles ABI extraction from GitHub repositories, versioning, npm publishing, and TypeScript binding generation. Packages are published under the @gitmyabi scope on npm, with specific entries like @gitmyabi/aethusdc for individual contracts. The TypeScript bindings use the viem type system, which means developers get autocomplete and compile-time checks for contract methods, events, and parameters. If you call a function with the wrong argument type, your editor catches it before your transaction reverts on-chain.

Why ABI management matters more than it sounds

Etherscan has long provided APIs for fetching verified contract ABIs. That solved the “where do I find this” problem. What it didn’t solve was the downstream workflow: turning that raw JSON into typed client code, keeping it versioned alongside your application, and ensuring every developer on your team is using the same interface definition.

GitMyABI collapses that multi-step process into something that looks more like installing any other dependency. Run an npm install, import the typed bindings, and start calling contract functions with full IDE support. The automation covers everything from the initial ABI extraction to the final published package, which means updates to verified contracts can flow through the same pipeline without manual intervention.

The Etherscan integration in context

Etherscan’s Cards tab allows third-party tools to surface functionality directly on contract pages. GitMyABI’s presence there means developers can discover and generate packages while they’re already browsing contract details, rather than navigating to a separate platform.

For AxLabs, the Etherscan integration provides distribution at exactly the moment a developer is thinking about how to interact with a specific contract, without leaving the Etherscan workflow.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.