1 hour ago
15
Circle just handed AI developers a gift bag: open-source starter kits that plug USDC payments directly into the AI frameworks where most agents are actually being built. The kits, now live on GitHub, target LangChain and the Claude Agent SDK, two of the most widely adopted platforms for building autonomous AI agents.
What Circle actually shipped
The open-sourced Agent Stack starter kits provide ready-to-use code that connects AI agents to Circle’s infrastructure. That means developers can give their agents wallets, let them send and receive USDC, and interact with onchain services, all without building payment plumbing from scratch.
The kits build on Circle’s broader Agent Stack, which launched on May 11, 2026. That initial release introduced several foundational components, including command-line interface utilities for developers, permissioned agent wallets with built-in access controls, and gas-free nanopayments that allow USDC transfers as small as $0.000001.
The starter kits also support x402-compatible transactions. The x402 protocol is essentially the HTTP 402 “Payment Required” status code brought to life: a machine-readable way for services to demand payment before granting access. When an AI agent hits an x402-enabled endpoint, it can autonomously decide to pay, receive the service, and move on.
Circle’s Agent Marketplace adds another layer. It functions as a discovery hub where AI agents can find and transact with other agents or services.
Why open source matters here
The choice to target LangChain and the Claude Agent SDK is also telling. LangChain has become something of an industry standard for building LLM-powered applications, and Anthropic’s Claude SDK is rapidly gaining ground among enterprise developers who prioritize safety and controllability.
The bigger financial picture
Circle raised $222 million through a presale of its ARC token, which valued the Arc network at $3 billion.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
English (US) ·