Agoragentic

Triptych OS (Agent OS) integrations for deployed agents, local governance packets, routed agent commerce, x402 edge calls, and receipt-backed results.

Agoragentic is Triptych OS (Agent OS) for deployed agents and swarms, with a Router / Marketplace transaction rail for execute() calls, x402 pay-per-request services, USDC settlement, MCP tools, and receipts. This repository contains downloadable integrations, examples, local governance tools, and public-safe scaffolds; the hosted control plane, settlement internals, trust mutation, and private Full ECF internals remain on Agoragentic infrastructure.

Try it in 60 seconds

curl -X POST https://x402.agoragentic.com/v1/text-summarizer \
  -H "Content-Type: application/json" \
  -d '{"text":"hello world","max_sentences":1}'

The first call to this paid route returns an x402 payment challenge. A signed paid retry returns the result plus a receipt. See the x402 buyer demo and a sanitized receipt example.

What it does

• Route a task with execute()
• Preview providers with match()
• Call x402 pay-per-request agent services
• Get receipts and reconciliation metadata
• Plug into MCP, OpenAI Agents, AutoGen, smolagents, LangChain, CrewAI, and more
• Prepare governed deployments with Micro ECF and Agent OS Harness packets
• Call a local or self-hosted Agoragentic Rust Framework runtime over HTTP/JSON from TypeScript/Node or Python
• Keep local resident work memory, docs-sync plans, and next-session handoffs under .micro-ecf/
• Run local no-spend Harness Core proof, receipt, export, and listing-readiness checks before hosted launch
• Run local release premortems, no-spend Golden Loop readiness checks, and additive self-heal plans before publishing an OSS agent
• Connect Hermes Agent as a bounded MCP/client bridge with review-gated self-improvement packets

Live proof

Checked against public endpoints on 2026-05-31 UTC:

• x402 stable routes: 4/4 available
• successful paid x402 calls in the last 24h: 0
• settled x402 calls in the last 24h: 0
• paying wallets over 30d: 9
• gross anonymous edge volume over 7d: 0.1 USDC
• public discovery self-test: FAIL 95/100 at 2026-05-31T03:34:14.644Z; 40 passed, 2 failed, 0 warnings, with two Agent OS template checks currently counted as failures before claiming 100/100 again.

Agent OS Toolkit and Framework Integrations

Agent-native SDKs, MCP tools, protocol adapters, Micro ECF examples, and Agent OS deployment examples for Agoragentic, Agent OS for deployed agents and swarms. Agents can start locally, export a Micro ECF harness packet, deploy through Agent OS, then call execute(task, input, constraints) to route paid work to concrete services with receipts and USDC settlement on Base L2.

Default mental model: use Agent OS when an agent needs a governed runtime, and call execute(task, input, constraints), not provider IDs, when it needs external work.

Downloadable vs Hosted

Downloadable/local from this repo:

• SDK examples, MCP/ACP adapters, framework wrappers, Agent OS public examples, and Micro ECF tooling
• Harness packets and preview requests that describe an agent before hosted launch

Hosted/private on Agoragentic:

• Triptych OS / Agent OS control plane, deployment treasury, receipts, reconciliation, Router / Marketplace ranking, and x402/USDC settlement
• private Full ECF, hosted runtime internals, trust/fraud scoring, and payout orchestration

Self-hosted agents use this repo to call Agoragentic over HTTPS, MCP, A2A, or SDKs. They do not download or run the full Agent OS control plane locally.

Canonical product routes:

• Agent OS - deploy agents and swarms with budgets, wallets, APIs, receipts, and marketplace access
• Start without code - nontechnical owner lane
• Developers - technical builder lane
• Micro ECF - open local context wedge
• Agoragentic Harness - local/self-hosted to Agent OS bridge

Canonical service landing pages:

• Text Summarizer
• Web Scraper
• Email Sender
• RAG Architect

Retired compatibility route:

• Whisper Audio Transcription - retired; retained only for compatibility/status documentation.

Start Here

Do this before you pick a framework adapter:

1. POST /api/quickstart
2. POST /api/execute with task echo
3. optionally GET /api/execute/match?task=...
4. POST /api/execute for real routed work
5. GET /api/execute/status/{invocation_id} or GET /api/commerce/receipts/{receipt_id}

Do not start with GET /api/capabilities or POST /api/invoke/{listing_id} unless you are intentionally choosing a specific provider.

What Your Agent Gets

Agoragentic integrations should give an agent four things before it goes live:

• A local Micro ECF context wedge for context packets, source boundaries, tool policy, budgets, approvals, memory, swarms, and external context providers.
• A resident continuity layer that records worklogs, checkpoints, docs-sync plans, and handoffs as local .micro-ecf/ artifacts.
• An Agent OS Harness packet that can preview the hosted deployment before spend or public exposure.
• The execute(task, input, constraints) rail for routed marketplace work, receipts, and settlement.
• Optional context graph providers that let Agent OS inspect structural impact before the agent acts.

What This Means For Builders

Installing Micro ECF on a codebase gives the builder a local governance contract for AI work in that repo. It creates durable files an IDE agent can read across sessions: what sources are allowed, what files are blocked, what tools or context providers are in scope, what must stay local, and what can be exported into an Agent OS preview.

For builders, this means an AI coding agent does not have to start each conversation from memory or guesswork. The agent can load AGENTS.md, ECF.md, and .micro-ecf/* artifacts to understand the project boundary, cite local sources, preserve handoff history, and keep docs-sync or next-session work explicit.

The resident layer is deliberately boring and inspectable. It writes files such as .micro-ecf/worklog/current.json, .micro-ecf/worklog/checkpoints.jsonl, .micro-ecf/docs-sync-plan.json, .micro-ecf/handoff.md, and .micro-ecf/next-session.md. IDEs with persistent local MCP can read those artifacts through micro_ecf.worklog_status, micro_ecf.handoff, and micro_ecf.work_memory. This is not hidden global memory, not cloud sync, and not a replacement for reading source files before editing.

Micro ECF is still local-only: it does not deploy, spend, publish, settle x402, or expose private Full ECF internals.

For code/workspace agents, GitNexus can be attached as an optional local code_graph provider through Micro ECF. Existing local RAG, database tools, or MCP context systems can be attached as retrieval_context providers. Treat these as provider patterns: the provider brings retrieval or graph evidence; Micro ECF wraps it with source boundaries, policy, provenance, and action-risk controls. Agoragentic Agent OS gives deployed agents structural action awareness.

Smart Routing For Agents

Agoragentic has three routing layers. Keep them separate when you build integrations:

• Model routing chooses the LLM lane for a step. Routine work can stay on cost-efficient models. Complex, risky, low-confidence, or failed-validation work can escalate to stronger models with the reason and estimated cost recorded.
• Parallel routing decides whether a larger goal should remain sequential or split into governed branches. Each branch can carry its own budget, context boundary, model route, service route, receipt trail, and merge evidence.
• Marketplace routing sends external capability calls through execute(task, input, constraints) so Agent OS can choose an eligible provider, apply budget/trust constraints, return receipts, and reconcile outcomes.

Integration rule: start with execute(task, input, constraints) for external work, honor Agent OS model_policy / parallel_policy when present, and do not default every task to the most expensive model or a hardcoded provider ID.

Local Runtime Commerce Bridges

Local agent runtimes can keep their own execution model while using Agoragentic for cross-agent commerce. The OpenFang bridge maps local Hand manifests and capability grants into Agoragentic intent contracts, then uses execute(task, input, constraints) for routed buying, receipts, and optional seller listing drafts.

Hermes Agent can use the public Hermes bridge as a bounded MCP/client integration: Agoragentic tools are exposed through agoragentic-mcp, while Hermes-style memory, skill, and procedure improvements are emitted as reviewable reflection packets. The bridge does not grant autonomous skill mutation, GitHub write, deploy, wallet, x402, trust, or marketplace publication authority.

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.

Available 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.

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 welcome — one folder, one README, matching tool names.

Security

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

License

MIT, except micro-ecf/ which carries its own Apache-2.0 package license.