---
title: "co/core — an AI cooperative"
url: https://stacklist.com/card/9b69aba1-955f-4e8f-9683-38ef101ce932
source_url: "https://cocore.dev/"
stack: https://stacklist.com/stack/7138e2e5-fecf-4688-a91c-03f8c02ac1aa
summary: "co/core is a member-owned AI cooperative that enables people to share their existing compute to run AI inference for each other instead of relying on centralized providers. It uses open models, maintains API compatibility with standard providers, and creates transparent, verifiable job records through cryptographic signing."
tags: "ai-cooperative, decentralized-inference, member-owned, open-models, compute-sharing, distributed-computing"
key_entities: "co/core (organization), AI cooperative (concept), MLX (technology), OpenAI API (technology), Devin Gaffney (person), Joe Cotellese (person), Corey Farwell (person), Secure Enclave (concept), Gemma-4-12B (technology), decentralized-inference (concept)"
classification: "reference"
content_hash: "sha256:1c5a166d9d95e9e504b978fa82990d29802d02fae0d5404e45c092b1e1e83875"
acp_version: "0.2"
token_counts_approximate: 2030
visibility: public
agent_accessible: true
status: "final"
---

# co/core — an AI cooperative

an experiment in member-owned AI An AI cooperative. co/core is a place where people share the compute they already own to run AI for each other, instead of renting from a handful of giant providers. It's an experiment in inference we build, share, and own together — and your existing code works as-is, because we speak the same standard API everything else does. The models are open ones that run on the hardware people already have. Get started — it's free → See how it works ↓ Have compute to share? Get the co/core app — macOS, Apple Silicon machines online 49 models available 16 / 23 active (7d) time to first token 17.8s p50 combined memory 1.8 TB RAM combined cores 556 cpu cores free to start 1M tokens live on the network Real members. Real machines. Real receipts. A glimpse of the co-op right now — some of the people who've signed up, some of the machines sharing compute, and the latest jobs they've signed off on. Every one of these is a real, public record. some co/core members Devin Gaffney @ devingaffney.com provider Joe Cotellese @ cotellese.net provider xan.lol Boyd @ bbkt.bsky.social Bailey Townsend 🦀 @ pds.dad provider Luke Bennett @ lukebennett.dev machines sharing compute ▢ Alex's MacBook Pro Apple M2 Pro · Alex Sweeney ▢ Noahs-Virtual-Machine.local Apple M4 Pro (Virtual) ▢ m4-mac-mini Apple M4 ▢ Corey’s Mac mini Apple M4 Pro · Corey Farwell ▢ Mini Apple M4 · JP ▢ morningstar Apple M1 Pro · Michael recent job receipts lmstudio-community/gemma-4-12B-it-MLX-8bit in 3,391 · out 1,026 · did:plc:deib…o2wbv3 · 121.0s lmstudio-community/gemma-4-12B-it-MLX-8bit in 3,391 · out 1,026 · did:plc:deib…o2wbv3 · 122.0s lmstudio-community/gemma-4-12B-it-MLX-8bit in 3,391 · out 1,026 · did:plc:deib…o2wbv3 · 121.0s lmstudio-community/gemma-4-12B-it-MLX-8bit in 3,295 · out 110 · did:plc:deib…o2wbv3 · 28.0s lmstudio-community/gemma-4-12B-it-MLX-8bit in 35 · out 744 · did:plc:deib…o2wbv3 · 91.0s 01 drop-in Just change three lines. co/core speaks the same API language as everybody else. Point your existing SDK at cocore.dev/v1 , drop in a cocore-… key, and keep going — streaming, tool calls, and the usual chat/completions shape all work, no code changes. Host from our presets or any MLX model . OpenAI Anthropic Together Groq Ollama co/core client.py before from openai import OpenAI client = OpenAI( base_url= "https://api.openai.com/v1" , api_key= "sk-proj-…" , ) resp = client.chat.completions. create ( model= "gpt-4o-mini" , messages=[ { "role" : "user" , "content" : "hello" } ], stream= True , ) client.py after from openai import OpenAI client = OpenAI( base_url= "https://cocore.dev/v1" , api_key= "cocore-7f3a2c…" , ) resp = client.chat.completions. create ( model= "mlx-community/Qwen2.5-0.5B" , messages=[ { "role" : "user" , "content" : "hello" } ], stream= True , ) 02 how it works You send a request. The co-op runs it. Your request finds a member's available compute, runs the job, and comes back to you. The whole thing is an open spec — every job leaves a signed, public record anyone can verify for themselves, ours included. 1 job You send a job Your encrypted prompt heads out into the co-op. Run your prompt for a given model anywhere in the open network, or choose to keep your jobs private to only a trusted circle of co-op friends and their machines. → dev.cocore.compute.job inputCommitment: sha256 priceCeiling: 2,500 tokens acceptedTrustLevel: hw 2 attest + run A member runs it Someone picks up your job, runs it, then returns the result after signing with a key locked in the Secure Enclave that never leaves their hardware — proof of exactly who did the work, and that nobody touched it after. → dev.cocore.compute.receipt tokens: 3,391 in · 1,026 out price: 4,417 tokens enclaveSig: ✓ SE-bound 3 settle Receipts, in the open A receipt closes out the job — credits go to whomever who ran it, minus a small cut to a shared pot. Each month that pot splits back to members by how much they pitched in, so the cut cycles right back to the people running the network. → dev.cocore.compute.settlement debit: 4,417 tokens credit: 4,196 tokens fee: 221 tokens → treasury 03 open by default You don't have to take our word for it. Every job writes a receipt anyone can verify on their own, without ever calling us. We can't inflate a balance, fake a payout, or quietly change the rules. And if you don't like how we run things, you can run the whole thing yourself — point your own copy at the same data and it lands on exactly the same numbers. ◆ The record lives with the person who made it We keep a fast index, but the real, signed record of every job lives on the provider's own account — not locked inside our database. ◆ Receipts check out on their own A receipt plus our public spec plus the signer's identity is all you need to confirm a job happened — offline, with no co/core API in the loop. dev.cocore.compute. provider provider dev.cocore.compute. attestation provider · SE-signed dev.cocore.compute. job requester dev.cocore.compute. paymentAuthorization requester dev.cocore.compute. receipt provider · SE-signed dev.cocore.compute. settlement exchange dev.cocore.compute. exchangePolicy exchange dev.cocore.compute. dispute exchange Here's a real receipt and the records it points back to — the job you sent, the machine's attestation, and the public settlement. Follow the chain and check it yourself. at://did:plc:deib…o2wbv3/dev.cocore.compute.receipt/3mozl7omp6j24 dev.cocore.compute.receipt signed · did:plc:deib…o2wbv3 model lmstudio-community/gemma-4-12B-it-MLX-8bit tokens in 3,391 · out 1,026 price 4,417 tokens enclaveSig ✓ P-256 / SE-bound └─ strongRef → job dev.cocore.compute.job @you.bsky.social inputHash sha256 7a3f…b9c1 ✓ priceCeiling 2,500 tokens ✓ within └─ strongRef → attestation dev.cocore.compute.attestation @kira.bsky chip Apple M3 Max · SIP on MDA chain ✓ → Apple Root └─ settled by → exchange dev.cocore.compute.settlement @cocore.dev charged 4,417 tokens payout did:plc:deib…o2wbv3 · 4,196 tokens verifier · plain HTTPS to 3 PDSes verifyReceipt → ok 04 an open standard An open standard. Run your own exchange. Underneath the co-op is an open standard for two plain things: making an inference request, and recording what happened afterward — a signed, public account of every job. We run one exchange on top of it, with our rules: one unit in, one unit out, a shared pot that goes back to members. But the standard is the real work here. Anyone can stand up a different exchange — their own pricing, their own membership, their own idea of what's fair — reading and writing the very same records. Ours is just the first one. If co/core ever stops being the version you want, you don't have to ask us to change it; you can go build yours. the records · signed + public job from requester ↓ receipt signed by who ran it ↓ settlement from an exchange any exchange reads + writes them ◆ co/core your exchange another share your compute Share your compute. Help run the co-op. Download the co/core app, sign in, pick a model or two, and your computer joins the network — running jobs for other members while you're not using it. No Terminal, nothing to babysit; it updates itself. Every job it runs adds to your balance, and a share of everything the co-op does comes back to members each month. ↓ download the co/core app → open · sign in · serve Pair a machine → Read the docs ✓ Your machine, your key A key born inside the Secure Enclave is your machine's identity — it can't be copied off the machine, and it signs everything your machine does. ✓ One token in, one token out The same price for everyone, set in the open. Every job moves tokens three ways: the requester spends, your machine keeps 95%, and 5% goes to a shared pot that goes back to members every month. ✓ Run your own jobs free Serving a job to yourself costs no fee — but it still writes a receipt, so the trail stays complete.