Gabriel Lopes

Ax402 is now Launa! We started with x402 micropayments. But agents need MORE than a way to pay. They need to find a business, understand its offer/catalog, transact, and settle. Launa makes businesses ready for the agentic internet. 👉 launa.io

Agents shouldn't have to wait for a human to click "confirm" to get work done. Introducing SAW (Simple Agent Wallet): the first wallet purpose-built for agentic commerce and x402 payments. 🛠️ The Agent-Native Flow: saw inspect → saw pay --confirm 🛡️ Hardened Security: - Keys stay local in wallet.json. - Secrets via stdin/prompts/env ONLY: never CLI flags. - Native approve-permit2 for EVM token flows. 🌐 Multi-Family: Neo X, Solana, Hedera, and all EVM chains in one wallet file. Stop adapting generic human-based wallets to agents... give your agents a tool that actually ships payments. Make the cut -> saw.axlabs.com/

Announcing: GitMyABI x Etherscan GitMyABI is partnering with @etherscan to bring `npm install` to every verified smart contract. AI agents shouldn't burn tokens parsing raw ABIs and building from scratch. They install a typed, safe npm package from GitMyABI and that's it! 👇

Introducing... Ax402 🚀 A payment layer for monetizing APIs, data feeds, content, and protected resources. Add pay-as-you-go access powered by the x402 standard. Simple for builders. Ready for humans and AI agents. First 1,000 settlements are free. ax402.io

Venice E2EE Proxy is now featured on Built in Venice 🎉 A local OpenAI-compatible proxy that encrypts requests and verifies responses when using @AskVenice E2EE models. Built for agents. No client changes. Repo 👇 github.com/AxLabs/venice-e2e… builtinvenice.ai

Today, online payments are built for people clicking buttons... and that's exactly why we're getting close to releasing Ax402. 🎉 A payment layer for APIs, content, and protected resources in the agentic economy. [1/5]

HTTP 402 was supposed to mean "Payment Required". But, for decades, it mostly meant "reserved for future use". Now the x402 standard is bringing it back… not for checkout pages, but for machines. AI agents need to request resources, pay, and access services without accounts, API keys, or manual setup. That's why x402 matters. 👉 Read our latest editorial: axlabs.com/editorial/x402-ex…

Plaintext prompts to AI providers should NOT be the default anymore. Privacy matters more than ever in the AI world. 👉 We built Venice E2EE Proxy: a local OpenAI-compatible proxy that encrypts requests and verifies responses when using `e2ee-` @AskVenice models. That's the power of end-to-end encryption. Run it: `npx @axlabs/venice-e2ee-proxy --venice-api-key <your-venice-key>` Then point your agent to: http://localhost:3000/v1 Encrypted inference. No client changes. 👉 github.com/AxLabs/venice-e2e… @ErikVoorhees @jordanurbs @jesseproudman @willyogo @dylangrabowski

🚨 Announcing xGAS and xGAS Station 🚨 xGAS stands for Extended GAS. It is a wrapped version of native GAS on Neo X, backed 1:1, but with additional authorization features designed for modern wallets, applications, relayers, and agent-based flows. At its core, xGAS keeps standard ERC-20 behavior intact. But it also adds: - EIP-2612 / ERC-20 Permit support - EIP-3009-style transfer authorization - ERC-1271-compatible signature paths for smart wallets Why does this matter? 🤔 Because not every application, relayer, or AI agent should need to hold native GAS and submit transactions directly. With xGAS, a user or agent can sign an authorization off-chain, and another party can submit the transaction on-chain. That enables delegated execution, smoother UX, and more flexible machine-to-machine payment flows. To make wrapping and unwrapping simple, we also created xGAS Station: 👉 xgas.axlabs.net xGAS Station lets users wrap and unwrap GAS <> xGAS on Neo X at a 1:1 rate, always. The xGAS smart contract has been audited and was designed as a minimal, immutable, integration-friendly base asset for the @Neo_Blockchain ecosystem. This is one more step toward making GAS programmable, easier to integrate, and ready for the AI agent economy. More to come! Stay tuned.

Day 3: AxLabs Retreat Real talk: today the AxLabs team put the laptops down and touched actual grass 🌿 Monastery visit ✅ Beer brewed by monks since the 1400s ✅ Hiking trails ✅ Debating Bitcoin forks mid-walk ✅ Turns out we can't fully escape the builder brain. But at least we did it surrounded by nature.

🚀 Day 1: AxLabs 2026 Retreat What a first day. We kicked things off by diving deep into some of the most relevant problems in tech right now: from supply chain attacks and developer trust, to AI consistency in production workflows and how to actually build products people will pay for. We debated what makes a builder credible, had honest conversations about MVPs vs. just "announcing things", and explored how crypto payments and ticketing systems could be reimagined with identity-linked ownership. Also tackled some big questions: how do you reach your first users? How do you price something? What does real traction look like vs. the illusion of it? Day 1 is done... but things are just getting started over here. 🔥

Backends have CI/CD. Frontends have CI/CD. Smart contract interfaces (ABIs) still live in Slack or Discord threads, docs, and Git repos. This is still far too manual. Too fragmented. There has to be a better way. So we built GitMyABI. Announcing 🥁🥁🥁 gitmyabi.com GitMyABI turns smart contract interfaces (ABIs) into proper build artifacts: - deterministic ABI outputs - stable URLs - versioned npm packages with bindings - reproducible builds for every commit Instead of: "Hey, do you have the latest ABI?" You get a URL. You get an npm package. You get a specific version. This becomes even more important in a world of AI agents, where smart contract integrations need reliable, ready-to-consume interfaces they can plug directly into dApps. We also use decentralized storage (NeoFS) to store smart contract npm packages, enabling: - immutable packages - decentralized hosting - verifiable artifact distribution And we’re not stopping there. We’re building an MCP interface so LLMs and agents can connect directly to GitMyABI and fetch contract artifacts more easily. This is just the beginning. Try it out and tell us what you think: 👉 gitmyabi.com