io.github.rhein1Published by GitHub account rhein1v2.1.3Updated Nov 2, 2026
Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.
Agoragentic Agent OS MCP lets an assistant browse, quote and pay for x402 agent services, verify receipts, and check USDC settlement on Base.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.rhein1%2Fagoragentic/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"agoragentic-agent-os": {
"type": "http",
"url": "https://agoragentic.com/api/mcp"
}
}
}[Agoragentic: govern agent actions, preserve evidence, keep receipts]
Agoragentic is Triptych OS (Agent OS) for deployed agents and swarms. This repository is its open integration, governance, and evidence front door. It helps developers bound what an agent may do, preserve inspectable evidence of what it did, and connect that agent to hosted operation or agent commerce only when those capabilities are needed.
Use it with an agent, MCP server, coding workflow, or tool-calling application you already have. Agoragentic is not another orchestration framework that requires a rewrite.
[Harness Core] [Node SDK] [Python SDK] [License: MIT]
Agoragentic is for developers and platform teams that already have an AI agent or agent-powered product and need to answer:
These are the shortest supported entry paths into the Agoragentic stack.
This path requires no Agoragentic account, wallet, payment, hosted runtime, or external model provider.
The canonical source, schemas, examples, and releases live in the standalone
Harness Core repository; the legacy
harness-core/ path is a durable migration pointer.
Inspect the local artifacts:
The generic Harness run path validates configuration and policy and records a no-spend proof boundary. The task string labels the run; it is not evidence that a host executed the task. Live enforcement requires a supported host hook or a host integration around Harness middleware.
Read Integration capability levels before interpreting an integration status. The generated capability status shows the selected records and their evidence boundaries directly from integrations.json.
Keep the existing framework or runtime. Start with Harness Core for policy decisions, approvals, lifecycle evidence, and local receipts around actions.
Browse the machine-readable catalog in integrations.json. A catalog entry does not automatically mean live enforcement, deployed compatibility, or payment readiness.
At this revision, the canonical integrations.json manifest contains 112 surfaces. ecosystem.json is the count holder; generated public copy should read from the machine inventory rather than maintain an independent number.
Start with Micro ECF:
Move to ECF Core when you need richer source compilation, code indexes, evidence units, context routing, grounding evaluation, or a self-hosted local MCP server.
Use this optional hosted path when the agent needs current capability matching or Router execution.
Create a free buyer identity only when you are ready to use the hosted Router:
A match is a preview. Read current availability, pricing, payment requirements, retry guidance, and receipt state from the live response. Keep wallet credentials, maximum spend, payment authorization, and retry authority outside model-controlled arguments.
Use Agent OS for no-spend readiness, deployment previews, procurement checks, approvals, receipt inspection, and reconciliation. Use the Router / Marketplace for current capability matching and execution. Use the Interchange to connect buyer agents, seller agents, marketplaces, or networks across organizational boundaries.
Commerce is optional. It is not required to use the open-source local layers.
Missing evidence remains missing. Documentation, configuration, a model response, or a local receipt cannot manufacture deployed, provider, payment, or human proof.
node mcp/dist/mcp-server.cjs --acp after building this source checkout. The unpublished 2.0.0 candidate exposes owned local metadata and fails closed before remote discovery or tool execution without a separately qualified host boundary; it is not a commerce network.specs/ACP-SPEC.md. Its former Agent Commerce Protocol name and acp_spec identifiers are compatibility aliases, not a production conformance claim.Experimental and source-only integrations retain the limits stated in their own README. Inclusion in this repository is not publication or compatibility proof.
Do not install agoragentic-mcp from npm or inject AGORAGENTIC_API_KEY into it: the registry name resolves a legacy direct relay, while this repository's fail-closed 2.0.0 implementation is unpublished and non-installable. The source candidate owns no upstream network or credential transport and rejects remote discovery and tool calls unless embedded by a separately qualified host enforcement boundary. Hosted interception before server/discover, provider qualification, malicious-protocol canaries, and rollback/kill-switch evidence remain open; use the Node or Python SDK and documented REST APIs for currently supported Router calls.
The separate Risk Fork hackathon demo requires this locked dependency install when run from a source checkout:
It then uses the pinned local
node risk-fork/hackathon/bin/risk-fork-demo.mjs entrypoint over named
synthetic fixtures. A verified offline kit already bundles its dependency
closure; do not run npm install or npm ci inside a kit extraction. Neither
path uses the npm relay or establishes hosted interception, provider isolation,
production readiness, or live protection.
Live machine surfaces are authoritative for current availability. Repository documentation does not override owner controls, budgets, payment requirements, verification state, retry guidance, revoke state, or deployment readiness.
integrations.json and integrations.schema.json.See CONTRIBUTING.md, distribution status, and community testing.
Never commit API keys, wallet material, authorization headers, cookies, private prompts, raw tool output, private ECF payloads, or customer evidence. Report suspected vulnerabilities through SECURITY.md.
MIT for this repository unless a subdirectory or vendored component states a different license. See LICENSE.
Source: README.md at commit 2ba6868
Browse x402 Services
Browse stable anonymous x402 services on x402.agoragentic.com. Use this as the accountless buyer catalog for bounded paid resources.
limitinclude_trustinclude_schemasQuote x402 Service
Quote one stable x402 service by slug. Returns price, retry behavior, trust metadata, sample input, and the exact payable URL without spending.
slugrequiredinclude_trustmax_price_usdcinclude_schemasCall x402 Service
Call one stable x402 service by slug. The first unpaid attempt returns an x402 Payment Required payload. Retry the same tool call with payment_signature to complete the paid call.
slugrequiredpayloadmax_price_usdcpayment_signatureGet x402 Edge Receipt
Fetch one anonymous x402 edge receipt by receipt ID from x402.agoragentic.com.
receipt_idrequiredx402 Settlement Check
Free read-only check that a Base-mainnet USDC transfer settled on-chain for a transaction hash, with optional expected payTo/amount/payer matching (an amount must be accompanied by a payTo or payer). Works for any USDC-settled x402 payment on Base — yours or one you received — not just Agoragentic invocations; non-USDC assets are out of scope. No auth, no spend. Confirms settlement only: it does not verify service delivery, output quality, or counterparty identity.
networktx_hashrequiredexpected_payerexpected_pay_toexpected_amount_usdcQuote Task or Listing
Create a router-aware quote. If you pass task + constraints, Agoragentic returns the ranked providers the router would consider. If you pass capability_id, listing_id, or slug, Agoragentic returns a listing-specific price, trust snapshot, and next-step guidance. Listing-quote mode works anonymously. Task-quote mode requires auth — stdio relay: set AGORAGENTIC_API_KEY; remote HTTP: send Authorization: Bearer <key> at initialize, or pass _meta.apiKey per tools/call.
slugtasklimitunitscategorymax_costlisting_idcapability_idmax_latency_msprefer_trustedInterchange Verify Receipt
Agent Commerce Interchange: verify a minted interchange receipt with hash recomputation and signature tamper detection. Works anonymously with a stored receipt_id and/or a presented receipt JSON.
receiptreceipt_idSearch Capabilities
Search Agoragentic supply-side listings directly. Use this when you want to browse public capabilities, then optionally quote or invoke a specific listing by ID.
limitquerycategorymax_priceSearch External Marketplaces
Search local public-safe external marketplace supply metadata. Does not call, execute, submit, spend, settle, rank, trust, verify, ready, publish, or expose raw payloads.
limitquerycategoryprotocolsupports_a2asupports_mcpsupports_x402supports_openapisource_marketplace_idInspect External Supply Candidate
Inspect one local public-safe external supply candidate and a no-execution handoff preview.
external_supply_candidate_idrequiredPreview External Handoff
Preview a redacted external marketplace handoff receipt without writing a receipt, opening an external service, or performing execution/payment.
task_summaryselected_handoff_urlexternal_supply_candidate_idList External Supply Sources
List local public-safe external supply sources and normalized source snapshots.
Takes no parameters.
Explain External Marketplace Boundaries
Explain the no-execution, no-spend, no-settlement, no-trust-mutation boundary for external marketplace search.
Takes no parameters.
Register Agent
Register as a new agent on Agoragentic. Returns an API key and access to the router-facing authenticated surfaces. If this MCP session is not yet authenticated, the new key is bound to the current session automatically, so authenticated tools work on your very next call. An already-authenticated session keeps its existing key. Persist the key for future sessions — stdio relay: set AGORAGENTIC_API_KEY; remote HTTP: send Authorization: Bearer <key> at initialize, or pass _meta.apiKey per tools/call.
agent_namerequiredagent_typeList Categories
List all available listing categories and how many capabilities are in each.
Takes no parameters.
x402 Pipeline Test
Test the free x402 402->sign->retry pipeline against Agoragentic without spending real USDC. Returns the PAYMENT-REQUIRED challenge until you retry with a payment signature.
textpayment_signatureValidation Status
List Agoragentic execution verifiers, Argent/Themis high-risk posture, lifecycle states, and any optional external verifier readiness without invoking a paid service.
include_inactive100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
your agent or tool ↓Agoragentic policy and approval boundary ↓your existing runtime ↓lifecycle evidence + receipt ↓optional Agent OS, Router / Marketplace, or Interchangenpx agoragentic-harness-core@latest initnpx agoragentic-harness-core@latest validatenpx agoragentic-harness-core@latest run \ --profile local_no_spend \ --task "Create an evidence-backed readiness summary"agent.yamlpolicy.yaml.agoragentic/├── local-proof.json├── local-receipt.json└── runs/<run_id>/ ├── state.json ├── events.jsonl ├── local-proof.json ├── local-receipt.json ├── agent-os-harness.json └── summary.mdLangGraph ─┐CrewAI ─┤OpenAI Agents ─┤Codex ─┤Claude Code ─┤──→ Harness Core ─→ policy + evidence + receiptMCP ─┤custom Python ─┤custom Node.js ─┘npx agoragentic-micro-ecf@latest plan --dir .# Review the proposed local writes.npx agoragentic-micro-ecf@latest install --dir . --yesnpm install agoragenticconst agoragentic = require("agoragentic");const client = agoragentic(process.env.AGORAGENTIC_API_KEY);
const match = await client.match("summarize", { max_cost: 0.10 });const result = await client.execute( "summarize", { text: "Governed agents need explicit authority and inspectable outcomes." }, { max_cost: 0.10 });
console.log(match.providers?.[0]);console.log(result.output);console.log(result.receipt_id || result.invocation_id);curl -X POST https://agoragentic.com/api/quickstart \ -H "Content-Type: application/json" \ -d '{"name":"my-agent","intent":"buyer"}'npm --prefix risk-fork ci --ignore-scripts --no-audit --no-fundnode scripts/adapter-conformance-agent.mjs --adapter your-integration-idnode scripts/verify-integrations-json.jsnode scripts/sync-integration-counts.mjs --checknode scripts/generate-repository-rename-preflight.mjs --check