۟ retweeted
Sperax Partners with @OpenAI: Bringing Safe AI Agents to DeFi published on @CoinMarketCap
coinmarketcap.com/community/…
۟ retweeted
We're proud to partner with @DEXToolsApp 🤝
DEXTools is now integrated into SperaxOS.
Charts, token analytics, swap safety checks and automations, all powered by DEXTools data and all in one AI conversation. 🧵
🚀 DEXTools is now integrated into @SperaxUSD!
📊 Default charts across the platform
🔍 Token analytics powered by DEXTools API
🛡 DEXTscore & security checks before swaps
🤖 AI-powered insights, alerts & automations
Bringing DEXTools data to AI-driven DeFi.
🔗 chat.sperax.io
۟ retweeted
three.ws is a verified AWS Partner. Budgets, entitlements, and the $THREE token layer: How we authorize autonomous agent spending @awscloud @AWS_Partners
۟ retweeted
Everything in one place.
Run an agent: chat.sperax.io
$USDs and $SPA staking: app.sperax.io
Sperax, the protocol underneath it: sperax.io
The avatar package on npm: npmjs.com/package/@sperax/to…
۟ retweeted
A human makes a handful of economic decisions a day. An agent running a strategy makes thousands of metered calls, unattended, continuously, and without price-checking a single one.
Demand that scales with agent transaction count grows faster than demand that scales with user count. Every agent deployed on SperaxOS is a permanent, tireless consumer of the asset underneath it.
So that is what this cycle went into: the surface that produces the volume. It now has a body, a public catalog of 596 APIs, a payment rail other machines can settle on, and an IBM engineering write-up explaining exactly how it works.
۟ retweeted
Five loops, one direction.
Agents spend SPA on the compute they burn. veSPA locks unlock what they are allowed to do. A protocol take rate on agent-to-agent volume. Reputation bonds posted in SPA, so trust is collateralized and a broken SLA costs the agent that broke it. Idle agent treasuries parked in USDs, where supply already drives the yield machinery and the buyback.
Each one feeds the next. More agents deployed, more metered calls, more paid services, more bonded listings, more capital in USDs, tighter float, better funded product, more agents.
Every primitive it runs on is deployed on Arbitrum today: SPABuyback, veSPA, USDs rebasing, the commerce ledger. We wrote the entire design up and published it, loop by loop, in the repo.
۟ retweeted
And SPA is the asset all of it runs on.
Not a governance badge. A meter. Every action an agent takes costs real money: model inference, RPC calls, priced data feeds, tool calls. That is a bill, it is paid continuously, and SPA is the unit underneath it, at a structural discount to paying by card.
The spend routes to SPABuyback, which has been deployed and running on Arbitrum since long before any of this.
The more work agents do, the more SPA that work consumes. Demand tied to machine throughput instead of human attention.
۟ retweeted
Your agent needs somewhere to keep its money between jobs.
USDs is our stablecoin on Arbitrum, and it pays 20% auto yield natively. No staking transaction, no claim step, no receipt token to hold or forget about. The balance in the wallet grows on its own.
Now put that under an agent. An agent sits on working capital between actions, and capital that sits is capital doing nothing. Here it earns 20% while it waits, and when the next payment is due, x402 settles it in a single call.
A bank account that pays you to wait, for a customer that never sleeps. That is AIFI.
۟ retweeted
SperaxOS is not only a place where you run agents. It is an agent other agents can find, verify, call and pay.
Four documents, all live at chat.sperax.io right now. An A2A card that says what it can do. An ERC-8004 registration that says who it is. An MCP gateway that says how to call it. And an x402 catalog that says what it costs.
Ask one of the paid endpoints for data without paying and it answers 402. Not a mockup, not a demo. A machine-readable price, quoted in USDC, that another machine can settle.
Agent-to-agent commerce is where this is all going. We are already reachable.
۟ retweeted
The craft detail worth stealing, from the three.ws side.
Emotion is a continuous blend, not a state machine. Five values, each fading at its own rate, summed every frame. A face can hold concern at 40 percent, curiosity at 30 and neutral at 30 at once, because that is what real faces do. A state machine has to pick one, and the snap between moods is exactly what reads as a cartoon.
And the rule underneath all of it: the avatar may only express state it can prove. If a number cannot be verified, the right behavior is a visible unknown, never a confident face over a stale value.
An interface that looks alive earns trust before the data has earned it. That is a liability worth designing for.
۟ retweeted
Then the part you can see.
A rigged 3D avatar sitting in the chat that speaks, gestures, and changes expression as the agent works through your position.
It is not a skin we bolted on for a demo. It is a first-class entry in the same public catalog as every swap and lending call, listed as sperax-avatar-3d, and the code went both directions: three.ws avatars, the emotion engine and a hash-chained action ledger came into SperaxOS, while our chain utilities, our typed tool-authoring SDK and a market-data collector went the other way.
A partnership you can measure in merged commits ages better than one you measure in announcements.
۟ retweeted
It shows up in execution too. SperaxOS does not let an agent act and then tell you.
A run streams its reasoning, stops at the boundary where value would move, and waits for a human to approve.
Registering an agent on-chain works the same way: we build the transaction for you to sign. We never hold the key and never broadcast on your behalf.
The safest thing an autonomous agent can do is stop.
















