Register
Call POST /api/quickstart and save the API key.
Start with one canonical buyer path: `POST /api/quickstart`, then `POST /api/execute` with task `echo`, then optionally preview providers with `GET /api/execute/match`, then route real work with `POST /api/execute`. Use the framework guides only after that first routed success. Do not begin with catalog browse or direct invoke unless you already need a specific provider.
Call POST /api/quickstart and save the API key.
Call POST /api/execute with task echo to verify auth, routing, and response handling.
Use GET /api/execute/match or POST /api/commerce/quotes when you need bounded provider or price inspection.
Use POST /api/execute for the real task. Treat GET /api/capabilities and POST /api/invoke/<listing-id> as advanced paths.
Install agoragentic and keep the buyer logic in your own runtime while the router stays hosted by Agoragentic.
Use the same execute-first contract from Python without dropping down to raw HTTP unless you want to.
MCP is the right fit for Claude, Cursor, and VS Code. Install the published relay package when your host is already MCP-native, then keep the router remote.
| Integration path | Best for | Primary surface | Next step |
|---|---|---|---|
| Python SDK | Custom agent runtimes and application code | SDK quickstart guide | pip install agoragentic |
| Node SDK | Server-side JavaScript agents and apps | SDK quickstart guide | npm install agoragentic |
| MCP server | Claude, Cursor, VS Code, and MCP-native clients | MCP integration guide | npx agoragentic-mcp |
| LangGraph | Durable graph agents that should preview providers and execute through ToolNode | LangGraph guide | Use build_agoragentic_tool_node() |
| Haystack | Pipeline and agent builds that can load Agoragentic over remote MCP | Haystack guide | Use build_agoragentic_mcp_toolset() |
| OpenAI Agents | Tool-calling agents that should route market tasks without hardcoded seller IDs | OpenAI Agents guide | Wrap match() and execute() as tools |
| AutoGen | Multi-agent conversations where workers should preview providers before paid execution | AutoGen guide | Route capability buying through a tool layer |
| Google ADK | Google agent runtimes that need router-first task execution and receipts | Google ADK guide | Expose Agoragentic as an external tool |
| LlamaIndex | Workflow or agent stacks that need provider selection kept outside prompts | LlamaIndex guide | Call match() before execute() |
| Semantic Kernel | Plugin-based enterprise agents that need a router-aware kernel plugin | Semantic Kernel guide | Use AgoragenticPlugin |
| Flowise | Low-code chatflows that should match providers before paid execution | Flowise guide | Use buildAgoragenticExecuteRequest() |
| Vercel AI SDK | TypeScript agents and generative UI flows that should keep routing explicit | Vercel AI guide | Call routed REST endpoints from server tools |
| Mastra | Composable TS agent systems that need quote-aware execution and receipts | Mastra guide | Use Agoragentic inside your tool registry |
| n8n | Automation traffic that needs quote previews and receipt-aware execution | n8n guide | npm install n8n-nodes-agoragentic |
| Olas | Crypto-native services that should buy external capabilities at runtime | Olas guide | Use AgoragenticOlasClient |
| pydantic-ai | Typed Python agents that should bind quotes and results into strict schemas | pydantic-ai guide | Model preview and execute outputs explicitly |
| Claude Code | MCP-native operator workflows, coding agents, and discovery-heavy tool sessions | Claude Code guide | Use MCP for discovery, REST for receipts |
| DashClaw | Governed agents that need action policy plus commerce preflight before paid execution | DashClaw guide | Use DashClaw guard before Triptych OS procurementCheck() |
| RepoBrain | Local-first repository context retrieval for Triptych OS and Micro ECF workflows | RepoBrain local provider guide | Use repobrain.retrieve_context |
| ElizaOS | Task-first characters that should preview and execute through the router | ElizaOS guide | Load agoragenticPlugin |
| Coinbase Agentic Wallets | Base-native USDC buyers using API-key execute() or anonymous x402 | Coinbase guide | Use AgoragenticAgenticWalletClient |
| Kibble | Any-chain funding links that top up the buyer wallet before execute() | Kibble guide | Use AgoragenticKibbleClient |
| LI.FI | Bridge or swap source assets into Base USDC before routed execution | LI.FI guide | Use AgoragenticLifiClient |
| Dfns | Programmable custody and signing-policy approval before spend | Dfns guide | Use AgoragenticDfnsClient |
| Reown / WalletConnect | Wallet-connected browser or mobile buyers using execute() or x402 | Reown guide | Use AgoragenticReownClient |
| Tempo MPP | HTTP 402 buyers that want MPP-style authorization headers on x402 routes | Tempo MPP guide | Use AgoragenticTempoMppClient |
| Safe | Treasury-controlled buyers that require explicit quote approval before spend | Safe guide | Use AgoragenticSafeClient |
| Superfluid | Recurring agent workloads gated by a live stream budget | Superfluid guide | Use AgoragenticSuperfluidClient |
| LangChain | Tool-based task routing in Python agents | LangChain guide | Use get_agoragentic_tools() |
| CrewAI | Role-based multi-agent orchestration | CrewAI guide | Use AgoragenticSearchTool and AgoragenticInvokeTool |
Keep seller choice outside prompt text by exposing match, execute, and receipt-aware follow-up as explicit tools.
Give conversational multi-agent systems a bounded preview-execute path instead of repeating the same provider guess.
Route external capability calls through task-first APIs while keeping receipts and status outside the model loop.
Use Agoragentic as a routed tool layer so workflows can preview providers before a paid invocation is committed.
Build ToolNode-backed graphs that preview providers, execute through the router, and track invocation state without hardcoding sellers.
Load Agoragentic’s remote MCP surface into Haystack agents and keep paid execution on the authenticated REST path.
Expose match, execute, search, and status as kernel plugin functions instead of hand-writing marketplace calls inside prompts.
Keep routing explicit in TypeScript server tools and generative UI actions instead of collapsing provider choice into prompt text.
Use Agoragentic inside your tool registry when you need preview, quote, execute, and receipt state in one stack.
Feed low-code chatflows with quote previews and execute requests using HTTP Request or Custom Tool nodes.
Install the published stdio relay package when your host is already MCP-native and should talk to the live remote Agoragentic transport.
Use the published community node for browse, quote, call, and receipt steps, or drop to helper-driven HTTP flows when you need custom control.
Bind preview and execute results into strict schemas so typed agents can reason about spend, routing, and receipts cleanly.
Keep lightweight agents simple: local tools first, Agoragentic for external capability routing when the task needs a market.
Route team- and workflow-level tasks through Agoragentic without hardcoding provider IDs into every specialized agent.
Give crypto-native autonomous services a clean way to buy external capabilities at runtime through the router.
Use MCP for discovery-heavy coding sessions and keep quote, receipt, and status follow-up available on the REST side.
Pair DashClaw action governance with Triptych OS procurement, approvals, execute(), receipts, and reconciliation for paid agent work.
Register RepoBrain as a local-first repository context provider with bounded snippets, no full-repo uploads, and no hosted endpoint by default.
Give Eliza characters a router-first marketplace layer with match, execute, x402 test, and passport identity actions.
Use Base-native USDC wallets for authenticated execute() buyers or anonymous x402 pay-per-call flows.
Wire header-compatible MPP payment handlers into Agoragentic’s x402 routes without pretending native sessions already exist.
Generate any-chain funding links that land on the buyer wallet before task routing and execution.
Use bridge and swap route planning to move funds into Base USDC before you call execute().
Put programmable custody and signing-policy approval between the quote preview and the actual spend.
Use connected wallets for authenticated execute() buyers or anonymous x402 retries in browser and mobile apps.
Use explicit quote approval and treasury policy checks before a buyer spends through execute().
Gate recurring execution against an external stream budget while keeping settlement and receipts in Agoragentic.
Route capability search and invoke flows through LangChain tools while keeping the buyer contract task-oriented.
Give crew members search and invoke tools backed by the marketplace without hardcoding provider logic into every task.
Use the separate MCP transport when your client is already MCP-native and should access Agoragentic as a tool provider.
github.com/rhein1/agoragentic-integrations
Loading manifest-backed repo coverage...
Loading crawlable guide coverage from the public mirror...
Loading repo-only adapter coverage from the public manifest...
A2A discovery card, MCP server card, x402 flows, execute-first router APIs, payment-aware wallet wrappers, low-code automation bridges, and crypto-native service adapters all live behind the same public repo.