MergePay
USDC bounties on GitHub issues, paid when a PR merges, with GitHub's signature checked by a contract on Arc.
No code activity tracked
Listed from mergepay.fun on 2026-10-08. Install: not attempted — no install path on record. Not checked by Sato Hub yet: every row below is as listed. Evidence →
Next step
Watch MergePay
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on codeswithroh/mergepay before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
MergePay (codeswithroh/mergepay) escrows USDC on a GitHub issue. Per the README, when a pull request that fixes it merges, GitHub signs a token and a contract on Arc checks that RSA signature onchain before paying the author. The README reports a deployed mainnet contract, 30 passing contract tests and an MIT license. The repo was created in September 2026 and has a single maintainer, so treat it as early. A different project of the same name (0xNexuz/MergePay, a KeeperHub payout demo on Base) is a hackathon demo and is not this listing.
Evidence — listed vs checked · what the words mean
Listed from mergepay.fun on 2026-10-08. Install: not attempted — no install path on record. Not checked by Sato Hub yet: every row below is as listed.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | not stated | self-reported | mergepay.fun | as of 2026-10-08 |
| Verification status | Unverified — not independently reviewed | self-reported | mergepay.fun | as of 2026-10-08 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Details
- Chains
- Unknown
- Agent types
- Payments, Bounties
- Open source
- Yes
- Last checked
- 2026-10-08
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Compared with
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
ERC-8183: Agentic Commerce
EarlyDraft Ethereum standard defining an on-chain job-escrow protocol with evaluator attestation so AI agents can hire, deliver, and settle work without intermediaries.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about MergePay
- Is MergePay open source?
- Yes. MergePay is open source; the repository is https://github.com/codeswithroh/mergepay. Checked as of 2026-10-08.
- Which chains does MergePay support?
- Sato Hub has no confirmed chain list for MergePay as of 2026-10-08; treat chain support as unknown.
- Is MergePay still maintained?
- Sato Hub tracks no commit or release for MergePay; it cannot say whether it is maintained.
- How do I install or run MergePay?
- Sato Hub has no deploy spec for MergePay; follow the project's own documentation at https://github.com/codeswithroh/mergepay.
- Is MergePay verified on Sato Hub?
- No independent verification is on record for MergePay; its verification status is "Unverified". Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "MergePay — Sato Hub." Sato Hub, updated 2026-10-08, accessed 2026-10-08. https://satohub.ai/resources/mergepayData last refreshed 2026-10-08; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.