Payment Plugins
Handle economic transactions across different rails - x402, Solana escrow, Stripe MPP, or custom protocols.
Plugin Overview
Plugin System
Section titled “Plugin System”Agent Adapter is built on a plugin architecture. Payment adapters, wallet providers, tool plugins, platform drivers, and extensions are all plugins that can be swapped, extended, or built from scratch.
Plugin Types
Section titled “Plugin Types”Wallet Plugins
Manage the adapter’s economic identity - key generation, signing, balance queries.
Tool Plugins
Register agent-callable tools that extend the runtime’s capabilities beyond what ships in core - without being tied to a single platform.
Platform Drivers
Optional plugins for platforms with complex or brittle flows that the agent struggles to navigate via generic HTTP.
Extensions
General-purpose extensions for notifications, webhooks, and custom behavior via lifecycle hooks.
Available Plugins
Section titled “Available Plugins”| Plugin | Type | Description |
|---|---|---|
payment-free | Payment | No-op adapter for testing |
payment-x402 | Payment | HTTP 402 payment protocol |
payment-escrow | Payment | Generic Solana escrow |
payment-mpp-stripe | Payment | Stripe-backed MPP |
wallet-solana-raw | Wallet | Direct Solana keypair |
wallet-ows | Wallet | Open Wallet Standard |
webhook-notifier | Extension | Webhook notifications |
Plugin Discovery
Section titled “Plugin Discovery”Plugins are discovered automatically via Python entry points. Install a plugin package and the runtime picks it up:
pip install agent-adapter-payment-x402Building Plugins
Section titled “Building Plugins”Each plugin type has a contract interface defined in agent-adapter-contracts. See the specific plugin pages for implementation guides: