ΛΟΓΙΟΝ // MARKETPLACE LOOP ONLINE

ΛΟΓΙΟΝ
Logion

Teach the agents what you know. Keep it owned, credited, and compounding.

Smarter, together.

An agent-native marketplace for operational knowledge, packaged as reviewed course bundles that agents can acquire, install, and improve.

  • Open-source, auditable client
  • Scanners + human review on every version
  • Immutable, versioned bundles
  • Creators keep 85%

linking your GitHub account…

View GitHub Read terms

Logion is not a video course marketplace or a generic skill directory. It packages reusable operating knowledge for agents as bundles with manifests, examples, tests, evals, docs, and explicit capability declarations.

bundle
course/capabilities.yaml
trust
scanners + review
access
entitlement
improve
bounties
v0.1.13 · stable
§ ethos

We built the library

For two decades people wrote the tutorials, the answers, and the open source — for free. It was compiled into products worth billions, and the people who wrote it were told they were replaceable. Logion is the correction: you keep your knowledge, publish it as a reviewed capability, and agents acquire it to do real work. When it can be better, a creator-funded bounty pays someone to improve it, and the next version lifts everyone. The people who built the library set the terms.

  • You keep your knowledge Publish what you know as a reviewed, versioned capability that agents pay to use and that others are funded to improve. Contribution stays owned and credited, not quietly absorbed.
  • Human expertise is the scarce input Models compress what already exists; they do not invent what was never written down. Frontier capability is bottlenecked by data, and that expertise erodes as fewer people learn the craft and more just ask a model. Logion is the person teaching the agent — keeping knowledge alive, owned, and compounding.
  • A network out-learns a lone model The edge is shifting from raw model scale to how well a system integrates real human expertise through continual learning loops. A network of people teaching agents beats any single model working alone — distributed and defensible, not winner-take-all.
§ what

What Logion is

Logion packages operational knowledge for agents as course bundles. A bundle can include skills, manifests, examples, tests, evals, and docs, plus a machine-readable course/capabilities.yaml declaration that explains what the bundle needs and does.

  • Not video courses The product is for agent execution, not passive human learning.
  • Not a generic skill directory Listings are reviewed, versioned marketplace artifacts with explicit acquisition and entitlement state.
§ agent-flow

Agent acquisition flow

A buyer agent searches the marketplace, gets details on a reviewed course, spends credits to purchase the entitlement, and installs the bundle into LOGION_HOME. The same CLI verbs power vendor integrations.

$ logion listings search --query "database migrations" --category data
  migration-safety-review     900 credits   v1.0.2
    capabilities: file, terminal
    review:       scanners + human publication review

$ logion courses get 7a2f...e0d4
  price:     900 credits
  publisher: opentide
  reviewed:  2026-04-12

$ logion credits balance
  1,200 credits

$ logion courses purchase 7a2f...e0d4 --yes
  spent:        900 credits
  remaining:    300 credits
  entitlement:  granted

$ logion skills install \
    --course-id 7a2f...e0d4 \
    --version-id 3f9b...c1a8 \
    --source ./migration-safety-review \
    --install-source logion-marketplace
  installed: [email protected]
§ security-authority

Security is the authority

Security and review are the central authority surfaces of the marketplace, not decorative claims. Listings are reviewable before acquisition and accountable after publication.

Runtime sandbox enforcement remains future runtime work; the landing must not claim it is already solved.

  • course/capabilities.yaml declarations
  • automated scanners
  • human publication review
  • immutable published versions
  • buyer-safe capability summaries
  • reports, takedowns, access revocation
  • execution policy export path
§ open-source-trust

Open-source trust layer

The API implementation is private; the client and integration surface are public for inspection. Audit what an agent runs locally and what it sends to the marketplace. No MCP setup is required for the first workflow.

§ loop

How the marketplace loop works

The heart of the product is a loop, not a transaction. An agent hits a wall, acquires a reviewed capability on trust, uses it on the task, and a creator-funded bounty improves it — and every turn leaves the marketplace stronger than the last. creator publishes -> Logion reviews -> buyer agent acquires entitlement -> agent installs/uses -> contributors improve through bounties

  • Creator publishes A creator packages a course bundle and submits it for publication review.
  • Buyer agent acquires The buyer agent receives an entitlement before installing or using the protected bundle.
  • Contributors improve Creator-funded bounties let contributors harden, extend, or repair useful bundles.
§ trust

Trust and safety model

Logion makes bundle behavior reviewable before acquisition and accountable after publication. Runtime sandbox enforcement is future runtime work, not a current landing claim.

  • Immutable versions Published versions are immutable so buyers can reason about exactly what their agent installed.
  • course/capabilities.yaml Capability declarations make permissions, tools, and expected behavior visible to reviewers and buyer agents.
  • Automated scanners Scanner results inform publication review and update history.
  • Human publication review New and updated bundles pass through human review before marketplace availability.
  • Buyer-safe summaries Listings summarize capabilities in language buyers can evaluate before granting access.
  • Reports and moderation Abuse reports, takedown paths, listing removal, access revocation, and account suspension protect the marketplace.
  • Execution policy path Execution policy is documented as the path toward runtime enforcement without claiming that sandboxing is already solved.
§ economy

Credits, referrals, and bounties

No platform subscription gate. Buyers top up credits and pay for courses in credits with no Stripe redirect per purchase. Free courses cost zero credits. Creators keep 85% and the platform fee is 15%. Referrers can earn credits through the referral program. Bounty funders fund with credits; bounty contributors cash out through Stripe Connect after acceptance.

  • 100 credits = $1 Credits are denominated at 100 credits per US dollar at top-up. All marketplace pricing is shown in credits.
  • Free and paid acquisition Free courses cost zero credits. Paid course purchases spend credits without a Stripe redirect.
  • Creators keep 85% Creators keep 85% of paid course revenue. The platform fee is 15%.
  • Referral rewards Referrers can earn credits through the referral program subject to attribution, qualifying purchase, and anti-abuse rules.
  • Bounties Bounty funders fund bounties with credits. Contributors cash out through Stripe Connect after acceptance.
§ install

Install

One line installs the Logion CLI and the agent companion, then runs onboarding. Point your agent — Claude, Codex, OpenCode, or Hermes — at Logion and it drives the marketplace for you. pipx and npx are alternate package-manager entrypoints that run the same onboarding.

curl primary (CLI + companion + onboarding)
curl -fsSL https://logion.sh/install.sh | sh
pipx alternate
pipx install logion-cli && logion onboarding
npx alternate
npx @logionsh/cli onboarding

The curl installer adds the CLI and the companion, then runs `logion onboarding` to wire up your agent. pipx and npx are alternate package-manager entrypoints that run the same onboarding. Use --cli-only or --no-onboarding to opt out.

§ harness

Harness-native workflow

The CLI is the execution layer. Vendor integrations should be thin wrappers over the CLI, and Logion is designed for harnesses such as Hermes Agent, Claude Code, Codex, and OpenCode where the integration is not already present.

§ faq

Frequently asked questions

Short, quotable answers to the questions buyers, creators, and agents ask most.

What is Logion?

Logion is an agent-native marketplace for operational knowledge, packaged as reviewed, versioned course bundles that buyer agents can acquire, install, and improve. It is not a video course marketplace or a generic skill directory.

How are courses priced?

Courses are priced in credits. Credits top up at 100 credits per US dollar. There is no platform subscription gate. Free courses cost zero credits. Paid course purchases spend credits without a Stripe redirect.

How much do creators keep?

Creators keep 85% of paid course revenue. The platform fee is 15%. Creator payouts are made through Stripe Connect, not by redeeming buyer credits.

How are course bundles trusted?

Every published bundle is reviewable before acquisition and accountable after publication. Trust comes from capability declarations (course/capabilities.yaml), automated scanners, human publication review, immutable versions, and reports/takedown paths. Runtime sandbox enforcement is future runtime work and is not claimed as solved.

How does a buyer agent acquire a course?

Real CLI flow - logion listings search to find a reviewed course, logion courses get for details, logion credits balance to confirm funds, logion courses purchase to spend credits and receive an entitlement, and logion skills install to install the bundle into LOGION_HOME.

Is MCP required to use Logion?

No. The first workflow uses the public CLI and SDK directly. MCP can remain a future thin adapter over the same public CLI and API contract; no MCP setup is required to get started.

What are bounties?

Bounties are creator-funded improvements to course bundles. Contributors submit improvements and, on acceptance, cash out through Stripe Connect. Bounties are funded in credits.

Are credits refundable or transferable?

No. Credits are non-cash, non-transferable, non-redeemable usage rights inside the marketplace. Credits may be reversed for chargebacks, fraud, abuse, or administrative correction. See /credits-terms for the full rules.