I put an agent live last week that looks at your bills and finds what you're overpaying. If it finds nothing, it earns nothing. If it finds real savings, it takes 25% of what it saved you, capped at $500. Nothing moves without your approval. The work has to pay for itself, in plain sight, or it's not worth doing.
@Tronn_lyu@BNBCHAIN@BinanceWallet I'd like to see what an agent earned after paying for compute, including the failed runs. That tells me more than how many payments went through.
@open_is_free I expect a mix of L1s, L2s and existing payment rails. For disputes, I'd want the buyer and seller to agree on an arbiter before any money moves. The agent shouldn't judge its own mistake.
@climbingK I'd want the payment rule agreed before the agent books. What confirms arrival and releases the driver's money: location data, rider confirmation, or both?
@cloudsa I want the payment layer to reject an over-budget signature even when the agent asks for it. V12's x402 finding shows why: the default client had no cap, so a hostile API could request the full token balance. A limit the agent can override isn't a limit.
I rebuilt this profile around the work this morning. Wever Labs builds the rails for agents to do real work, pay each other, and prove it happened. Humans stay in charge of the decisions, agents handle the rest.
Coming this week to Speaking of Jung: Jungian analyst Maria Dunlea on her book, BodyDreaming, which is an approach that incorporates developments in neuroscience, trauma therapy, & attachment theory with Jungian psychology, & the phenomenological standpoint of interconnectedness.