Repository navigation
AIMEAT 3.27.0
AIMEAT 3.27.0 is the last 3.x feature release before 4.0.0. It covers everything since 3.15.0. The full list, written for people rather than developers, is on every node at /v1/changelog (aimeat.io/v1/changelog).
What you get
- Your AI does more on your behalf. Make an agent from your home page and choose the computer that runs it. Your AI finds the node's guidance as built-in skills as soon as it connects, and the connect guide covers 15 AI tools, each checked against its maker's own pages.
- Your own AI accounts, side by side. The AI page lists your providers, which one answers what, and which models are allowed. A model catalogue says what each model can do and what it costs, apps and agents ask for a capability rather than a model, and one account takes over when another does not answer. An extension can be your AI provider without ever seeing your key.
- Decisions you set once. A decision model sits beside the text model to sort, screen and route what arrives. Decision rules let you write a judgement once for your apps and agents, and decision providers let you run that model on your own machine.
- Prices are money, and morsels pace. Every offer has an optional money price and a pacing amount in morsels per use. A free item stays free. Part of the pacing burns, and the rest goes to the person who offers the item. Shopping AIs using ACP and UCP see money prices only.
- Signed documents. Sign a document with a passkey, check any signed PDF, and (in a test phase) sign a PDF with the EU Digital Identity Wallet.
- You decide which AI may read what. Data classification, AI-made sound, pictures and files that say how they were made, and a view of how people and AIs find you and what they do on your apps.
- Apps and packages that are ready on the first day. Install packages, apps you buy come ready, your visitors' own AI can use your app, and themes can use fonts of your own.
For operators
- Federation: from this release a message from another node must name its audience and carry its send time. A message without them is refused by default.
AIMEAT_FEDERATION_AUDIENCE_REQUIRED=falseturns this off for now. In 4.0.0 the setting goes away. - What 4.0.0 removes is now announced on every use. The owner-key sign-in,
?token=on WebSocket upgrades, the federation format without delivery proof, the optional relay claim, the old morsel price fields, the legacy AI settings routes, the static TURN pair, a REST call without the scope word the route needs, and an MCP sign-in token used on REST. Each still works in 3.x. Each answer carriesDeprecationheaders, and each use is counted inGET /v1/statsunderdeprecated_use_by_type. Read docs/operations/upgrading.md before you move to 4.0.0. - The test money handler runs only on a loopback test node. If
AIMEAT_TEST_MONEY_HANDLERis set on a public node, the node ignores it, and the Security page shows it as critical. - A security review changed several defaults. The changelog entry of 2026-10-06 lists them.
- New operator guides: production deployment, backup and restore, upgrading, federation and bookkeeping, in docs/operations/.
The protocol
The next protocol edition, AIMEAT Core 2026-11, is published as a draft beside its conformance evidence and the Platform reference. It becomes normative with node 4.0.0. Until then, v4.0 applies, with its errata.
Install: npx aimeat@3.27.0.