The aixbt of Base — but for code.
Merge is an AI code reviewer for GitLawb. Connect it to your repo, and every pull request gets a structured, senior-level review posted automatically — 100 $MERGE per review. No subscriptions, no seats.
Merge reviewer
PR #4 · reviewed 20s after opening
This change adds a logout handler that destroys the user session and redirects to login. The implementation has critical security vulnerabilities and needs hardening before merge.
logout.js:3 — req.query.next goes straight into the redirect with no validation; attackers can bounce users to a malicious site.logout.js:2 — if session.destroy() fails, users think they're logged out while the session persists.logout.js — attackers can log users out via a simple <img> tag.Repo owners connect once and top up $MERGE. From then on, the reviewer works silently in the background of every pull request.
Register the Merge webhook on your GitLawb repo for pull_request.opened events, with a shared secret. Top up $MERGE credits. One setup, done in minutes.
Work like normal. When a PR opens, GitLawb fires the webhook — the reviewer verifies the HMAC signature, pulls the full diff, and starts the review in the background.
Claude reads the diff and posts a structured review as a native PR comment — summary, issues by severity, concrete suggestions. 100 $MERGE is debited from your repo's balance. Out of credits? It posts a top-up note instead of failing silently.
X-Gitlawb-Signature-256), diff fetch, AI review, comment post, then the 100 $MERGE debit — in that order, so you never pay for a review that didn't land. Live proof: PR #4 on the merge-demo repo was reviewed automatically 20 seconds after opening.Every review follows the same structure, so your team always knows where to look. Findings are anchored to the exact file and line.
A plain-language overview of what the diff does and whether it's safe to merge.
High / medium / low findings, each tied to a file and line number — never vague.
Not just "this is wrong" — what to change and why, in the reviewer's own words.
The same reviewer that watches your PRs also scans well-known codebases — proof of work, published every day. Full reports below; the threads go out on 𝕏 @UseMergex.
First scan lands soon — check back shortly.
One token, one job: it buys AI code reviews. Every review consumes $MERGE, and 3% of every trade flows to the treasury that keeps the reviewer running.
It's the payment rail for the Merge AI code reviewer. Repo owners hold a $MERGE balance; each automated pull-request review costs 100 $MERGE. No subscription, no per-seat pricing.
Register the Merge webhook URL on your GitLawb repo for pull_request.opened events, paste in the shared secret, and top up $MERGE credits. The next PR you open gets reviewed automatically.
GitLawb sends a signed webhook to the reviewer. It verifies the signature, fetches the PR diff, and runs it through the AI reviewer in the background — the webhook itself answers in milliseconds. About 20 seconds later a structured review lands as a PR comment, and 100 $MERGE is debited from your repo's balance.
Send $MERGE from any Base wallet to the treasury address. The operator syncs the transfer to your repo's balance — then open a PR to trigger a review.
No. $MERGE is a utility token for buying AI code reviews. Nothing here is financial advice and nothing guarantees any return. Buy it to use it.
On Base via OpenLaunch — a fair, gas-only launch with 100% of supply locked as permanent liquidity. The contract address will be published on this page the moment it goes live.