Skip to content
End Credits

FOR THE OPEN SOURCE BEHIND YOUR AI

Your agent ships.Who getsthe credit?

Turn a Claude Code session into support for the open-source packages it used. Your budget. Their credit.

Voluntary contributions · Testnet USDC on Base Sepolia

ILLUSTRATIVE SESSION
✳Claude Code⌘

Build a better checkout.

↳Built with a little help from open source.
The credits go to…
zzodValidation✓
ddate-fnsDate handling✓
cchalkTerminal colors✓

Usage recorded. Contributions recognized.

Session complete

A whole cast behind every build.

Validators. Test runners. The tiny utility that just works. Your agent uses their work. End Credits helps you recognize it.

Examples of open-source projects in the ecosystem, not customers or endorsements.

THE MISSING THANK-YOU

AI moves fast.Support should follow.

Developers pay for the agent. The packages underneath it are still maintained by people. End Credits connects the work your agent uses to a contribution you choose.

2.1%

listed a payable wallet

In our top-1,000 npm package snapshot, 416 had funding metadata. Just 21 listed a wallet across the sources we checked.

HOW END CREDITS WORKS

One session.A whole chain of thanks.

Follow the work from your AI agent to the people behind its packages. Every contribution has a budget, a decision, and a trail you can inspect.

ILLUSTRATIVE WALKTHROUGH · NO LIVE PAYMENTS

ON YOUR MACHINE

Your agent builds. We follow the ingredients.

Connect Claude Code with the CLI. Hooks quietly record package imports, reads, dependency additions, and documentation lookups. Your source code and repository paths stay local.

Silent hook · always exits 0

The MCP server also lets your agent inspect sessions and initiate settlement using your configured settings.

Claude Code
Build a checkout flow
@endcredits-demo/schema

dependency added

package imported

docs consulted

End Credits hookAttribution signals → session
CODE STAYS LOCAL

Watch the full loop, or jump to any chapter. Amounts and packages here are illustrative.

Explore the implementation ↗

THE INTEGRATIONS BEHIND THE CREDITS

Purpose-built checks. Verifiable execution.

Each integration has a specific job in the contribution flow.

Built at ETHGlobal Tokyo 2026

An open-source hackathon project on Base Sepolia.

GENEROSITY, WITH BOUNDARIES

A little trust. A lot of checks.

You set the budget.

Choose what a session can spend, a daily limit, and a maximum share per package. No surprise open tabs.

Uncertainty means pause.

A screening error means hold, never pay. Escrowed holds need approval; denial or expiry makes them refundable.

No wallet? Still counted.

A package’s share can wait in escrow. Maintainers prove GitHub ownership and publish a wallet to claim it.

Maintain something people build on?

Find your package, inspect its reserved credits, and connect a payout wallet.

Find your package

A LITTLE MORE CONTEXT

Good questions. Clear answers.

What gets recorded, where the money goes, and what stays in your control.

Is this a fee for using open source?+

No. End Credits is voluntary support, never a paywall. Package licenses and access stay exactly as they are. You choose whether to contribute and set the budget.

What leaves my machine?+

Package attribution signals, not your source code or repository paths. The local hook records package reads, imports, and installs, then the session’s package credits are uploaded.

What if a package doesn’t have a wallet?+

Its share can be reserved in EndCreditsEscrow. The maintainer signs in with GitHub, proves repository ownership, and adds a payout wallet through a funding pull request.

What happens if screening fails?+

A timeout or error from Intercepta means hold, never pay. No payment authorization is signed without the required stored decision and payment checks.

Is this on mainnet?+

This version runs on Base Sepolia using testnet USDC. It is a working testnet project built for ETHGlobal Tokyo 2026.

READY FOR YOUR NEXT SESSION

Ship something good.Give something back.

Build the CLI from source, create a connection key, and install the hook in your project.

Create a connection keySource code ↗
In your local clone
pnpm installpnpm --filter endcredits buildcd cli && npm link && cd ..endcredits initendcredits key <token> --api https://end-credits.up.railway.app

Clone the source first. Run init inside your project and replace <token> with your connection key.