x402 Protocol Lets AI Agents Pay Per API Call Using HTTP and Blockchain

·2 views

The x402 specification repurposes the long-dormant HTTP 402 Payment Required status code to enable per-call micropayments between autonomous AI agents and API servers. When a client makes a request without payment, the server responds with a 402 status and embeds payment details in a standard HTTP header, which the client's wallet then fulfills on-chain. Once the transaction is verified, the server processes the request and returns a normal 200 response — all without a separate billing system or custodial intermediary. The reference implementation uses USDC on Base, an Ethereum Layer-2 network, offering transaction fees as low as $0.0001 and roughly two-second confirmation times. The approach is designed for developers building AI agents that make thousands of fine-grained service calls daily, where traditional subscription or invoice-based billing models become impractical.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Key Architectural Patterns That Keep Full-Stack Apps Maintainable Long-Term

A technical guide published on DEV Community outlines architectural decisions that determine whether full-stack applications remain workable years after launch. The article emphasizes establishing a single source of truth for API contracts — using tools like OpenAPI or tRPC — to prevent inconsistencies as codebases grow beyond a handful of endpoints. It recommends separating business logic into a dedicated service layer, keeping route handlers and data persistence layers focused on narrow responsibilities. The guide also warns against reactive caching strategies, urging developers to define staleness tolerance and invalidation rules before adding any cache layer. Additionally, it highlights that database schema decisions carry far greater long-term cost than frontend choices, making careful migration practices and explicit relationship modeling essential from the start.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

VeraCrypt 1.26.29 Guide: How to Avoid Lockouts, Data Loss, and Misuse

VeraCrypt 1.26.29, released on June 9, 2026, is the latest version of the open-source disk-encryption tool, introducing Argon2id key derivation for non-system volumes and fixing a plausible-deniability flaw present in versions 1.26.6 through 1.26.28. The software encrypts and decrypts data on the fly, allowing applications to interact with files normally without awareness of the underlying encryption. A practical guide accompanying the release highlights that most VeraCrypt failures stem from poor system design rather than broken cryptography, citing risks such as forgotten PIM settings, untested recovery media, and improper volume unmounting. The guide recommends using default AES encryption with Argon2id, maintaining backed-up keyfiles, and avoiding system encryption on unsupported platforms like macOS and Linux. It also cautions that VeraCrypt protects data only at rest and cannot defend an unlocked volume against malware, ransomware, or keyloggers.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Reviews Tencent EdgeOne Makers, Shares Web Deployment Best Practices

A developer has shared a hands-on review of Tencent EdgeOne Makers, a platform that allows developers to build, test, and deploy web projects in a real environment. The review highlights key considerations including performance optimization, such as compressing images and removing unused files, to ensure consistent load times across devices and networks. The author also stresses that security practices — like keeping API keys and passwords out of public source code — should be adopted early, especially by beginners. Testing beyond the local environment is recommended, with the developer suggesting a continuous cycle of building, publishing, checking, and improving. The piece concludes with practical advice for young developers, emphasizing clean project structure and thorough testing at every stage.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build a Reliable Small-Scale Test for AI Memory Systems

AI memory systems often appear impressive in demos, but a convincing output is not proof they will perform reliably in real-world use. A practical evaluation method involves creating a minimal note with a known date, owner, decision, and explicit limitation, then testing retrieval, interpretation, missing information, updates, and historical recall separately. Testers should verify not just the answer but the source evidence behind it, checking whether names, dates, and negations such as 'not approved yet' are preserved accurately. Updating a fact and re-querying helps distinguish whether the system correctly identifies the most current value versus an outdated one. Repeating the test across sessions with source inspection at every step provides a reproducible way to pinpoint whether failures stem from retrieval, interpretation, data freshness, or unsupported generation.

0 comments Read more at DEV Community