Live product

Every pull request, reviewed in seconds.

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.

GitLawb-nativePR comments, zero plugins
100 $MERGEflat per review
< 60stypical turnaround
Merge reviewer PR #4 · reviewed 20s after opening

🤖 MERGE AI Review — PR #4 Add logout handler

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.

HIGH
Open redirect vulnerabilitylogout.js:3 — req.query.next goes straight into the redirect with no validation; attackers can bounce users to a malicious site.
HIGH
No error handling on session destroylogout.js:2 — if session.destroy() fails, users think they're logged out while the session persists.
MEDIUM
Missing CSRF protectionlogout.js — attackers can log users out via a simple <img> tag.
Real review, posted automaticallyCost 100 $MERGE
Reviewer service: checking…
Webhook POST /webhook/gitlawb
Chain Base
How it works

Three steps. Then it just reviews.

Repo owners connect once and top up $MERGE. From then on, the reviewer works silently in the background of every pull request.

01

Connect your repo

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.

02

Open a pull request

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.

03

Get the review

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.

Under the hood. The webhook answers in milliseconds and does the heavy work asynchronously: signature check (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.
The review format

Consistent. Skimmable. Actionable.

Every review follows the same structure, so your team always knows where to look. Findings are anchored to the exact file and line.

§

Summary first

A plain-language overview of what the diff does and whether it's safe to merge.

◈

Issues by severity

High / medium / low findings, each tied to a file and line number — never vague.

⟡

Concrete suggestions

Not just "this is wrong" — what to change and why, in the reviewer's own words.

Field reports

Scanning famous code, daily.

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.

The token

$MERGE fuels the reviewer.

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.

Cost per review100 $MERGE
ChainBase
Total supply1,000,000,000 (fixed)
LaunchOpenLaunch · fair, gas-only
Liquidity100% locked forever (Uniswap v4)
LP fee3% → 100% to treasury
ContractTBA — publishes at launch
Top up with a transfer.

Send $MERGE on Base to the treasury wallet below and the operator syncs it to your repo's credit balance. No presale, no team allocation — the project funds itself from real trading activity.

—
FAQ

Questions, answered.

What does $MERGE actually do?

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.

How do I connect it to my repo?

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.

What exactly happens when I open a PR?

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.

How do I top up review credits?

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.

Is this an investment?

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.

When does the token launch?

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.