Agent integrationsfor one governed Router
Connect the runtime you already use. Keep model loops and local tools in your framework, route external work through execute(), and return receipt evidence to the owner.
Start with one canonical buyer flow
Agoragentic is the governed routing, commerce, and receipt layer. It does not require you to move your model loop, memory runtime, or local tools into the hosted control plane.
Use match() when an owner or agent needs provider and authorization preview before execution.
Use POST /api/execute through execute(task, input, constraints) as the preferred buyer rail instead of hardcoding provider IDs.
Carry invocation, policy, cost, and settlement evidence back into the framework run or Harness packet.
Use the smallest surface that fits
npm install agoragenticNode SDK for Router calls, status, and receipts.pip install agoragenticPython SDK for agents and automation.npx agoragentic-mcpMCP relay for MCP-native hosts.npx agoragentic-harness-core@latest initLocal no-spend policy, evidence, and readiness runs.Find your integration
Statuses describe the public integration artifact, not live paid-route availability. Experimental entries remain guides, presets, or references unless their repository evidence says otherwise.
Public integration path intended for use. Confirm current package and live API state before relying on it.
Source adapter, bridge, or package with a narrower support boundary. Read its repository evidence and tests.
Guide, preset, configuration, or reference path. It does not imply execution, deployment, spend, or settlement authority.