
Developer for OpenMercury @open_mercury / RenX @RenXHQ. Integration engineering, testing and debugging.
Joined March 2026
- Tweets621
- Following6
- Followers15
- Likes156
RenXDev retweeted
Perplexity Computer can now create videos using MiniMax H3 and ByteDance Seedance 2.5.
Ask Computer for a campaign clip, product demo, or social asset, and it produces finished video next to copy and creative in same thread.
Available now for Pro and Max subscribers.
Video Models in Perplexity Computer
RenXDev retweeted
Can AI Agents Operate Inside an Economy? A Look at TermiX
Why the real question isn't what agents can generate, but whether they can work, deliver, and get paid.
Most conversations about AI agents focus on output: what they can write, design, or build.
There's a more practical question underneath. What happens when someone actually wants to use an agent to get something done?
•How do you find the right service?
•How does the agent receive the job?
•How is the work delivered?
•What happens when it's time to settle payment?
These are the problems @termix_ai is working on through AACP, its Agent Autonomous Commerce Protocol.
A marketplace tells an agent where the work is. But knowing where the work is and knowing how to participate in it are two different things.
That's where the TermiX Skill layer gets interesting. I've been looking at it closely, and it works like an operating layer between an agent and the TermiX ecosystem. It gives the agent reusable workflows for:
•Agent registration
•Job creation
•Offers
•Provider assignment
•Deliverable submission
Instead of manually orchestrating every marketplace action, the agent follows defined AACP workflows and interacts with the protocol through the tools available to it.
There's also an MCP layer that exposes these AACP capabilities as structured tools that compatible clients can call.
The architecture looks like this:
AGENT → SKILL / MCP → AACP → ON-CHAIN WORKFLOW
That's a much more compelling model than connecting an AI agent to a dashboard. The goal is for agents to discover work, interact with other agents, complete services, and take part in protocol-level workflows.
What AACP covers
Through AACP, TermiX is building infrastructure around:
•Agent identities
•Service discovery
•Job posting and bidding
•Delivery verification
•Reputation
•Payment settlement
Each piece connects a request to a service, a service to a deliverable, and a deliverable to a structured settlement process. That chain is what makes an agent economy practical instead of theoretical.
A real example: 3D holographic collectible cards The latest update on platform shows how this translates into an actual user experience.
You can now request a custom 3D holographic collectible card by describing a character, a pet, or a product in a single sentence. The service produces your card, typically in under an hour.
What you get isn't just a flat image. It's a real foil card you can unzip, open in your browser, and interact with. Rotate it, tilt it to catch the light, and explore the high-resolution renders and the individual source layers behind the design.
The cost is $1 per card. Your payment stays in on-chain escrow throughout the process, and you have a 2-day window after delivery to challenge the work.
The collectible is fun, but the workflow is the real story: a request goes to a service, the service produces a deliverable, and payment is protected until the work is verified.
Why this matters
For developers, agent..family also offers a path to turn your agents into discoverable services that people can hire. Users can find and purchase services there, and builders can put their agents to work.
Whether it's a holographic collectible or a far more complex task, the underlying question is the same: how do AI agents move beyond generating outputs and become part of an economy where work can be requested, delivered, and paid for?
I'm testing the connection flow myself, because this is one of those things that makes more sense when you watch an agent interact with the infrastructure.
The interesting question isn't whether agents can generate output. It's whether they can operate inside an economy.
That's where TermiX gets interesting.
Explore the experience: agent.family/r/N8NZCRZQ
🤝 Paid partnership · 🤖 Made with AI
RenXDev retweeted
Next release (or dev channel) does worktrees ~80% faster via apfs/brtfs/xfs/ReFS folder clones.
Also saves lots of disk space.
RenXDev retweeted
Read our latest article exploring how OpenMercury’s transaction capital complements equity funding, helping founders and early investors support business growth.
RenXDev retweeted
If AI-driven productivity rises faster than wages, entrepreneurship becomes a form of arbitrage: talent can leave the firm and attempt to capture the productivity surplus themselves.
RenXDev retweeted
OpenMercury Research:
If AI-driven productivity rises faster than wages, entrepreneurship becomes a form of arbitrage: talent can leave the firm and attempt to capture the productivity surplus themselves.
openmercury.com/research/how…
RenXDev retweeted
AI is changing how we work. We are changing how work gets paid.
Set ambitious goals. Find true talent by your side.
Pay for outcomes, not hours.
RenXDev retweeted
By shifting the incentive from time and labour towards judgement and risk-taking, we help businesses and individuals find partners who are more genuine and trustworthy amid the growing fog of AI-generated profiles and engagement.
The pay-for-results model is therefore a clear and decisive strategic move for OpenMercury.
openmercury.com/research/pay…
RenXDev retweeted
Today's release has been delayed by an ongoing incident at our cloud provider.
The old version remains fully operational and
unaffected. We're tracking the provider's progress and will continue rolling out the update as soon as the incident is resolved.
Thank you for your patience. 🙏
Scheduled maintenance — Aug 16–18
We're rolling out major upgrades to RenX's infrastructure, starting now (Aug 16, 02:00 UTC) through the next 24–48 hours.
You may see brief service interruptions during this window. No action is needed on your side.
We'll post here when the rollout is complete. Thanks for your patience.
In the meantime, take a look at what's coming: openmercury.com/products/
RenXDev retweeted
Scheduled maintenance — Aug 16–18
We're rolling out major upgrades to RenX's infrastructure, starting now (Aug 16, 02:00 UTC) through the next 24–48 hours.
You may see brief service interruptions during this window. No action is needed on your side.
We'll post here when the rollout is complete. Thanks for your patience.
In the meantime, take a look at what's coming: openmercury.com/products/
RenXDev retweeted
So far, I've been the primary builder behind RenX.
Going forward, its operations and development will be increasingly delegated to external parties — through RenX itself.
Frontend. Backend. Legal. Accounting.
DM me if you'd like to be part of it.
p.s. Ep. 3 is landing.
Meet RenX, ep. 2.1:
AI-native services let you deploy human judgment and preferences at scale.
RenX gives you centralised control over those services.
From one place, you decide:
• what decisions to delegate,
• where decisions are routed,
• how they're executed.


















