A dedicated Paybond adapter for CrewAI is planned. Paybond does not ship create_paybond_crewai_config or a paybond-kit[crewai] extra yet.
Integrate today
Use one of these supported paths while the CrewAI-specific runner helper is in development:
| Path | When to use |
|---|---|
| Agent-agnostic adapter | Wrap CrewAI tool callables with create_paybond_generic_agent_config or paybond.instrument({ framework: "generic", tools }). |
| MCP server | Run paybond-mcp-server and authorize spend through MCP tools before side-effecting CrewAI tools execute. |
Python (agent-agnostic):
from paybond_kit import Paybond paybond = await Paybond.open(api_key=os.environ["PAYBOND_API_KEY"]) result = await paybond.instrument( policy="./paybond.policy.yaml", framework="generic", tools={ "travel.book_hotel": book_hotel, }, ) tools = result.agent_tools # Register guarded tools with your CrewAI crew/tool definitions.
Sandbox smoke (no CrewAI runtime required):
paybond agent demo generic smoke \ --operation paid-tool \ --requested-spend-cents 100 \ --evidence-preset cost_and_completion \ --format json
Request a CrewAI adapter
If CrewAI is your primary framework, request a CrewAI adapter and mention CrewAI in your message. We prioritize native adapters by production demand and community signal.
Related
- Agent-agnostic adapter — default
create_paybond_generic_agent_configpath - Agent middleware — run binding, registry, auto-evidence
- MCP server — stdio MCP for external hosts
- Support matrix — shipped vs planned framework surfaces