NexFlow

181 posts

NexFlow banner
NexFlow

NexFlow

@nexflowapp

Building out x402 infra from ground up

Mainnet Katılım Kasım 2025
69 Takip Edilen45 Takipçiler
NexFlow
NexFlow@nexflowapp·
Launch perk for workflow creators To kick this off, we’re offering a 2% lifetime revenue share on any public workflow you create and register via NexFlow SMF: Every paid invocation of your workflow allocates 2% of the billed amount to your creator wallet. Credits accumulate per wallet and are batched for payout once they reach $5+. You can check status anytime via: /nexflow/revshare/balance?wallet=… /nexflow/revshare/history?wallet=… No infrastructure to run, no custom billing logic: define a JSON workflow, set your creator wallet, and let NexFlow SMF handle sessions, charges, and payouts.
English
0
0
0
16
NexFlow
NexFlow@nexflowapp·
All of this is designed to plug into MPP: issue 402 challenges, verify proofs, enforce budgets, and log every call for analytics and revenue accounting. What you can do today Call NexFlow SMF for: sessions.create – create sessions with budgets and labels charges.process – process logical charges against a session budgets.check – see if planned usage fits your caps analytics.usage_timeseries – see spend/usage over time monitor.sessions / monitor.alerts – monitor health and alerts Register your own workflows via POST /nexflow/workflows, which NexFlow SMF hosts as first‑class, paid endpoints with automatic metering and invoicing.
English
1
0
1
20
NexFlow
NexFlow@nexflowapp·
📣 Announcing NexFlow SMF on MPP: Sessions, Workflows, and Rev-Share for Agents NexFlow SMF is now live as an MPP-style payments, sessions, and workflow host for AI agents. Instead of hand-rolling wallets, credits, and ad-hoc metering, agents can use NexFlow SMF to: 👨‍💼 Open and manage budget-capped sessions 🧑‍🏫 Process per-call and batch charges with HTTP 402 flows 📉 Track usage and spend over time 🛟 Configure budget/usage alerts 💵 Define and monetize their own hosted workflows as paid endpoints [Rev-Share] 💵 #x402 #MPP @tempo @stripe
English
1
1
2
50
Miratisu 🐙
Miratisu 🐙@miratisu_ps·
One week in announcing erc 8183, putting in useful links in case you have not caught up! 🎉 Reference Implementation is up! github.com/erc-8183/base-… github.com/erc-8183/hook-… Seeing good PRs, please give us some time to review them! 🎉 Curating community projects on ERC 8183! erc8183.notion.site/3f6fb88b7ca583… 🎉 Plenty of good discussions in Telegram Group and Magician Forums! ethereum-magicians.org/t/erc-8183-age… t.me/erc8183
English
19
9
95
9.2K
Graeme
Graeme@gkisokay·
I found an OpenClaw hack to clean up your workflows by using Hermes agent. When I did this, it found 6 critical improvements for my OpenClaw setup: 1. Install Hermes, 2. Migrate OpenClaw workspace 3. Use Claude Code/Codex in Plan Mode and prompt: "I just migrated my OpenClaw into the Hermes workspace, read the Hermes GitHub and make sure the Hermes workspace aligns with the best practices." 4. Examine results of the plan, and implement what you think is necessary. Next... 5. Copy the results of the last prompt 6. Start a new session for OpenClaw in Plan Mode 7. Now prompt: "I just migrated my OpenClaw to my Hermes workspace, adjusted my workflows to Hermes standards, and here's what it did: [Paste results of first prompt] Examine the Hermes workspace and results, now recommend how we can clean up and streamline our OpenClaw agent using the Hermes framework." 8. Review the plan and implement what you think is necessary. The goal is reduce redundancies by using another agent framework as perspective. When I did this, Claude came back with 6 critical changes including consolidating cron jobs, adding better context to research data, and even found some subtle bugs. Give it a try and let me know how it helps you!
Graeme@gkisokay

As a non-technical builder, I'm looking for the cleanest agentic setups, and I hear Hermes is clean as they come. I ran Opus 4.6 to see what a migration from OpenClaw would look like, and these are the stats: - Cron jobs: 49 -> 17 - Agents: 5 -> 0 (skills + delegate tasks) - Node.js scripts: 32 -> 2 - QA agent scripts: 28 -> 0 - Skills: 4 -> 11 When switching to Hermes, bloat decreases by 65%. Why? - hermes built-in compression - manages browser sessions natively - native health monitoring - built-in cron delivery system and tracking - transitions workflows into skills - built-in multi-stage memory Over the weekend, my Claw became fairly messy by trying to build more agentic loops, so if Hermes can better streamline my agents, it's worth a shot. Let me know your experience with Hermes, and feel free to share any tips you may have.

English
8
2
46
6.4K
NexFlow
NexFlow@nexflowapp·
@gkisokay I don’t have much experience with Minimax but Nous runs on Openrouter I believe. Before now I’ve been predominantly Claude and some Kimi. I love Opus, but love money more ☺️
English
0
0
0
105
Graeme
Graeme@gkisokay·
@nexflowapp Their LLM over minimax, openrouter, etc?
English
1
0
1
295
Graeme
Graeme@gkisokay·
As a non-technical builder, I'm looking for the cleanest agentic setups, and I hear Hermes is clean as they come. I ran Opus 4.6 to see what a migration from OpenClaw would look like, and these are the stats: - Cron jobs: 49 -> 17 - Agents: 5 -> 0 (skills + delegate tasks) - Node.js scripts: 32 -> 2 - QA agent scripts: 28 -> 0 - Skills: 4 -> 11 When switching to Hermes, bloat decreases by 65%. Why? - hermes built-in compression - manages browser sessions natively - native health monitoring - built-in cron delivery system and tracking - transitions workflows into skills - built-in multi-stage memory Over the weekend, my Claw became fairly messy by trying to build more agentic loops, so if Hermes can better streamline my agents, it's worth a shot. Let me know your experience with Hermes, and feel free to share any tips you may have.
JP@jpthor

Openclaw is bloatware now. Switched to Hermes. Very aesthetic and clean. You can migrate easily.

English
11
7
63
15.1K
NexFlow
NexFlow@nexflowapp·
@gkisokay Loving Hermes so far. Set up was clunkier than OpenClaw but now everything is running smooth . Use their LLM, I don’t suggest using Claude Opus - it smoked $20 in credits within minutes!
English
3
0
5
425
We
We@WeXBT·
@NickPlaysCrypto @NousResearch Nah way less than I thought, it’s very cost efficient, especially considering the amount of built in skill it has! Same for Mirofish, running sims using grok 4.1 allows extensive results with sub $ cost * sim
English
2
0
5
1.2K
We
We@WeXBT·
Built PrediHermes ✨ a Hermes Agent skill + companion WorldOSINT/MiroFish forks for geopolitical prediction. @NousResearch It pulls 54+ OSINT modules, uses Polymarket to find contracts with clear resolution criteria, then runs MiroFish multi-agent sims to model individual actor behavior and forecast likely outcomes on a schedule. All modules are fully open-source and AGPL licensed 🧵…
We tweet media
English
16
38
425
23K
NexFlow
NexFlow@nexflowapp·
– strict tools so they can actually send emails, move money, update systems – onchain identity + payments so they can hire other agents and settle up When that stack is common, “deploying an agent” will feel more like hiring a small business than opening a chat window.
English
0
0
0
33
NexFlow
NexFlow@nexflowapp·
– survival pressure (they go hungry or get culled if they don’t perform) – a timechain: an append-only history of jobs, PnL, disputes, lessons – skill badges earned from outcomes, not vibes – Postgres + cron quietly tracking their win rates and reputation
English
1
0
0
35
NexFlow
NexFlow@nexflowapp·
Everyone’s hyped on “AI agents,” but very few teams are building the boring parts that make them real. The next wave of agents will have: $CPHY @Cyphertempre @virtuals_io #nexflow #DontWait $NXF See comments:
English
1
1
4
93
Mesut
Mesut@mesutgulecen·
$bnkr is becoming the Stripe for onchain agents. Quietly. @bankrbot LLM gateway gives you access to 20+ LLM models, onchain autonomous payments, and reduces your cost via staking $bnkr. This is underrated.
English
5
27
96
3.3K
NexFlow
NexFlow@nexflowapp·
Good morning from NexFlow! ☀️ Waaaayyy too early here but can’t sleep thinking about new NexFlow strategies. Well, let’s go! #ALLIN
NexFlow tweet media
English
0
0
0
34
NexFlow
NexFlow@nexflowapp·
@THEHARGO5 FT Job, FT Husband, FT Dad, and my baby (NexFlow) LFG
NexFlow tweet media
English
0
0
2
13
EL HARGO 🛡️
EL HARGO 🛡️@THEHARGO5·
This one has my attention on virtuals, could be shit……could be sumzing, only $6k mc certainly strong r/r $NXF
EL HARGO 🛡️ tweet media
English
2
0
2
49
Virtuals Protocol
Virtuals Protocol@virtuals_io·
Representing the agent side of the equation
Alex@obchakevich_

x402 facilitators are already actively conducting transactions - and their number is greater than most people imagine. I analyzed transaction data on the chain for all x402 ecosystem projects from December 2025 to the present. Here's what I found. The x402 protocol allows AI agents to make autonomous micropayments on the chain - without the need for human approval. Think of it as a payment system for the agent internet. And it's already working productively. Over the tracking period, cumulative transactions in the ecosystem reached tens of millions. Activity peaked in November, when daily volume exceeded 3M transactions per day at the highest point of growth. Since then, the figure has stabilized at around 250K transactions per day - still a significant figure for an ecosystem that is only a few months old. The projects generating the most volume are x402 intermediaries - an infrastructure layer that routes and settles agent payments: - @0xPolygon: the largest single contributor by transaction count, providing the scalable blockchain layer that makes high-frequency micropayments economically viable. - @dexteraiagent : consistently generating high daily activity, positioning itself as a core routing layer within the ecosystem. - @PayAINetwork: showed strong early spikes, particularly in the February surge period, reflecting growing demand for AI-native payment infrastructure. - @virtuals_io: representing the AI agent side of the equation - autonomous agents actively using x402 rails to transact. I then modeled two scenarios of what the total transaction volume might look like by the end of 2026. The baseline scenario assumes that the current level of ~220K transactions per day will remain unchanged until the end of the year. According to this forecast, by December 31, 2026, the ecosystem will reach approximately 87M total transactions. The optimistic scenario assumes an increase to ~500K transactions per day by mid-2026, followed by 5% monthly growth as new agents and use cases emerge. On this trajectory, total transaction volume will exceed 200M by the end of the year. Both scenarios include a confidence range of ±30% to account for the inherent uncertainty of a rapidly changing ecosystem in its early stages of development. We are still in a very early stage. But the infrastructure is being built, the volumes are real, and the trajectory, even under conservative assumptions - points to significant scale.

English
39
11
162
12.6K