Skip to content
Menu

suwappubot

AI Agents

Is this your project? Claim and verify →

Cross-chain DEX infrastructure for humans and AI agents — swap tokens across 14 chains via Telegram, WhatsApp, Discord, or a programmatic REST/MCP/A2A API.

What HEY knows

Building
Last shipped 19 days agoActive: 2 meaningful events in 30 days; latest ship 19 days ago. Evidence Source

Build Momentum 28How it is measured

Latest ship
Code changes, week of 2026-09-28 – 2026-10-04 · 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.

Latest change
Fact17 days ago: Links the official site declares changed: 4 added, 0 removed. Added docs link: suwappu.bot/docs/api-reference/registration.md; docs link: suwappu.bot/docs/api-reference/swap-history.md; docs link: suwappu.bot/docs/billing/agentic-payments.md; and 1 more. Evidence Source
FollowCreate alertTerminal previewView latest ship
Share

Follow puts suwappubot 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 suwappubot’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
Unknown3 gaps: Published packages (not enough yet), API description (source unavailable), Official site changes (stale). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 7 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
Active.
“Active” by the activity rule: 2 meaningful events in the last 30 days, the newest 2026-09-30.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 133 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 77 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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.
Source37 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-28 – 2026-10-04 · 2 commitsCode changes, week of 2026-09-21 – 2026-09-27 · 133 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 77 commits+7 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-09-28 – 2026-10-04 · 2 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in 0xsoftboi/suwappubot.

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:3952820c… · 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 suwappubot — as of 2026-10-19

Is suwappubot still being built?
DerivedActive: 2 meaningful events in 30 days; latest ship 19 days ago. Evidence
What did suwappubot ship last?
FactCode changes, week of 2026-09-28 – 2026-10-04 · 2 commits — Code activity, 19 days ago. Evidence
What does HEY not know about suwappubot?
Unknown3 gaps: Published packages (not enough yet), API description (source unavailable), Official site changes (stale). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

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

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in 0xsoftboi/suwappubot.

    This week HEY looked inside 4 of 133 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

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

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

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in 0xSoftBoi/suwappubot.

    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-09-07 – 2026-09-13 · at least 77 commits (opens in a new tab)

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

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in 0xSoftBoi/suwappubot.

    This week HEY looked inside 10 of 220 commits to see what changed: 3 changed code, 7 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 14 automated commits (bot accounts or a repeating scripted message) not counted.

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

  4. Discovery & protocol hygiene

    Feature releaseSource linked

    MCP server now negotiates protocolVersion on initialize ( 2024-11-05 , 2025-03-26 , 2025-06-18 ) instead of assuming one. New /.well-known/ai-catalog.json (ARD v0.9 draft) for machine discovery, mounted next to the agent card. Agent card now declares the a2a-x402 payment… Show all

    MCP server now negotiates protocolVersion on initialize ( 2024-11-05 , 2025-03-26 , 2025-06-18 ) instead of assuming one. New /.well-known/ai-catalog.json (ARD v0.9 draft) for machine discovery, mounted next to the agent card. Agent card now declares the a2a-x402 payment extension in capabilities.extensions . POST /v1/agent/swap/simulate + simulate_swap MCP tool: a zero-funds-move dry run with balance, allowance, gas, revert, and slippage checks. Jul 2, 2026 Feature

    View evidence: Discovery & protocol hygiene (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 suwappubot? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

7 changes on HEY’s record for suwappubot: 1 release · 2 official source changes · 4 weeks of code pushed.

  • Official source changed17d ago · 2 official source changes

    Links the official site declares changed: 4 added, 0 removed. Added docs link: suwappu.bot/docs/api-reference/registration.md; docs link: suwappu.bot/docs/api-reference/swap-history.md; docs link: suwappu.bot/docs/billing/agentic-payments.md; and 1 more

    See the change Source ↗

  • Code pushed19d ago · recorded by HEY 15d ago

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

    See the change Source ↗

  • Code pushed22d ago

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

    See the change Source ↗

  • Code pushed1mo ago

    Code changes, week of 2026-09-07 – 2026-09-13 · at least 77 commits

    See the change Source ↗

  • Code pushed1mo ago

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

    See the change Source ↗

All 7 changes for suwappubot →

The full change record holds 39 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 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 2h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1y ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 2h ago.
  • API descriptionSource unavailableThe API description it links could not be read.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 19h 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

32 more sources (docs)

Security context: a published security contact. An audit shows an audit took place; it is not a guarantee of safety.