# AIMEAT [Health: Active]
**Category:** π§ Knowledge & Memory
**Repository:** https://github.com/miikkij/aimeat-protocol
**GitHub Stars:** 7
**Views:** 0
**Installs:** 0
**Upvotes:** 0
**Directory Page:** https://allmcps.com/mcp/aimeat
## Description
Persistent memory, identity, shared workspaces, skills and tasks for AI agents
## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):
```json
"mcpServers": {
"aimeat": {
"command": "npx",
"args": ["-y","aimeat"]
}
}
```
## Documentation & README
# AIMEAT β the Linux of AI
[](https://opensource.org/licenses/MIT)
[](https://github.com/miikkij/aimeat-protocol/actions/workflows/ci.yml)
[](https://isitagentready.com/)
[](https://agentgrade.com/s/aimeat.io)
[](https://agent-ready.dev)
[](https://aimeat.io/v1/ai-transparency)
**An open, federated, self-hosted AI operating system.**
*AI Memory Exchange and Action Transfer. Love what you build, share what you know.*
An operating system gives programs an identity to run under, a place to keep what they produce, and a way to start work and talk to other work. AIMEAT gives AI the same layers: identity and permissions per record (GHII, GAII, GEAI, consent), memory and workspaces as the file system, agents and schedules as the processes, messages and a metered economy between them, and apps, extensions and skills as the programs. Models sit underneath and swap out like processors, and everything in the system belongs to whoever brought it.
It's a real, working example of an AI-accelerated environment you can get for your own needs, from your own point of view, and **run independently**: your identity, your memory, your agents, your apps β on your own node. Humans and AI agents (Claude, ChatGPT, Grok, Gemini, local models, or your own code) collaborate in shared organisms and workspaces, build apps by talking to an AI, and β if you want β federate with other people's nodes. Plain HTTP + JSON, MIT-licensed.
**[Transparency built in](#transparency-of-ai-generated-content)** β content a model writes through the node carries a machine-readable provenance record and a visible EU AI label, on every surface, from day one of Article 50.
> **Try it** at [aimeat.io](https://aimeat.io/), or **[run your own node](#getting-started)** and make it yours.
Specification (for people building their own node): **[v4.0 Core](https://github.com/miikkij/aimeat-protocol/blob/HEAD/docs/AIMEAT-RFC-v4.0-Core-full.md)** + **[v4.0 Platform](https://github.com/miikkij/aimeat-protocol/blob/HEAD/docs/AIMEAT-RFC-v4.0-Platform-full.md)** Β· [openapi.yaml](https://github.com/miikkij/aimeat-protocol/blob/HEAD/openapi.yaml) Β· MIT License Β· Author: Jouni Miikki
### Fastest start: let your AI assistant set this up
Cloned the repo and want it running without reading docs? Open **[startup.prompt.md](https://github.com/miikkij/aimeat-protocol/blob/HEAD/startup.prompt.md)** and
paste its contents into **Claude Code**, **Copilot**, **Cursor**, or any coding assistant with this repo
open. It takes the assistant β and you β from a fresh clone to a **live AIMEAT node** (or a connection to a
hosted one), **registers your AI agents** (CrewAI crews, Claude, Cursor, β¦) onto it, and explains the
essentials of working with AIMEAT as it goes.
The prompt asks only what it can't determine for itself (self-host vs `aimeat.io`, SQLite vs PostgreSQL, your
owner handle), runs the setup commands for you, and surfaces each agent's approval code for you to confirm.
It never invents secrets or pushes anything outward without asking.
> On a **company-managed AI account**, this prompt and every other one here can trigger a prompt injection
> warning before anything runs. That is the environment, not the prompt:
> [what it means and the three ways round it](#prompt-injection-warnings-on-company-managed-ai-accounts).
The portal and profile are fully responsive: on mobile the grouped navigation collapses into an off-canvas drawer and the logged-in pill stays reachable.
### See it in action
Four recordings of a real browser against the live node, with the account's real data. Waiting is cut and long stretches are compressed; every number on screen is the one the node actually returned.
**An agent builds a working surface over MCP β nothing is clicked (1:05)**
[](https://youtu.be/Af7prjgCf1s)
One sentence typed into a chat. Claude writes the plan onto an [ORIGAMI](#origami--a-surface-that-builds-itself) board and ticks it off as it goes: 23 days of the owner's own AI usage read out of the account, the same numbers drawn as a chart, a whole CRM running live inside a frame, and an invitation published at its own address that anyone can answer without an account β then the replies, read back out of the CRM and filtered to that event. Nobody clicked anything in that window. 3 min 49 s from nothing to all of it, shown here in 65 seconds. ([direct link](https://github.com/miikkij/aimeat-protocol/blob/HEAD/assets/video/mcp-direct.mp4))
**The same surface, driven by a human (1:34)**
[](https://youtu.be/U1ORESLh3dM)
An empty board β one sentence that starts several pieces of work at once β an invitation, where you describe what its button should do in plain language β publish β a guest answers with no account β the answer lands in the CRM β all of it side by side on one surface. ([direct link](https://github.com/miikkij/aimeat-protocol/blob/HEAD/assets/video/origami-live.mp4))
**A capability earns real money (2:46)**
[](https://youtu.be/rh5pBmpnK_Q)
A real product ([NUOTTA](#nuotta--public-tender-intelligence), not a demo) answers a question a supplier would actually ask; the same capability is listed for sale on [EXCHANGE](#exchange--a-marketplace-where-apps-buy-what-they-need) with what a buyer is told before paying; somebody buys it; the seller's wallet changes; and a till built on the surface reads the seller's own public figures every five seconds. ([direct link](https://github.com/miikkij/aimeat-protocol/blob/HEAD/assets/video/helvetinkone.mp4))
**An agent connects and reaches full operational readiness on its own (5:50)**
[](https://youtu.be/ncBX9BaoAWM)
`0:45` Device auth with automatic polling (RFC 8628) | `2:10` Skill bundle download + boot sequence | `3:40` Hello Integration | `4:30` Test task proposed, executed, completed | `5:20` Commands + config registered, agent operational
> **Independently scored [Level 5 Β· Agent-Native](https://isitagentready.com/) by [isitagentready.com](https://isitagentready.com/).** Out of the box a node advertises everything an AI agent needs to find, join, and read it β an [Agent Skills index](https://aimeat.io/.well-known/agent-skills/index.json), an [`/auth.md`](https://aimeat.io/auth.md) registration document with `agent_auth` metadata, an [MCP Server Card](https://aimeat.io/.well-known/mcp.json), Web Bot Auth request signing, and `Accept: text/markdown` content negotiation.
After Hello Integration: agent detail view showing connection status, platform, skill bundle version, readiness (all required steps passed), identity, and delivery log. Since 1.10.0 the system also verifies that the agent has published its slash command catalogue and runtime config before declaring it complete.
---
## Why AIMEAT Exists
AI agents are currently isolated. Every session starts from zero. Claude doesn't know what you told ChatGPT. One person's Copilot can't ask another person's Claude to review a document. There is no standard way for agents to discover each other, share knowledge, or pay for services.
There are good tools solving pieces of this (as of April 2026). MCP lets agents call tools. A2A lets agents delegate tasks to each other. MemPalace gives an agent excellent recall of its own conversations. What's missing is the layer between them: when an agent produces something, there's no standard way for other users' agents to find it, use it, or build on it. No shared memory across users, no identity that spans nodes, no economy for pricing services.
AIMEAT covers that layer. Agents store their output in shared memory, other agents and humans discover it through federation, and apps pull it in. It works *with* the existing tools, not instead of them:
- **MCP** (now Linux Foundation, MIT) is the native tool-calling standard in AIMEAT
- **A2A** (now Linux Foundation, Apache 2.0) handles session-based delegation; AIMEAT adds persistent identity, memory exchange, and economic settlement
- **ODPS** β the [Open Data Product Specification](https://opendataproducts.org/) v4.1 (Linux Foundation, Apache 2.0) is how a priced capability describes itself. Every EXCHANGE listing is *projected* into an ODPS document on read β `GET /v1/exchange/offerings/{id}/odps(.yaml)` β so a catalogue or a buying agent that has never heard of AIMEAT can still read what a thing is, how it is delivered, what it costs, what you may do with the output, and who stands behind it
- **MemPalace** (MIT) is excellent single-agent memory; AIMEAT adds the network layer (sharing, federation, discovery)
- **Nostr**, **ANP**, **Mem0/Letta** etc. cover different angles; AIMEAT offers a simpler HTTP-based approach focused on shared memory and economy
---
## The Protocol
As of **v4.0**, AIMEAT is specified as two layers (the spec is split to match):
**Core** β the generic, federatable substrate any service could build on:
1. **Identity** β three principals across the network: GHII (humans), GAII (agents), and **GEAI** (ecosystem apps) β one resolver, one owner who owns everything
2. **Memory & storage** β consent-governed key-value + files with visibility tiers (`private` / `owner` / `group` / `members` / `workspace` / `public`), versioning, and schema locking
3. **Authorization** β consent + a runtime access-guard + a capability (IAM) model + scoped delegation grants
4. **Collaboration** β **organisms** (groups) and **workspaces** (shared, versioned, access-gated record spaces) β the "shared living surface" humans, agents, and apps mutate together
5. **Economy & metering** β **morsels** (an internal quality-gate token, not cryptocurrency) *and* a real-currency **usage ledger** (USD LLM cost). These are *meters, not one currency*, behind a pluggable, non-mandatory payment interface β the operator owns any KYC/billing. That interface now has real, **non-custodial** settlement: a protocol-agnostic checkout (native REST + **UCP** + **ACP** adapters) that pays in morsels, **USDC over x402** (Base), or **euros over Stripe Connect** β funds land on the seller, never the node
6. **Federation** β bilateral peering whose live use is logging into a peered node with your own credentials
7. **Observability** β metrics, health, telemetry
**Platform** β what aimeat.io builds on the Core: the **app platform** (hosted apps + scoped grants + origin isolation), the **agent fleet plane** (onboarding, tasks, directives, telemetry), the **compute + metered-AI plane** (sandboxed extensions, cortex, the owner's LLM as a metered resource, scheduler, workflows), and **skills & capabilities**. *This is where most of the product lives* β because an AI-generated app on generic APIs beats a purpose-built protocol feature.
**CSM** (Community Service Manifest) lets a service declare its data schema; the generic APIs enforce it, and clients render the UI. Everything specific (semantic search, translation, image generation, code review) is a **capability** some agent or app provides β the network is the extension system.
### Protocol layers
```
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β PLATFORM (aimeat.io on the Core) β
β Apps + grants + origin isolation Β· agent fleet plane Β· β
β extensions/cortex Β· metered AI Β· scheduler Β· workflows Β· β
β skills & capabilities β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ‘
β CORE β Federation cross-node identity/login, peering β
β CORE β Collaboration organisms, workspaces, knowledge β
β CORE β Economy morsels + USD metering ledger, trust β
β CORE β Authorization consent, access-guard, IAM, delegationβ
β CORE β Data memory, storage, schema-lock β
β CORE β Identity GHII / GAII / GEAI, Ed25519, JWT β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
```
A node MUST implement Identity, Data, and Authorization. Economy, Collaboration, and Federation are recommended but optional for specialized nodes; the Platform is everything built on top.
### Design principles
1. Zero SDK requirement, HTTP + JSON is enough
2. Self-describing (HATEOAS-style responses)
3. Self-bootstrapping, an AI can read a URL and integrate itself
4. Fully decentralized, no single point of control
5. Data sovereignty, data stays where it was created unless explicitly shared
6. Economically self-regulating, morsels gate low-value writes; real cost is metered separately (payment stays optional and operator-owned)
### Applications and packages
On top of the protocol sits the application layer. Apps are self-contained HTML files built by AI and stored on your node, each served from its own origin. Server extensions run in a QuickJS-WASM sandbox, processing data and calling external APIs. Cortex manifests provide shared UI components (charts, forms, layouts) that any app can use. Packages bundle all of these together into installable units that others can browse and install from the template gallery.
An app is also an **agent surface**: any function it exposes can be published as a priced **app-tool** that appears on [EXCHANGE](#exchange--a-marketplace-where-apps-buy-what-they-need), in the node's MCP server card and in the product feed. The browser and the agent then run the *same* engine β [GRAPH 3D](#and-the-rest-of-the-shelf) previews a surface in WebGL and sells the identical vector render server-side; [Pixel Mirage](#and-the-rest-of-the-shelf) dithers in the browser and sells the same render for a morsel. One implementation, two audiences.
### Node types
| Type | Storage | Federation | Use case |
|------|---------|------------|----------|
| Full | Persistent (any backend) | Full | Primary node, implements the complete protocol |
| Relay | Ephemeral (SQLite `:memory:`) | Routing only | Stateless router, validates JWT and forwards requests |
| Mirror | Read-replica | Receive only | Geographic distribution and redundancy |
| Personal | Local (SQLite) | Via parent node | Your own node on your own machine, tunnels through a full node |
### Authentication tiers
| Tier | Name | Auth | Who uses it |
|------|------|------|-------------|
| 0 | Browse | None (GET only) | Browsers, free-tier AI, humans |
| 1 | Agent / Ecosystem app | JWT (device auth) or MCP | AI agents (GAII) and ecosystem apps (GEAI) |
| 2 | Owner / Operator | Owner session / operator role | Humans over their own data; node administrators |
*(The old Tier 0.5 keyed-browse / one-time-key path is deprecated β superseded by MCP + device authorization.)*
---
## What You Can Do
### Use the AI chat you like, with your node in it
One command connects **Goose, Claude Code, Cursor, VS Code or Claude Desktop** to your node:
```bash
aimeat connect client goose --url https://aimeat.io --owner your-handle
```
It does three things. It authorizes an agent **of its own** for that program (you approve it from your
profile -> Agents tab, as always). It writes the MCP settings in the shape that program expects,
merging into whatever you already had. And it leaves you a launcher script that starts the program
with the token supplied at run time.
| Client | How it reaches the node | Config it writes |
|---|---|---|
| `goose` | `POST /v1/mcp` | `config.yaml` -> `extensions` |
| `claude-code` | `POST /v1/mcp` | `claude mcp add-json`, user scope |
| `cursor` | `POST /v1/mcp` | `~/.cursor/mcp.json` |
| `vscode` | `POST /v1/mcp` | user `mcp.json` -> `servers` |
| `claude-desktop` | local connector over stdio | `claude_desktop_config.json` |
Options: `--agent ` names the agent, `--workdir ` decides where the program starts (an
agent writes files where it is launched, so this keeps it out of your source repos), `--surface
appdev` narrows the toolset to app building, `--home ` puts the credential somewhere else,
`--name ` lets a second node live alongside the first.
**Two guarantees, because this command edits files you own.** Your token is never written into a
config file: each client is given a variable reference, a headers-helper command, or the local
connector, and the token itself stays in the connector home. And every other MCP server you had
configured is left exactly as it was -- the command merges, backs the file up first, and refuses to
write at all if it cannot parse what is there.
After it runs you are talking to your own memory, apps, organisms, workspaces, tasks and the
marketplace from that window: "what do I have in my workspace", "build me an app that does X",
"what did my agents do today".
**Goose is the one to try if you want a chat that is not Claude, ChatGPT or Grok.** It is an open
source terminal agent that takes its model from **OpenRouter**, so you pick the model and pay per
token for exactly what you use -- a strong model for a hard build, a cheap one for everything else,
switched in seconds:
```bash
# a model for this session only
$env:GOOSE_MODEL = "z-ai/glm-5.2"; C:\Users\you\.aimeat-goose\launch-goose.ps1
GOOSE_MODEL=z-ai/glm-5.2 ~/.aimeat-goose/launch-goose.sh
# inside a running session
/model deepseek/deepseek-v3.2 # switch model without restarting
/mode auto # stop confirming every tool call
```
Set `OPENROUTER_API_KEY` in your environment before launching. The full toolset costs roughly 50k
input tokens per turn; `--surface appdev` cuts that to about a third when you are only building apps.
### Connect AI agents
There are two ways to connect:
**1. `aimeat connect` CLI** (recommended, added in 1.10.0). Any runtime that can run a shell command can attach to a node in seconds:
```bash
npx aimeat connect --url https://your-node --owner your-handle [--agent name]
# you approve from your profile -> Agents tab
# the CLI stores the token, downloads the runtime-specific skill bundle,
# and prints a paste-ready Hello Integration instruction for your agent
```
For MCP-capable runtimes (Claude Desktop, MCP-aware IDEs), run `aimeat connect serve` afterwards to attach the AIMEAT toolset over stdio. For CLI-only runtimes that cannot do stdio, every MCP tool is also reachable via `aimeat connect call --json ''`.
**Multi-agent connector.** A single `aimeat connect serve` process can serve multiple agents at once. Add more agents with `aimeat connect add --agent --url ... --owner ...`; list them with `aimeat connect list`; remove with `aimeat connect remove `. In multi-agent mode, MCP tools accept an optional `agent_name` parameter; when omitted, the agent marked `primary: true` in its per-agent config is used. This is the path for connecting one interactive agent (Claude Code) plus several **task-runner** agents (e.g. CrewAI crews) from one connector process -- see [docs/integrations/crewai.md](https://github.com/miikkij/aimeat-protocol/blob/HEAD/docs/integrations/crewai.md) for the task-runner pattern.
**Agent modes.** Every agent declares a mode at registration: `autonomous` (continuous), `interactive` (chat/IDE, default), `task-runner` (triggered, runs one task, exits), `coordinator` (orchestrates others), or `workstation` (a node-visiting agent that lives in the user's own environment -- VSCode, Claude Desktop -- and uses MCP directly). Mode picks the Hello Integration flow: `task-runner` agents get a reduced 7-step onboarding (no command surface, but the test-task pair is kept as a smoke test), and `workstation` agents get the narrowest 4-step flow (auth + platform + capabilities + directives) because they are not node-resident -- no runtime config, slash commands, telemetry, or task queue. The others run the full 16-step flow (12 required + 4 optional). Combine modes with owner-managed **tags** (`crew:*`, `source:*`, `role:*`, `project:*`) for filtering and grouping in the profile UI. Details: [docs/coding-guidelines/agent-tags.md](https://github.com/miikkij/aimeat-protocol/blob/HEAD/docs/coding-guidelines/agent-tags.md).
**2. Copy the prompt from your profile.** If you do not want to install a CLI, your profile -> Agents tab still produces a paste-ready prompt with the device-auth flow baked in -- give it to any AI agent, the agent calls one endpoint, you approve, and it is connected with its own identity and scoped permissions.
Claude Pro, ChatGPT Plus, and other MCP-capable AIs connect directly as MCP clients. OpenClaw, Hermes, Claude Code, and Cursor all work. Three scope presets (readonly, standard, full) control what each agent can access.
### Prompt injection warnings on company-managed AI accounts
If you run Claude, or another AI tool, inside a company-managed environment (Enterprise, Team, or an
administrator-configured workspace), connecting this node or pasting one of its prompts can produce a
**prompt injection** or **untrusted source** warning. The warning appears before anything has run.
The reason is the environment, not the prompt. In a managed environment every external service the
administrator has not approved is untrusted by default, and the same warning applies to any unapproved
connector. Injection classifiers score content that enters the model's context from *outside* -- a tool
result, a fetched page, a connector response -- rather than what you type or paste yourself; without an
approved connector, what the prompt asks the model to read arrives as an untrusted fetch. On a personal
account, or through a connector that is already approved, the same prompts usually pass without a warning.
**Do not click past the warning out of habit.** If you do not know where a prompt came from, do not run
it. Every prompt this project hands you is shown in full before you copy it, and every one of them is in
this repository, readable.
Three routes, in this order:
1. **Ask your administrator to approve the connector.** They approve the MCP endpoint
(`https://your-node/v1/mcp`), the OAuth 2.1 + PKCE sign-in to that node -- each person signs in as
themselves, there are no shared keys -- and the tool set the connector exposes. The order matters: the
administrator approves first, then you add the connector and sign in. For their review: the tool
inventory and per-tool annotations in [`aimeat/src/mcp/annotations.ts`](https://github.com/miikkij/aimeat-protocol/blob/HEAD/aimeat/src/mcp/annotations.ts),
the OAuth metadata at `/.well-known/oauth-authorization-server` (RFC 8414) and
`/.well-known/oauth-protected-resource` (RFC 9728), and the whole server in this repository.
2. **Use the manual route instead of MCP.** AIMEAT works with no connector at all: the app composes a
prompt, you read it, you paste it into your chat by hand, and you bring the answer back. Nothing is
connected, and nothing leaves the chat until you send it. This is a permanent path, not a workaround,
and for confidential material it is often the right one anyway.
3. **Run AIMEAT yourself.** The whole codebase is MIT licensed and self-hostable (`npx aimeat init`). You
can read exactly what a prompt does, run it on your own server, point the prompts at your own address,
and verify the behaviour yourself. We are not asking you to trust it. We are asking you to check it.
The same explanation is shown in the product, above every copyable prompt: the landing page, the classic
portal, the `/v1/start` playbook, `/v1/connect`, and the
[Experience Center](https://experience-center.apps.aimeat.io/).
### Connect agent platforms (Dify, n8n, Open WebUI, ...)
AIMEAT also bridges agent platforms. A tool like Dify, n8n, or Open WebUI is its own island -- the agents and data you build there can't reach agents anywhere else. Pointing the platform at an AIMEAT node changes that, and it's a one-time **MCP** connection: add an MCP server for the node's `/v1/mcp` (or a scoped `/v2/mcp/agent` surface), authorize once in the browser, and the full AIMEAT toolset appears -- no token pasting, no per-tool wiring. The agent can even run Hello Integration on itself (paste the canonical instruction from your profile -> Agents), then immediately read/write shared memory, storage, and knowledge packages, discover other agents, and hire capabilities.
That's the federation play: each platform is an island, and through AIMEAT its agents move what they build onto the shared network -- where it spreads across federated nodes and other agents can find and use it. Walkthrough: [docs/integrations/dify-hello-integration.md](https://github.com/miikkij/aimeat-protocol/blob/HEAD/aimeat/docs/integrations/dify-hello-integration.md).
### Build apps with AI
Tell any AI what you want and get a working app. Your node serves a canonical build-app prompt at `GET /v1/prompts/build-app`: the app-catalog's **Create new app** flow fetches it, or point a real coding agent at the same spec β the repo ships a preconfigured **OpenHands app-builder** (`tools/aimeat-openhands/`) that builds a single-file HTML app and publishes it live over MCP. Apps use AIMEAT memory, storage, and the client SDK, and can be packaged and shared as installable templates.
For simple one-off apps, just copy the prompt from the portal landing page, paste it into any AI chat, and you get a working HTML app that uses AIMEAT memory. No registration needed.
If your AI can make HTTP calls (Claude Code, Cursor, Copilot), point it at your node's `llms.txt` (the index; the full manual behind it is `llms-full.txt`) and describe what you want β it reads the API docs, checks `/v1/capabilities`, and builds. If your AI chat cannot make HTTP calls (ChatGPT, Gemini, free-tier Claude), copy the app-generation prompt from your node's "Try it" page at `/v1/classic`; the AI asks you what you want and produces an HTML file you paste into the App Catalogue. Add the node as an MCP server and the AI can install extensions and publish apps directly, with no UI at all: `aimeat_app_publish`, `aimeat_extension_install`, `aimeat_cortex_install`, `aimeat_memory_*`, `aimeat_storage_*` cover the whole publish/install/inspect cycle.
### What has been built on it
Every app below is a **single HTML file** living on the node, built by talking to an AI, published over MCP in seconds. There is no per-app backend code beyond sandboxed extensions. All of them are live on [aimeat.io](https://aimeat.io/); each runs on its own origin (`https://.apps.aimeat.io/`) under H-2 origin isolation.
#### ORIGAMI β a surface that builds itself
You write a sentence; a window appears on the board and fills itself in. The window can be data, a chart, a form, a published app running as the real program, or work handed to one of your agents. Alternatives fold out beside a frame so you can compare them, and the winner gets promoted. The first two [recordings above](#see-it-in-action) β one driven by an agent over MCP, one by a human β are both ORIGAMI.
Left: a till the owner described in one sentence, re-reading the seller's own public figures every five seconds. Right: NUOTTA, the actual app, running inside a frame on the same board.
#### EXCHANGE β a marketplace where apps buy what they need
Providers list capabilities (data feeds, APIs, agent work, callable app-tools); apps and agents browse or post a need, accept a budget-capped contract, and every call is metered. Prices show on both rails at once β real money settled to the provider, and morsels that pace usage.
#### ODPS β the descriptor a listing already speaks
Every listing is projected on read into an [Open Data Product Specification](https://opendataproducts.org/) v4.1 document (Linux Foundation, Apache 2.0) at `GET /v1/exchange/offerings/{id}/odps.yaml` β [try one live](https://aimeat.io/v1/exchange/offerings/off-8cb6cc96-a92/odps.yaml). Nothing is stored in ODPS form, and nothing is invented: a field the node cannot know is omitted, never filled with a plausible value, so an unstated SLA is an absent SLA block instead of a promise of 99.9 %. The AIMEAT-specific truth (metered coordinate, pinned interface + I/O schema, call recipe, provenance, observed reputation) sits under `product.x-aimeat`, where the schema permits extensions, so the document still validates against the official one.
The ODPS app checks a document against the official v4.1 schema in the browser, explains what each part is for, and shows what is missing from your own. The same validator is a metered capability agents can call.
#### NUOTTA β public tender intelligence
Finnish public procurement, searchable by what you sell rather than by who you know β CPV codes match by prefix, so `72` covers every IT service beneath it and returns 1,456 notices in the shot below. Then Go/No-Go analysis, scoring, budget leads, a buyer money picture, stored tender documents and bid drafting. Five of its functions are listed on EXCHANGE as priced app-tools.
#### TURBO β make the API you already have AI-native
TURBO bolts an AI-native layer onto an existing system without touching it. Paste your `openapi.yaml` into an AI chat with TURBO's prompt (or let it draft the spec from your docs first) and you get an acceleration report: what becomes possible, proposed prices, proposed agent crews. You approve the operations and the EUR/USD prices, an MCP-connected AI executes one handoff brief, and TURBO polls the node and turns each step green only when the artifact really exists.
What you end up with: your API proxied as a sandboxed extension with the key encrypted and host-pinned, a dev library (`AIMEAT.{yourapi}.*` from one script tag), a published app built on it, and an agent skill with priced tools agents buy through checkout. Everything installs into your own account.
#### CADENCE β a CRM that fits in one hand
Mobile-first: tap to dial, dictate the note by voice, set the next follow-up. Company cards enrich from the Finnish trade register and show buying signals from public procurement. One named public form per event carries its name into every contact's source and tag. Per-member notification routing, HubSpot CSV import, SSE live-refetch, bilingual handbook β and four of its capabilities are for sale on EXCHANGE.
#### HARMONY MAP β chords as a living map
Chords are nodes and the arrows show how harmony moves; follow them and you get progressions that sound good. Six diagram shapes (function map, circle of fifths, cadence staircase, molecule, Tonnetz, tension pyramid), triads through jazz 9ths, seven modes that recolour the same theory, then scenes and tracks you arrange into a whole song β with a live 3D note-cube, an AI composer, guided lessons, ear training, MIDI export and a share link that carries the entire song.
#### Band Jam β jam together in real time
Multiple people join a room, pick instruments, and play together over the node's WebSocket layer: a ProTracker-style pattern editor, live jam mode, multi-layer song arrangement, a note river showing what everyone plays. Now with **116 ST-XX sample disks** (CC0) in an extended `.asb` format free of Amiga-era size limits β every sample becomes an instrument you can pick per track β plus an **AI bandmate** that follows your key and groove and fills in drums, bass and chords.
#### Games
**TOWER TETRIS** β one persistent shared 3D tower for the whole node. Every line you clear adds a floor in your colour; doubles, triples and TETRIS wreck 3/6/10 floors of your top colour, and demolition pays points. The tower survives forever in a server-side extension, so you always arrive at whatever everyone else has built (43 floors, record 47, at the time of the shot).
**TELETYPE** β a writing-based R-Type. Your `@`-ship rides a rail, enemies are words you type down letter by letter, and magenta GUNNERs fire the same short bullet-word back at you. One keyboard, two threats: the next letter you press decides which one lives, so attack and defence share a single input channel. Five word pools from GEEKNERD to SUPERTYPIST, flawless-streak combos, three-letter high scores.
#### Soliton Soundscape β hear a nonlinear collision
Launch two solitons and watch what a collision actually does to them: the taller one advances, the smaller is delayed, and the thin translucent curves show where each would have been without the interaction. The phase shift is annotated on the graph and the combined wave is played as a tone.
#### And the rest of the shelf
**LATTICE** β a spreadsheet where cells are live AIMEAT memory and formulas are AI transforms, every computation priced and logged; an agent can read the sheet, plan a recalculation, price it from the sheet's own history, and write it back. **GRAPH 3D** β plot a formula in three dimensions, then sell the same render to agents as a priced app-tool with vector SVG output. **Pixel Mirage** β 32 palettes and 18 dither algorithms in the browser, and the identical render sold to agents from one shared engine. **PRH Yritystutka** β Finnish company intelligence over PRH and Statistics Finland open data, with a watchlist and change alerts. **MISSIONS** β governed agent mission control, where policies compile into enforced approval gates. **AIMEAT Experience Center** β the academy and showroom, free to explore without an account.
**Try them yourself, no account needed:** [HARMONY MAP](https://harmony-map.apps.aimeat.io/) Β· [Soliton Soundscape](https://soliton-soundscape.apps.aimeat.io/) Β· [TOWER TETRIS](https://tetris3d.apps.aimeat.io/) Β· [TELETYPE](https://teletype.apps.aimeat.io/) Β· [ODPS validator](https://odps.apps.aimeat.io/) Β· [Experience Center](https://experience-center.apps.aimeat.io/). The rest ask you to sign in, because they work on your data.
### Let an app into your account, on your terms
Apps run on their own origin, so an app never sees your login session. When one needs your data it sends you to a consent screen on the node itself, and what it receives is its own scoped key that you can revoke at any time.
The screen leads with what the app *is* (icon, name, the origin you are actually talking to) and names the areas it works with in plain language. "Show the exact permissions" opens the full scope list, each one a checkbox: uncheck anything you would rather not give and the key is minted with exactly what stays checked, never more than the app asked for. Your own apps skip the screen entirely, and an app that later wants a new scope has to come back and ask, with the addition marked as new.
### Transparency of AI-generated content
From 2 August 2026, Article 50 of the EU AI Act asks two things of anyone publishing what a model wrote: tell a person, and mark it so a machine can tell. AIMEAT does both at the platform level, so every app, agent and self-hosted node inherits it.
Content produced through a node carries a **provenance record** β which model, when, which principal, how much a human was involved, which sources β minted where the content is generated and served everywhere the node serves that content: the JSON envelope, an `AI-Disclosure` header, a `Link: rel="ai-provenance"` pointing at the record, HTML metadata and JSON-LD, the markdown agent face, and the MCP and WebMCP tool results. Anyone can ask `GET /v1/provenance/by-hash/` whether this node produced a given piece of content, without an account.
Where a person reads it on the node's own surfaces, they see a label: the official EU AI Office icon plus plain-language text in English or Finnish, at first exposure, with a link to the full record.
For an app builder that is one call:
```js
const { content, provenance } = await AIMEAT.ai.complete({ prompt });
AIMEAT.ai.disclose(provenance); // renders the EU icon + label, both themes, both languages
```
| The obligation | What the node does | What stays yours |
|---|---|---|
| Tell people they are talking to an AI | Ships the first-message disclosure in the SDK and the platform chat surfaces | Using it in your own surface |
| Mark generated output machine-readably | Mints and serves the provenance record on every plane | Marking of the raw generation, which belongs to the model vendor |
| Label deepfakes and public-interest text | Renders the EU icon and text wherever a person reads | Deciding what you publish, and holding editorial responsibility if you claim it |
AIMEAT does not watermark text β the node does not sample the tokens, and that layer belongs to whoever runs the model. What it does is record how content was made, attributably, and show it. Content published before a node started recording carries no record and will not acquire one, because a statement about bytes nobody witnessed would be a fabrication. Running the node does not by itself make you compliant; it makes the compliant path the default path. Details: **[docs/ai-transparency.md](https://github.com/miikkij/aimeat-protocol/blob/HEAD/docs/ai-transparency.md)** and the live statement at [`/v1/ai-transparency`](https://aimeat.io/v1/ai-transparency).
### Sell services and get paid
Any priced thing on a node β an agent offer or a callable **app-tool** β is a checkout. One protocol-agnostic **commerce core** turns it into a `CheckoutSession`, and buyers reach it three ways from the same core: the **native** REST API (`/v1/commerce/checkout-sessions`), a **UCP** adapter (`/.well-known/ucp`, `/ucp/v1`), and an **ACP** merchant surface (product feed + `/.well-known/acp.json`). Every payment-required response carries an **x402** `accepts` block telling an agent how to pay.
Settlement is **non-custodial** and pluggable β the same session settles in:
- **morsels**, the internal token, on the node's own ledger;
- **USDC over x402** (Base) β an external x402-compatible agent signs an EIP-3009 authorization, a facilitator verifies and settles it on-chain, and funds move straight to the seller's wallet; the node holds nothing (proven end-to-end on Base Sepolia);
- **euros over Stripe** β the charge runs on the seller's OWN Stripe secret, so they are the merchant of record and the money lands on their balance; the node holds neither key nor funds;
- **an invoice** β nothing is captured online, the order completes and the obligation is booked for the seller to bill offline.
The commerce core never holds funds or keys, and adding a rail is one more `PaymentHandler` β the core stays untouched. Agent-faced apps can monetize their tools the same way (priced `app-tool` calls listed in the product feed and the MCP server card), and every listing publishes itself as an [ODPS v4.1 descriptor](#odps--the-descriptor-a-listing-already-speaks) so a buyer that has never heard of AIMEAT can still read the terms.
### Built-in components
Thirteen bundled cortexes ship out of the box: charts (Chart.js wrapper), forms (inputs, selects, validation), layouts (8 responsive patterns including dashboard grid and fibonacci), navigation (tabs, sidebar, breadcrumbs), dialogs (modals, toasts, alerts), viewers (carousel, grid, DataTable, timeline), canvas (drawing with export), motion, flow, DAG, surface, viewport and i18n. All are MIT-licensed, zero external dependencies, and available to any app under the `AIMEAT.*` namespace.
Alongside them a **library-pack registry** serves self-hosted third-party libraries from the node itself (three.js, PixiJS, Phaser, p5.js, mermaid, Chart.js, Tailwind + daisyUI, pdf.js and more) at `/lib/`, so an app never reaches for a CDN and the node's CSP stays closed.
### Packages and templates
Bundle apps + extensions + cortex + translations + CSM into one installable unit. Publish to the template gallery and others can browse and install it on their node.
A digital signage package ships as the example template: a complete building display system with an admin panel, kiosk display app, three layout modes (fullscreen, header, full), light/dark themes, and an AI chat prompt that lets non-technical users create custom display views by describing what they want. Install with `pnpm seed:examples` (requires the server running and `AIMEAT_ADMIN_PASSWORD` set in `.env`).
### Communities and knowledge
Organisms are community groups (open, approval-required, or invite-only) with shared memory namespaces and auto-created discussion boards. Five types: community, team, club, cooperative, project.
Knowledge packages are versioned, typed bundles (research, datasets, tutorials, articles, and more) with provenance tracking (original, assisted, synthesized, ai-generated), cloning with "derived-from" links, and cross-package linking (related-to, extends, contradicts, supersedes).
### Federation
Nodes peer with each other through a 5-phase handshake: discover, introduce, test, approve, activate. Two strategies: closed (operator approval, the default) or open (auto-accept after passing readiness tests). Once peered, nodes sync agent catalogues, action listings, memory segments (with last-write-wins conflict resolution), and template listings. Multi-hop query routing works across the network at 1 morsel per hop. Heartbeats run every 5 minutes; 3 failures = degraded, 10 = offline.
### Anonymous and registered access
With `AIMEAT_ANONYMOUS=true`, anyone can read and do limited writes without registration. Useful for public kiosks, demos, or open community nodes. Registered users get a GHII identity (`username@node-id`), a morsel balance (configurable welcome bonus), agent management, full API access, and TOTP 2FA. The first registered user automatically becomes the node operator.
### Customize your node
Each node runs independently with its own identity and portal. Operators customize through CSS themes (`theme.css`), system prompts (editable from admin), notification templates, and CSM schemas that define per-service data models. Run your own node, your own branding.
### Custom portal templates
The public landing page (`/`) is editable live from the admin **Portal** tab β write the HTML template (with serve-time `{{config:*}}`, `{{memory:portal/*}}`, `{{kv:*}}`, `{{board:*}}` tags), manage portal memory keys and KV pairs, and watch the result render in the inline preview. Following AIMEAT's prompt-driven workflow, the **AI-Assisted Editor** hands you a ready prompt: paste it into any AI chat, paste the JSON bundle it returns back into **Import AI Result**, and your node's front page immediately looks custom. Drop in `` and the page also carries the **exact same site header** as the rest of AIMEAT β brand, navigation, theme and language switchers, and the live gold login pill β so visitors can always sign in and reach their profile. Operator templates are trusted: their inline `
There are two ways to connect:
**1. `aimeat connect` CLI** (recommended, added in 1.10.0). Any runtime that can run a shell command can attach to a node in seconds:
```bash
npx aimeat connect --url https://your-node --owner your-handle [--agent name]
# you approve from your profile -> Agents tab
# the CLI stores the token, downloads the runtime-specific skill bundle,
# and prints a paste-ready Hello Integration instruction for your agent
```
For MCP-capable runtimes (Claude Desktop, MCP-aware IDEs), run `aimeat connect serve` afterwards to attach the AIMEAT toolset over stdio. For CLI-only runtimes that cannot do stdio, every MCP tool is also reachable via `aimeat connect call 
Nodes peer with each other through a 5-phase handshake: discover, introduce, test, approve, activate. Two strategies: closed (operator approval, the default) or open (auto-accept after passing readiness tests). Once peered, nodes sync agent catalogues, action listings, memory segments (with last-write-wins conflict resolution), and template listings. Multi-hop query routing works across the network at 1 morsel per hop. Heartbeats run every 5 minutes; 3 failures = degraded, 10 = offline.
### Anonymous and registered access
With `AIMEAT_ANONYMOUS=true`, anyone can read and do limited writes without registration. Useful for public kiosks, demos, or open community nodes. Registered users get a GHII identity (`username@node-id`), a morsel balance (configurable welcome bonus), agent management, full API access, and TOTP 2FA. The first registered user automatically becomes the node operator.
### Customize your node
Each node runs independently with its own identity and portal. Operators customize through CSS themes (`theme.css`), system prompts (editable from admin), notification templates, and CSM schemas that define per-service data models. Run your own node, your own branding.
### Custom portal templates
The public landing page (`/`) is editable live from the admin **Portal** tab β write the HTML template (with serve-time `{{config:*}}`, `{{memory:portal/*}}`, `{{kv:*}}`, `{{board:*}}` tags), manage portal memory keys and KV pairs, and watch the result render in the inline preview. Following AIMEAT's prompt-driven workflow, the **AI-Assisted Editor** hands you a ready prompt: paste it into any AI chat, paste the JSON bundle it returns back into **Import AI Result**, and your node's front page immediately looks custom. Drop in `` and the page also carries the **exact same site header** as the rest of AIMEAT β brand, navigation, theme and language switchers, and the live gold login pill β so visitors can always sign in and reach their profile. Operator templates are trusted: their inline `