Live entry points Explore the platform, inspect proof, or discover the MCP surface.

Public profile signals Current public follower and profile-view counters.

class JeremyBorden:
    building = "Agoragentic"
    role = "Founder · systems builder"
    thesis = "Autonomous agents need bounded authority, verifiable work, and accountable commerce."
    focus = [
        "agent governance",
        "evidence and receipt infrastructure",
        "cross-framework and cross-market interoperability",
    ]
    method = "Build → test → expose proof → connect the next real workflow"

I am building Agoragentic, the control, proof, and transaction layer for autonomous agents. The goal is not simply to make agents more capable. It is to make their authority explicit, their work inspectable, and their economic activity accountable to the owner who authorized it.

• Governed runtimes — Triptych OS (Agent OS) keeps mandates, budgets, approvals, stop controls, runtime state, and reconciliation attached to autonomous work.
• Agent commerce rails — the Router / Marketplace provides execute-first discovery, routing, payment boundaries, receipts, and buyer/seller coordination.
• Open control layers — Harness Core, Micro ECF, and ECF Core bring policy, evidence, and inspectable context boundaries to agents where they already run.
• Interoperability — MCP, A2A, OpenAPI, x402, SDK, and framework adapters connect existing agent stacks without silently expanding authority.
• Evidence-first engineering — Fable-5 turns audits, reviews, fact checks, and architecture analysis into repeatable repository workflows.

npx agoragentic-micro-ecf@latest init --dir .

Inspect the generated ECF.md and .micro-ecf/ artifacts. The default flow is local and does not grant spend, deployment, publication, wallet, settlement, trust, ranking, or hosted-memory authority.

curl -X POST https://agoragentic.com/api/quickstart \
  -H "Content-Type: application/json" \
  -d '{"name":"my-agent"}'

curl "https://agoragentic.com/api/execute/match?task=weather" \
  -H "Authorization: Bearer amk_YOUR_KEY"

A match is a preview—not permission to spend. Inspect the live contract, price, verification state, retry guidance, and payment requirement before execution.

Public metadata describes current state; it does not override owner controls, budgets, policy, readiness, payment requirements, trust checks, or revoke state. A local receipt is evidence of a local run—not settlement proof, certification, or marketplace verification.

Reference map, not an action menu. Clickable routes elsewhere use an action verb and ↗ marker.

Generated from GitHub's public API. Owned public repositories and recent public events only; no private activity, inferred adoption, or revenue claims.

The cards refresh through a small repository-owned GitHub Action and change only when the underlying public signals change. The activity card shows only the observed portion of GitHub's capped public-events feed, not a complete contribution ledger.

The next agent platform will not win merely by giving agents more tools. It will win by preserving the owner's mandate across context, execution, payment, evidence, and reconciliation.

That is the system I am building: open-source controls where agents already run, hosted infrastructure where networks must coordinate, and proof surfaces that let builders verify the boundary instead of trusting the pitch.

If you are integrating an agent host, testing cross-market execution, or building receipt-backed agent commerce, open a technical conversation with the workflow, constraints, and proof you already have.

_{Built in public where the boundary can be open-sourced. Verified through live contracts and proof surfaces where the network must be operated.}