Replying to @BuildOnCircle
One balance per asset across chains is a big deal for wallet UX. In the 1Shot passkey wallet we use CCTP so users never have to think about which chain their USDC is on, and EURC getting the same treatment opens that up for euro users. Do Nanopayments cover EURC at launch?
Replying to @gaspardlezin @agentcardhq @pravapayments @getpayos @evervault @basistheory @crossmint @openfort_hq @turnkeyhq @HallidayHQ @naturalpay @catena_labs
Great research
1Shot API retweeted
I mapped 30 startups building payments for ai agents in 2026
> agent cards & tokens
@agentcardhq @pravapayments @getpayos @evervault @basistheory
> wallets & accounts
@crossmint @openfort_hq @turnkeyhq @1shotapi @HallidayHQ
> banks & networks
@naturalpay @catena_labs @GoKiteAI @PaymanAI + ATXP
> pay-per-call & x402
@daydreamsagents @merit_systems @PayWithLocus + Nevermined, Lava
> trust & identity
@VouchedID @trySkyfire @sapiom @t54ai @Mnemopay
> checkout & merchants
@rye @nekuda_ai @bitrefill @meshpay + Firmly
most are crypto-native and only a handful work on cards, stripe isn't the only one building the agent payment stack!
who's missing? 👇
Why does your AI agent pay the highest card fees in payments?
> your agent can't use your debit card, it gets a virtual card
> that card is issued to a company (the agent startup), not to you
> so visa and mastercard classify it as "commercial"
> commercial cards carry the highest interchange: ~2.5-3%
> and unlike debit, there's no regulatory cap on it
result: a $100 purchase costs the merchant $2.80 instead of $0.27
the issuer and the agent startup split that fee. that's their business model
That's a massive problem for merchants once agents start buying at scale. One fix already exists: wallet + stablecoins + x402.
Our answers for the 1Shot wallet: keys stay on the user's device, raw key material never reaches your app or us, and there are no MAU or signature fees. Try it: wallet.1shotapi.com
If an embedded wallet disappears with its provider, it was never really the user's wallet.
Three questions to ask before you pick one: who holds the key, who else sits in the signing path, and what growth will cost you.
1shotapi.com/blog/who-actual…
1Shot API retweeted
$0 to on-ramp. USDC lands on @arc. Your first BTC buy goes out on schedule. That's the whole setup. 🔁
Replying to @paularambles
so are you supposed to eat the hamster if you get desperate?
1Shot API retweeted
We all gotta self-custody our money now, can't trust anything that you can't audit with your own AI.
Thats why we wrote the signing logic for @1shotapi embedded wallet in pure javascript with no dependencies.
Hopefully the browser vendors are a little safer that PHP
Two critical vulnerabilities have been identified in PHP, a widely used programming language that powers websites and web applications. These vulnerabilities (CVE-2026-109618 and CVE-2026-109619) could allow malicious cyber actors to remotely execute code in PHP core, potentially compromising sensitive data and networks.
The FBI urges organizations to take the following steps now:
➡️ If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated.
➡️ Immediately update affected PHP installations following the guidance on php.net. Inventory where PHP runs in your environment, prioritizing internet-facing systems and vendor products that bundle PHP.
➡️ Monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files. Ensure appropriate process-monitoring capabilities are in place to help identify potential exploitation.
➡️ If you find signs of compromise, isolate affected systems, preserve your web server and PHP logs, and report it to your local FBI field office or ic3.gov. Those reports help us identify the actors involved and warn other organizations before they become victims.
For the latest information, follow PHP’s announcement on php.net, CERT-EU Security Advisory 2026-018, and CISA’s Known Exploited Vulnerabilities catalog.
How session keys and ERC-7710/7715 delegations give an agent bounded, revocable authority instead of the keys: 1shotapi.com/blog/embedded-w…
Replying to @samconnerone
Ready. Clear final rules are what let regular apps offer USDC, not just crypto-native ones. That's the bet behind our free self-custodial passkey wallet, with Circle Onramp built in and gas payable in USDC.
1Shot API retweeted
New: Buy the Dip 📉
Pick a coin, pick the drop, pick the window. Your wallet buys automatically when it happens, and the coins land in your own wallet.
No 3am chart watching. 🔁
1Shot API retweeted
Replying to @CoinOperatedFi
@CoinOperatedFi now has onchain enforced (EIP-7710) "Buy the dip" triggers.
So you can setup a plan that will buy bitcoin:native when prices say 3% in 6 hours. It uses your USDC on @arc network and the BTC gets sent to your personal wallet.
Works for $ETH and $PAXG too.
Replying to @corey__cooper
The escrow one is a great end-to-end test. Pair the Studio-built contract with a passkey wallet on the front end and testers can fund and release escrow in USDC without ever holding a gas token. Fastest way to see the whole Arc flow from a user's seat.
1Shot API retweeted
Thank you @Cloudflare and @eastdakota for the startup credits.
I can't promise i'll make you proud but this will definitely help a lot for @1shotapi and @CoinOperatedFi













