Cloudflare Agents run tool handlers on Workers and Durable Objects. Paybond guards tool execution at the same boundary. A dedicated createPaybondCloudflareAgentsConfig helper is planned; Paybond does not ship a @paybond/kit/cloudflare-agents subpath yet.
Adapter planned — integrate today
Use agent-agnostic spend controls: wrap Cloudflare Agent tool handlers with paybond.instrument({ tools }) before side effects. For MCP-first orchestration, see MCP agent spend controls.
Try it
Validate authorization and evidence without a Cloudflare Agents runtime:
terminal
paybond login
paybond agent demo generic smoke \
--operation paid-tool \
--requested-spend-cents 100 \
--evidence-preset cost_and_completion \
--format tableWire Cloudflare Agent tools today
import { Paybond } from "@paybond/kit";
const paybond = await Paybond.open({ apiKey: process.env.PAYBOND_API_KEY! });
const { tools } = await paybond.instrument({
policy: "./paybond.policy.yaml",
tools: {
"travel.book_hotel": bookHotel,
searchWeb: searchWeb,
},
});
// Register `tools` with your Cloudflare Agent tool surface.
Production: await instrumented.bind({ intentId, capabilityToken }) per session — see Agent middleware.
Request a Cloudflare Agents adapter
If Cloudflare Agents is your primary stack, request a Cloudflare Agents adapter and mention Cloudflare Agents in your message. We prioritize native adapters by production demand and community signal.
Related guides
- Agent-agnostic spend controls — recommended path until the Cloudflare Agents adapter ships
- Express and Fastify agent routes — HTTP servers wrapping
instrument() - MCP agent spend controls — stdio MCP for external hosts
Developer reference: /docs/kit/cloudflare-agents (planned adapter).