A dedicated Paybond adapter for Cloudflare Agents is planned. Paybond does not ship createPaybondCloudflareAgentsConfig or a @paybond/kit/cloudflare-agents subpath yet.
Integrate today
Use one of these supported paths while the Cloudflare Agents-specific runner helper is in development:
| Path | When to use |
|---|---|
| Agent-agnostic adapter | Wrap Cloudflare Agent tool handlers with createPaybondGenericAgentConfig or paybond.instrument({ tools }). |
| MCP server | Pair a stdio MCP Paybond server with your agent host when MCP fits your deployment model. |
TypeScript (agent-agnostic):
import { Paybond } from "@paybond/kit"; const paybond = await Paybond.open({ apiKey: process.env.PAYBOND_API_KEY! }); const { agentTools: tools } = await paybond.instrument({ policy: "./paybond.policy.yaml", tools: { "travel.book_hotel": bookHotel, }, }); // Register `tools` with your Cloudflare Agent tool surface.
Sandbox smoke (no Cloudflare runtime required):
paybond agent demo generic smoke \ --operation paid-tool \ --requested-spend-cents 100 \ --evidence-preset cost_and_completion \ --format json
Request a Cloudflare Agents adapter
If Cloudflare Agents is your primary framework, request a Cloudflare Agents adapter and mention Cloudflare Agents in your message. We prioritize native adapters by production demand and community signal.
Related
- Cloudflare Agents spend controls guide — task-oriented stub with smoke command
- Agent-agnostic adapter — default
createPaybondGenericAgentConfigpath - Agent middleware — run binding, registry, auto-evidence
- MCP server — stdio MCP for external hosts
- Support matrix — shipped vs planned framework surfaces