Skip to content
Menu

agentpay

AI Agents

Is this your project? Claim and verify →

AgentPay - The economic-intelligence layer for AI agents — an x402 gateway that prices, caps, and receipts agent data spend. 17 free tools + verified_route, the buyer-side x402 trust oracle. USDC on Base or Stellar.

What HEY knows

Building
Shipping consistentlyShipping: 5 meaningful events in 30 days; latest ship 6 days ago. Evidence Source

Build Momentum 48How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 2 commits · · Code activity

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts agentpay on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me agentpay’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 8 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 5 meaningful events in the last 30 days, the newest 2026-10-13.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 2 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 4 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 25 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 2 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 4 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 25 commits+4 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 2 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in romudille-bit/agentpay.

This week HEY looked inside 1 of 2 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:19d63ad3… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about agentpay — as of 2026-10-19

Is agentpay still being built?
DerivedShipping: 5 meaningful events in 30 days; latest ship 6 days ago. Evidence
What did agentpay ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 2 commits — Code activity, 6 days ago. Evidence
What does HEY not know about agentpay?
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 4 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in romudille-bit/agentpay.

    This week HEY looked inside 1 of 4 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 4 commits (opens in a new tab)

  2. Code changes, week of 2026-09-28 – 2026-10-04 · 25 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in romudille-bit/agentpay.

    This week HEY looked inside 3 of 25 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 25 commits (opens in a new tab)

  3. Code changes, week of 2026-09-21 – 2026-09-27 · 21 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in romudille-bit/agentpay.

    This week HEY looked inside 1 of 21 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 21 commits (opens in a new tab)

  4. Code changes, week of 2026-09-14 – 2026-09-20 · at least 14 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in romudille-bit/agentpay.

    This week HEY looked inside 1 of 14 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 14 commits (opens in a new tab)

  5. agentpay-x402 0.5.1

    GitHub releaseSource verified

    agentpay-x402 0.5.1

    View evidence: agentpay-x402 0.5.1 (opens in a new tab)

  6. Code changes, week of 2026-09-07 – 2026-09-13 · at least 33 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    30 active days in romudille-bit/agentpay.

    This week HEY looked inside 3 of 33 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 33 commits (opens in a new tab)

  7. agentpay-x402 0.5.0 — Stacks sBTC on mainnet

    GitHub releaseSource verified

    Stacks sBTC on mainnet. pip install "agentpay-x402[stacks]" and the one-liner quickstart(stacks_key="…", prefer_chain="stacks") pay tools in sBTC against agentpay.tools — sign-don't-broadcast, hard USD cap, receipts chain-verified on the public ledger. Three mainnet receipts… Show all
    • Stacks sBTC on mainnet. pip install "agentpay-x402[stacks]" and the one-liner quickstart(stacks_key="…", prefer_chain="stacks") pay tools in sBTC against agentpay.tools — sign-don't-broadcast, hard USD cap, receipts chain-verified on the public ledger. Three mainnet receipts settled before release (30689b5e…, d1de1a79…, 59ce7014…); the daily flagship agent runs on the same rail. Everything below is the M2 hardening that went in between 0.4.0 (testnet) and this release. Fixed
    • Stacks confirmation never seen — the gateway polled Hiro at /extended/v1/tx…
    View evidence: agentpay-x402 0.5.0 — Stacks sBTC on mainnet (opens in a new tab)

  8. Code changes, week of 2026-08-31 – 2026-09-06 · at least 6 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    34 active days in romudille-bit/agentpay.

    This week HEY looked inside 1 of 6 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 6 commits (opens in a new tab)

  9. agentpay-x402 0.3.0 — payment-safety hardening

    GitHub releaseSource verified

    agentpay-x402 0.3.0 — payment-safety hardening Breaking release. The buyer SDK now refuses to overspend, double-pay, or trust a hostile 402. It comes out of the July 2026 gateway code review. If you relied on the budget cap silently clamping the amount you pay, you'll now get a… Show all
    • agentpay-x402 0.3.0 — payment-safety hardening Breaking release. The buyer SDK now refuses to overspend, double-pay, or trust a hostile 402. It comes out of the July 2026 gateway code review. If you relied on the budget cap silently clamping the amount you pay, you'll now get a BudgetExceeded exception instead — that's the one behavior change to handle on upgrade. pip install --upgrade agentpay-x402 or: agentpay-x402[base] Why upgrade Every change closes a way an agent's wallet could have been drained faster than its budget allowed. Breaking
    • The budget cap…
    View evidence: agentpay-x402 0.3.0 — payment-safety hardening (opens in a new tab)

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about agentpay? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

11 changes on HEY’s record for agentpay: 3 releases · 1 build pace change · 7 weeks of code pushed.

All 11 changes for agentpay →

The full change record holds 4 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 58m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 1h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 2d ago.

Code and packages

  • Repository detailsMeasuredRead 6h ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources