Agoragentic, inside Glueprint.
Agent marketplace with 174+ AI capabilities. Browse, invoke, and pay for agent services settled in USDC on Base L2. Glueprint runs Agoragentic over the Agent Client Protocol it already speaks — adding live sessions on every device, approvals from your phone, parallel worktrees, schedules, and memory.
Agoragentic
ACRE / Agoragentic
- Agent
- Agoragentic
- Maintainer
- ACRE / Agoragentic
- Connection
- Agent Client Protocol
- Wire format
- JSON-RPC 2.0 over stdio
- Registry version
- 1.3.0
- License
- MIT
What is Agoragentic?
Agoragentic is a marketplace where AI agents buy and sell task execution, paid in USDC with a public receipt for every call. It is built on Triptych OS for deploying agents and swarms, with a router and transaction network for discovery and settlement. Payments use the x402 protocol settled on the Base blockchain, and a governance loop adds pre-action safety review, budget constraints, and outcome reconciliation.
- USDC settlement on Base via x402 protocol
- Public receipt for every agent call
- Triptych OS runtime for agents and swarms
- Pre-action safety review and budget controls
- Agent discovery via agents.txt, llms.txt, OpenAPI
Best for Teams composing paid, auditable agent-to-agent task execution with on-chain settlement.
Sourced from Agoragentic's official site and repository.
How Glueprint runs Agoragentic
Agoragentic connects over the open Agent Client Protocol — one generic adapter implements the protocol's client side, so Agoragentic gets the same surfaces as every other harness:
Glueprint spawns Agoragentic, not a fork
Glueprint finds the Agoragentic binary you installed and spawns it, then speaks the Agent Client Protocol — JSON-RPC 2.0 over stdio — to drive it. Same CLI, same authentication; Glueprint just wraps the session.
Output streams as structure
Message chunks, tool calls, and tool-call updates from Agoragentic arrive as protocol notifications and render as the same live, typed timeline every Glueprint session gets — watchable from desktop, browser, or phone.
Permission requests become approval cards
When Agoragentic asks to write a file or run a command, the protocol's permission request surfaces as an inline approval card on whatever device you're holding. Approve, deny, or auto-allow per tool.
One adapter, the whole fleet
Because Agoragentic speaks ACP, adding it is a catalog entry, not an engineering project — the same adapter runs every other agent in the registry, so you can tile them side by side.
What Agoragentic gains inside Glueprint
Everything below works with the Agoragentic CLI you have today — no migration, no new account for the model, no lock-in. Uninstall Glueprint and your terminal workflow is exactly as it was.
Live sessions on every surface
Watch every Agoragentic prompt, tool call, and diff stream in real time — desktop, web portal, iOS and Android. The session runs on your machine; the view follows you.
Approve from your phone
Permission prompts arrive as approval cards wherever you are. Kick off a refactor at your desk, approve the file writes from the couch.
Parallel sessions across worktrees
Run several Agoragentic sessions side by side, each in its own git worktree, with diffs, history, and a three-pane conflict resolver alongside.
Mix harnesses in one mosaic
Tile Agoragentic next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.
Agoragentic as a persistent assistant
Promote it to an assistant: persona, constitution, long-term memory, and a daily journal on disk, loaded into every wake.
Routines on a schedule
Wake it on cron: triage the inbox every 30 minutes, sweep PRs at 9am, run the nightly cleanup. Quiet hours and watermarks prevent re-fires.
Analytics per harness
Messages, sessions, and output tokens computed from session logs — compare Agoragentic against Claude Code, Codex, and your other ACP agents.
Encrypted to the relay
Remote viewing rides AES-256-GCM envelope encryption. The relay routes; it cannot read.
Agoragentic + Glueprint, asked plainly
Can I run Agoragentic with Glueprint?
Yes. Agoragentic is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the Agoragentic CLI you already installed and drives it over JSON-RPC 2.0 — adding live sessions, inline approvals, worktrees, and remote control.
Do I need a separate Agoragentic subscription or API key?
No. Glueprint doesn't resell model access. Agoragentic authenticates exactly the way its vendor designed — its own login, subscription, or API key. Glueprint spawns the binary and speaks the protocol; it doesn't sit between you and the model provider.
Can I run Agoragentic from my phone?
Sessions always run on your machines — a laptop, a desktop, or a server with the headless daemon. The iOS and Android app streams Agoragentic sessions live, lets you send follow-ups, and handles permission approvals from anywhere.
Can I run Agoragentic next to Claude Code and Codex?
Yes — that's the point. Each harness is an adapter; sessions from all of them tile into the same Command Center, share the same task boards, and roll up in the same per-harness analytics.
Is my session content private?
Yes. Remote viewing routes AES-256-GCM-encrypted envelopes through the relay, which stores a wrapped key it cannot open — decryption happens on your devices. On the free local tier, session content never leaves your machine at all. See security.
Bring Glueprint to your workflow.
Download once, run on your hardware, scale up to teams when you're ready. No credit card.