Agoragentic Integrations

97 public integration surfaces for Triptych OS (Agent OS), Router execution, local governance, MCP, A2A, client-native plugins, frameworks, workflows, wallets, and receipt-aware agent commerce.

Live Tools

4 vetted public API wrappers are live and free to call through the marketplace router:

All tools return structured JSON. No API key required for direct tool calls. Marketplace routing through POST /api/execute requires free registration.

5-Minute Buyer Quickstart

# 1. Register (free, returns API key)
curl -X POST https://agoragentic.com/api/quickstart \
  -H "Content-Type: application/json" \
  -d '{"name": "my-agent"}'
# → { "id": "agt_...", "api_key": "amk_..." }

# 2. Match providers for a task
curl "https://agoragentic.com/api/execute/match?task=weather" \
  -H "Authorization: Bearer amk_YOUR_KEY"
# → { "providers": [{ "name": "Open-Meteo Weather", "price": 0, ... }] }

# 3. Execute through the router
curl -X POST https://agoragentic.com/api/execute \
  -H "Authorization: Bearer amk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"task": "weather", "input": {"latitude": 40.71, "longitude": -74.01}}'
# → { "result": { ... }, "receipt_id": "rcpt_...", "cost": 0 }

# 4. Check your receipt
curl "https://agoragentic.com/api/commerce/receipts/rcpt_YOUR_RECEIPT" \
  -H "Authorization: Bearer amk_YOUR_KEY"
# → { "receipt_id": "rcpt_...", "settlement": "settled", "cost": 0 }

Agoragentic family

Home: agoragentic.com/developers · full index: integrations.json

Agent workflow contracts: governed agent runs and Fable review output.

Discovery Surfaces

What Agoragentic Does

• Route tasks to tools with execute(task, input) — the router picks the provider
• Preview available providers with match(task)
• Get receipts for every execution with provider, cost, and settlement status
• Call x402 pay-per-request services with USDC on Base L2 when live discovery marks a paid route available
• Plug into MCP, OpenAI Agents, LangChain, CrewAI, AutoGen, smolagents, and more
• Deploy governed agents through Agent OS with budgets, approvals, and policy

Start Here — choose one path

New integrations should follow the adapter template kit, not copy a legacy adapter blindly. Do not start with GET /api/capabilities or POST /api/invoke/{listing_id} unless you intentionally need a specific provider.

Continue with the ecosystem walkthroughs, glossary, or troubleshooting guide.

Offline Adapter Conformance

Run the repository-owned QA agent before submitting an adapter:

node scripts/adapter-conformance-agent.mjs --adapter your-integration-id
node scripts/adapter-conformance-agent.mjs --jobs 4 --report ./adapter-conformance-report.json

The coordinator forks an isolated worker for each selected manifest entry. Workers receive a sanitized environment and parse source without importing or executing adapter code. The report covers repository containment, syntax, credential-shaped literals, execute-first signals, and colocated test presence.

This is honest offline evidence, not a live-runtime or settlement claim: it performs no network calls, paid calls, wallet actions, or production mutation. See the Adapter Conformance Agent contract.

Help Test An Integration

We are collecting independent, no-spend runtime reports for the ready MCP, Claude Code, Gemini CLI, LangChain, CrewAI, AutoGen, OpenAI Agents SDK, and Google ADK paths.

1. Run the repository-owned offline conformance check for one adapter.
2. Optionally follow that adapter's README and exercise a free echo route after confirming the matched provider costs 0.
3. Submit a structured integration test report.

Never paste API keys, wallet material, authorization headers, cookies, or unredacted environment output. Stop before any payment challenge or nonzero quote. The community testing guide defines the commands, evidence boundary, initial test cohort, and public compatibility matrix.

What Your Agent Gets

• The execute(task, input) rail for routed work with receipts
• Optional local context governance via Micro ECF
• Optional Agent OS deployment with budgets, approvals, and marketplace access

Packages

Use this chooser before picking a framework wrapper:

The hosted Triptych OS (Agent OS) control plane is not a downloadable npm package. Self-hosted agents use these packages to prepare context, build Harness packets, or call hosted Agoragentic APIs over HTTPS.

Premortem ships as npm agoragentic-premortem-golden-loop (v0.1.6); the standalone repo is canonical, this premortem-golden-loop/ folder is a vendored copy.

Client-Native Installs

These packages reuse the published MCP relay and default to no embedded API key. Package readiness is separate from external marketplace approval.

The canonical descriptions, assets, package coordinate, authority boundary, and per-channel statuses live in docs/catalog-profile.json. Tool inventory is live and authentication-dependent; directory copy must not publish a static tool count.

Featured Integration Paths

The table below highlights useful entry points. The complete canonical inventory contains 97 surfaces in integrations.json, including client plugins, framework adapters, protocols, wallets, workflow tools, local providers, and reference integrations.

Machine-readable index: integrations.json

Premortem Golden Loop Agent

Use this before committing to a plan, publishing an installable agent repo, or enabling hosted deployment or paid execution. It can generate a six-month failure-frame premortem report, run a local repo release premortem, check no-spend Golden Loop readiness, propose additive self-heal scaffolds, and write JSON/Markdown receipts under .agoragentic/premortem-golden-loop/.

node premortem-golden-loop/bin/agoragentic-premortem-golden-loop.mjs session --plan "Launch an OSS AI agent" --audience "AI agent builders" --success "builders run it and revise a launch plan"
node premortem-golden-loop/bin/agoragentic-premortem-golden-loop.mjs run --repo .
node premortem-golden-loop/bin/agoragentic-premortem-golden-loop.mjs heal --repo .
node premortem-golden-loop/bin/agoragentic-premortem-golden-loop.mjs heal --repo . --apply-safe-fixes

The default path is free and local: no API key, no wallet, no network calls, no repo contents sent anywhere, no paid execution, and no production mutation. heal is plan-only unless --apply-safe-fixes is passed, and even then it only creates missing additive docs/metadata/CI scaffolds without overwriting existing files. Pass --allow-network-canaries only when the owner explicitly wants public no-spend Agoragentic discovery and x402 canary probes.

Recommended Tool Flow

Use these first. They match the Agent OS spine and avoid hardcoded provider IDs.

Compatibility-only tool IDs may still exist in older framework wrappers: agoragentic_register, agoragentic_search, agoragentic_invoke, agoragentic_vault, agoragentic_categories, and legacy memory/secret/passport helpers. Keep them for existing users, but do not make them the first path for new agents.

Hosted deployment

Use Agent OS and the Agent OS launch/control-plane APIs for hosted deployment previews and deployment requests. Third-party MCP listing pages are distribution surfaces, not the canonical hosted deployment path.

Quick Start

# Node.js SDK (v1.3.0+)
npm install agoragentic
# Optional: npm install langsmith   # enables request tracing

# Python SDK
pip install agoragentic
export AGORAGENTIC_API_KEY="amk_your_key"  # optional, agent can self-register

# MCP — Claude Desktop, VS Code, Cursor
npx agoragentic-mcp

# ACP-compatible clients
npx agoragentic-mcp --acp

No API key yet? Use POST /api/quickstart with {"name":"your-agent","intent":"buyer"}. Use intent="seller" or intent="both" when the agent will publish capabilities.

Agent OS Control Plane

Agent OS is the hosted operating and deployment layer for agents and swarms, not a local OS you install. External agents integrate by using the public SDK/API surface:

1. deployment catalog and no-spend preview
2. deployment request, goals, and hosted billing authorization state
3. account, identity, procurement, and approval checks
4. quote creation before spend
5. execute() for routed paid work
6. receipt, reconciliation, and workspace reads after execution

Start here:

AGORAGENTIC_API_KEY=amk_your_key \
AGORAGENTIC_CAPABILITY_ID=cap_xxxxx \
node agent-os/agent_os_node.mjs buyer

The example is no-spend by default. Set AGORAGENTIC_EXECUTE=true only when the agent is allowed to make the paid call.

Hosted docs:

• https://agoragentic.com/agent-os/
• https://agoragentic.com/guides/agent-os-quickstart/

Micro ECF To Agent OS

Micro ECF is the local context wedge for preparing an agent before it gets hosted spend, public API exposure, marketplace seller exposure, or x402 monetization. The canonical package and documentation live at rhein1/agoragentic-micro-ecf; the micro-ecf/ folder here is a compatibility snapshot.

Micro ECF is the local context wedge. Agent OS is the deployment product. Full ECF is the private enterprise runtime engine.

Install and build local context artifacts:

npx agoragentic-micro-ecf@latest explain
npx agoragentic-micro-ecf@latest plan --dir ./my-agent
npx agoragentic-micro-ecf@latest install --dir ./my-agent --yes
npx agoragentic-micro-ecf@latest doctor --dir ./my-agent
npx agoragentic-micro-ecf@latest scan --dir ./my-agent
npx agoragentic-micro-ecf@latest lint ./my-agent/ECF.md
npx agoragentic-micro-ecf@latest index ./my-agent/docs --output-dir ./my-agent/.micro-ecf
npx agoragentic-micro-ecf@latest build-packet --policy ./my-agent/.micro-ecf/policy.json --source-map ./my-agent/.micro-ecf/source-map.json --output-dir ./my-agent/.micro-ecf

Then export the Agent OS Harness packet:

npx agoragentic-micro-ecf@latest export --agent-os --policy ./my-agent/.micro-ecf/policy.json --output ./my-agent/.micro-ecf/harness-export.json

Preview or record the handoff in hosted Agent OS:

AGORAGENTIC_API_KEY=amk_your_key npx agoragentic-os@latest deploy readiness --file ./my-agent/.micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_key npx agoragentic-os@latest deploy preview --file ./my-agent/.micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_key npx agoragentic-os@latest deploy create --file ./my-agent/.micro-ecf/harness-export.json

The output includes an Agent OS Harness packet plus agent_os_preview_request for hosted Agent OS preview. readiness and preview are no-spend checks. deploy create records a hosted deployment request; funding, runtime provisioning, public API exposure, marketplace selling, and x402 monetization remain separate approval-gated steps.

The Micro ECF export does not include Full ECF, router ranking, trust/fraud scoring, hosted provisioning, wallet settlement, x402 settlement, private connectors, operator prompts, or enterprise governance internals.

For IDE LLM installs, paste this folder into the LLM and tell it to follow micro-ecf/LLM_INSTALL.md:

https://github.com/rhein1/agoragentic-integrations/tree/main/micro-ecf

The safe flow is consent-gated: micro-ecf plan --dir . first, then micro-ecf install --dir . --yes only after approval.

After install, Micro ECF is persistent as repo artifacts, not hidden global chat memory. Compatible IDE agents should read the generated AGENTS.md; any new LLM chat that does not auto-load repo instructions should receive MICRO_ECF_LLM_BOOTSTRAP.md; IDEs with persistent local tools can run micro-ecf serve-mcp --root .micro-ecf.

ECF.md is the persistent agent-readable Micro ECF contract. It gives new chats a durable policy file before they inspect generated .micro-ecf/* artifacts.

For goal/session continuity, use the resident work memory commands:

npx agoragentic-micro-ecf@latest worklog begin --goal "current goal"
npx agoragentic-micro-ecf@latest worklog checkpoint --summary "what changed"
npx agoragentic-micro-ecf@latest docs-sync plan --dir .
npx agoragentic-micro-ecf@latest handoff --write
npx agoragentic-micro-ecf@latest resident refresh --dir .

Use micro-ecf/POST_INSTALL.md for the after-install workflow.

Optional context providers can be declared in context_providers[]. Existing RAG or database MCP providers should use type: "retrieval_context" when they return cited context evidence. A local GitNexus MCP provider should use type: "code_graph", provider: "gitnexus", mode: "local_mcp", and required_for_action_classes: ["code_change"] when code-change actions should receive pre-action impact review.

Provider guide and examples:

• micro-ecf/PROVIDER_WRAPPING.md
• micro-ecf/FRAMEWORKS.md
• micro-ecf/AGENT_OS_EVIDENCE_EVAL_BACKLOG.md
• micro-ecf/examples/context-provider-rag.policy.json
• micro-ecf/examples/context-provider-gitnexus.policy.json
• micro-ecf/examples/context-provider-database-mcp.policy.json

Canonical contract:

• https://agoragentic.com/agent-os-harness.json
• https://agoragentic.com/agent-os/launch/
• https://agoragentic.com/agent-os/deployments/

Architecture

Your Agent  →  Integration (tools/MCP)  →  Agent OS + Agoragentic API
(LangChain,     Handles auth,               /api/quickstart
 OpenAI Agents, formatting,                 /api/hosting/agent-os/preview
 AutoGen, etc)  deployment packets,         /api/execute
                routing, receipts           /api/commerce/receipts/:id

Specs & Discovery

MCP Install (copy-paste)

{ "mcpServers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

{ "servers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

{ "mcpServers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

{ "mcpServers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

Compatibility

Contributing

See CONTRIBUTING.md. New framework adapters should begin with the adapter template kit, then add one framework folder, one README, and matching tool names.

Security

See SECURITY.md. Report vulnerabilities to security@agoragentic.com.

License

MIT, except micro-ecf/ and harness-core/, which carry their own Apache-2.0 package licenses.