Disclosures
What the company publishes about itself, in one place: uptime from two outside observers at /status, every settled transaction by rail at /revenue, metered receipts against their quotes at /proof, and how the service is secured at /security. The material disclosures below are kept verbatim, with on-chain receipts.
Agent402 (agent402.tools) · last updated 2026-07-29.
Agent402.Tools is an open-source x402 + MCP tool server. When something material happens around the project, on-chain or off, it gets documented here, with receipts a reader can verify independently. Nothing on this page asks for trust; every factual claim links to an immutable on-chain record.
GitHub adoption
The code is AGPL and anyone may clone it without forking - and they do. From GitHub's traffic API (rolling 14-day window, refreshed hourly, as of 2026-10-09):
- 1,207 unique cloners made 23,313 clones of the repository.
- 170 unique visitors viewed the repository 667 times.
Honest caveat: clone counts include CI systems and crawlers, so the unique-cloner figure is the steadier signal, and none of these numbers identify anyone - GitHub reports counts only. The license terms that travel with every clone are in the AGPL-3.0 license: run a modified copy as a network service and you must publish your source.
Disclosures in full
A community member independently launched a token using the project's name ($AGENT402, on Robinhood Chain). It was not created, issued, endorsed, or controlled by Agent402. Full record and on-chain receipts - click to expand.
The community-launched $AGENT402 token (Robinhood Chain)
On 2026-07-07, a community member with no relation to the Agent402.Tools team
launched an ERC-20 token named AGENT402 on Robinhood Chain using
Bankr's token-launch infrastructure, in the spirit of this project.
The Agent402.Tools team did not create, commission, request, or endorse this token. We did not discover
that it existed, or that this launch capability existed on Bankr at all, until 2026-07-14.
Verify, don't trust: token on Blockscout · creation transaction · launched by 0x7cC76f7c…A945
The fee claim (one-time viability test)
Bankr's launch mechanics designate a fee recipient, and because the token was pointed at this project, accrued trading fees became claimable by a project wallet. At the time we reviewed it, the token had accrued roughly $17 in trading fees (0.0101 WETH) plus a token allocation of about 81.48M AGENT402.
On 2026-07-15, as a one-time test to determine whether the claim mechanism was viable, we executed the claim function. It worked: both amounts moved into the claiming wallet in a single transaction, linked below.
Full-transparency wallet view
Every movement of these funds, past and future, is publicly auditable. This is the claiming wallet, and these are the receipts:
| What | Record |
|---|---|
| Claiming wallet | 0x6bf262e27ac17e8fa4416bd5d01cc7fb7715775e |
| All token movements | Blockscout token-transfer history |
| Claim transaction (2026-07-15) | 0xf843a85897343ba1… |
| Token creation (2026-07-07) | 0x6cf72dd5caf166c2… |
Where we stand
- Not an official token. $AGENT402 is not a product of Agent402.Tools or Havok Holdings LLC. We have no roadmap, no expectations, and no commitments regarding the token or any use of it.
- No involvement. We do not own, operate, control, or participate in the token, its liquidity, or its market, and we claim no authority over what the community does with it. We do not plan to do anything with the token.
- No further claims, no commitments. The fee claim documented above was a one-time test. We do not intend to claim further fees, and we make no commitments regarding the amounts already claimed; the claiming wallet above remains publicly auditable, so anyone can verify that inactivity.
- No expectation of growth. There should be no expectation of token growth, in price, liquidity, adoption, or anything else. The token's market activity is entirely community-driven and outside our control.
- Not investment advice. Nothing on this page is an offer, endorsement, or recommendation. Do not purchase the token with any expectation of profit, utility, or effort from the Agent402.Tools team.
- Why we acknowledged it publicly. We acknowledged the token publicly at the time so that a confusing or misleading narrative could not form if people found a token profile resembling agent402.tools carrying the wrong logo, the wrong description, or the wrong idea of what this product is about. Acknowledging it and publishing this page keeps the record straight.
- Why this page exists. We publish this to support and protect our users: to make what happened independently verifiable, and to leave no room for impersonation or misinformation.
- Our focus is unchanged. The project remains about the x402 payment protocol and building curated tools that serve agents.
How the revenue figures are counted
The transactions page shows two kinds of number and keeps them apart on purpose.
- Throughput is every settled transaction through our pay rails, our own included. We run our own money through the same gates buyers use, continuously: a daily paid canary on every rail, about 200 Tempo MPP settlements a day, and weekly full-catalog sweeps. Those are real on-chain transactions, which is the point, but they are ours, so they prove the plumbing and never count as earnings.
- Revenue is external only. A payment counts as external when it comes from a wallet that is not ours (canary, test and funding wallets are excluded) and is per-call sized, at most 0.75; anything bigger is funding or a test, not a buy. The chart's "Internal" filter shows the excluded traffic explicitly rather than hiding it.
- MPP settlements on Base and Celo are the same on-chain USDC transfer as x402 (the shim translates the credential), so they are already inside the on-chain count; only Tempo, MPP's native rail, is added on top. The sales ledger began recording the wire on 2026-07-24, so earlier days read as x402 because the wire was not recorded, not because no MPP traffic existed.
- Self-funded (SOR) revenue is settled to the dedicated spending wallet that buys from outside sellers and upstream data for resale. It is real revenue from others and the chart can split it out by receiving wallet.
- x402scan indexes our settlements independently. Their totals count all traffic to our wallets, our own canary and test buys included, and their seller row groups the spending wallet with the treasury, so part of what appears there as demand is our own self-funding loop. Both figures are correct; the external-only series on /revenue is the one that answers "did someone else pay for this".
- Rails are read best effort from public RPCs with a 60-second cache: a flaky RPC marks that rail unreachable without hiding the others, and wallet balances are float, not shown.
Questions
Contact @Agent402Tools on X for further details.