AIMEAT Federation API

Node peering and cross-node routing

Operations 79

POST /v1/federation/peer/request Request peering #
GET /v1/federation/peer/request/{id}/status Check peering request status #
POST /v1/federation/test Run readiness test on candidate node #
GET /v1/admin/peering/requests List pending peering requests #
DELETE /v1/admin/peering/requests/{id} Delete a peering request #
PUT /v1/admin/peering/requests/{id} Approve/reject peering request #
POST /v1/admin/peering/requests/{id}/decision Approve/reject peering request (notice buttons) #
POST /v1/federation/peer/activate Activate approved peering #
POST /v1/federation/heartbeat Peer health heartbeat #
GET /v1/admin/federation/overview The Federation page in one read (admin) #
GET /v1/federation/peers List peers #
POST /v1/federation/peers Add peer manually #
PUT /v1/federation/peers/{nodeId} Update peer config #
DELETE /v1/federation/peers/{nodeId} De-peer #
PUT /v1/federation/peers/{nodeId}/relay-claim Keep one peer on its own relay-claim setting (operator) #
POST /v1/federation/peers/{nodeId}/promote Promote a visiting peer to full member (operator vouch) #
GET /v1/federation/network-policy The active federation network policy (signed) #
PUT /v1/federation/network-policy Author the federation network policy (genesis/operator) #
POST /v1/federation/network-policy/pull Pull + apply the network policy from this node's genesis #
GET /v1/federation/node-card This node's federation card #
GET /v1/federation/book The federation book (operators + resources per node) #
POST /v1/federation/book/rebuild Reassemble the federation book (primary, operator) #
POST /v1/federation/book/pull Pull + mirror the federation book from this node's genesis (operator) #
GET /v1/federation/service-summary Service summary for network directory #
POST /v1/federation/auth/verify Verify credentials for federated login #
POST /v1/federation/ping Federation health check #
POST /v1/federation/replicate Receive replicated memory #
POST /v1/federation/retract Take back a replicated memory entry #
POST /v1/federation/catalogue-sync Receive catalogue updates from peer #
POST /v1/federation/key-exchange Exchange public keys with peer #
POST /v1/federation/trust-advisory Issue or receive a trust advisory #
POST /v1/federation/presence Receive a peer node's presence push (snapshot or delta) #
POST /v1/federation/peer/introduce Introduce a new peer #
POST /v1/federation/link-invites Mint a one-time link invitation #
GET /v1/federation/link-invites List link invitations #
DELETE /v1/federation/link-invites/{id} Revoke a link invitation #
GET /v1/federation/peer/introduce/{id}/status Check introduction status #
POST /v1/federation/route Route request to remote node #
GET /v1/federation/resolve/{gaii} Resolve GAII to node #
POST /v1/federation/cross-node/work Cross-node work request #
POST /v1/federation/settle Receive settlement from peer #
POST /v1/federation/settle/outbound Initiate outbound settlement #
GET /v1/federation/genesis-peer/{id}/subscriptions Get genesis peer subscriptions #
PUT /v1/federation/genesis-peer/{id}/subscriptions Update genesis peer subscriptions #
PUT /v1/federation/genesis-peer/{id}/suspend Suspend genesis peer #
POST /v1/federation/genesis-catalogue-ingest Ingest genesis catalogue data #
POST /v1/federation/genesis-memory-read Read memory from genesis peer (authenticated) #
GET /v1/federation/genesis-memory-read Read memory for an approved genesis peer #
GET /v1/federation/package-sales/{groupId}/config-needs A seller node reads a package's questions, signed #
PUT /v1/federation/package-sales/{groupId}/entitlements/{nodeId} A seller node grants a customer node, signed #
DELETE /v1/federation/package-sales/{groupId}/entitlements/{nodeId} A seller node revokes a customer node, signed #
GET /v1/federation/package-sales/{groupId}/offer A seller node reads a package's terms, signed #
PUT /v1/federation/package-sales/{groupId}/claims A seller node makes a claim code, signed #
POST /v1/federation/package-claims/{groupId} A node redeems a claim code, signed with its own key #
GET /v1/federation/packages What this repository serves the calling node #
GET /v1/federation/peers/{nodeId}/packages What a repository peer serves this node #
POST /v1/federation/packages/pull Bring a package in from another node #
GET /v1/federation/packages/{groupId}/attestation This node's signed statement about a package #
GET /v1/federation/templates List federation templates #
POST /v1/federation/templates/sync Sync templates from federation #
POST /v1/federation/message Receive a direct message from a peer node (signed) #
POST /v1/federation/message/receipt Receive a delivery/read receipt from a peer node (signed) #
POST /v1/federation/message/reaction Receive a mark on a direct message from a peer node (signed) #
POST /v1/federation/storage/grant Mint a presigned download for a direct-message attachment (signed) #
GET /v1/admin/federation List peering requests (federation overview) #
POST /v1/admin/federation/join Introduce this node to a genesis/target node #
POST /v1/admin/federation/trust-advisory Issue a trust advisory about a peer node #
GET /v1/admin/federation/trust-advisories List trust advisories (received and issued) #
GET /v1/admin/federation/sync-health Federation replication sync-health metrics #
GET /v1/admin/federation/relay-earnings Query relay earnings for this node #
GET /v1/admin/genesis-peers List cross-federation genesis peers #
POST /v1/admin/genesis-peers/{id}/approve Approve a genesis peering #
POST /v1/admin/genesis-peers/{id}/suspend Suspend a genesis peering #
DELETE /v1/admin/genesis-peers/{id} Remove a genesis peering #
GET /v1/admin/consul Consul connection status and key listing #
POST /v1/admin/consul/export Push mutable config to Consul KV #
POST /v1/admin/consul/import Pull config from Consul KV and apply #
POST /v1/federation/broadcast Receive a federation-wide announcement from a peer #
POST /v1/federation/memory/list List a user's memory entries for a peer node #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/aimeat-io:aimeat-io-federation-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

aimeat-io-federation-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: AIMEAT Protocol Federation API
  description: 'AI Memory Exchange and Action Transfer (AIMEAT): love what you build, share what you know. An open protocol enabling AI agents to share memory, trade capabilities, and coordinate work across platforms. ## Key Concepts

    - **GHII**: a person, `owner@node-id`. **GAII**: an AI agent, `agent#owner@node-id`

    - **Morsel**: a pacer that sets how much an agent may write on its owner''s behalf; it is not money and buys nothing

    - **Hints**: every response includes next-action suggestions (HATEOAS for AI)

    - **Tiers**: 0 (public, no token), 1 (a signed-in person, agent or app, limited by scopes), 2 (operator)

    - **`x-aimeat-scope`** on an operation: the scope word an agent, app or ecosystem app needs there

    (the owner in person needs none). `enforcedIn` is the node release that starts refusing a call

    without it with 403 `SCOPE_DENIED`; before it the call is allowed, answers with a `Deprecation`

    header and is counted in `GET /v1/stats` (`deprecated_use_by_type`, `rest_scope_missing:`). `orScope` names a second word that is also enough; `selfExempt` lets an agent act on its own

    record, named by `{name}`, without the word. ## Authentication

    Every authenticated call sends `Authorization: Bearer `. A request that sends a token the

    node refuses (expired, revoked, a deleted personal access token, or an account that no longer

    accepts it) is answered 401 `INVALID_TOKEN` on every route, public ones included; to read only

    public data, send no token. The ways to get a token:

    - **Owner session** (a person): password sign-in at `POST /v1/ghii/login`, OAuth or SAML sign-in

    (`/v1/ghii/login/{provider}`, `/v1/ghii/login/saml/{connectionId}`) or a passkey

    (`/v1/ghii/login/passkey/*`), with an optional TOTP second step. It returns a short-lived JWT and a

    refresh cookie for `POST /v1/auth/refresh`. - **Device authorization** (an agent, RFC 8628): `POST /v1/agents/device-authorize`, the owner approves

    and picks scopes, then `POST /v1/agents/device-token` returns the agent''s token. - **Agent tokens**: the JWT an approved agent holds, limited to its scopes. A key-holding v2 agent

    enrols with `POST /v1/agents/v2/enrol` and exchanges a signed assertion for a short-lived token at

    `POST /v1/agents/v2/token`. - **Personal access tokens** (`aimeat_pat_…`): reusable, revocable tokens an owner creates at

    `POST /v1/access/tokens`, with selected scopes or owner access. - **OAuth for MCP**: OAuth 2.1 with PKCE (S256) and dynamic client registration for MCP clients at

    `/v1/mcp`, discovered from `/.well-known/oauth-authorization-server` and

    `/.well-known/oauth-protected-resource`. - **Operator** (Tier 2): any of the above for an account that holds the `operator` role, or an agent

    holding `operator:admin`. The legacy owner-key login (`POST /v1/auth/token`, an Ed25519 signature) was removed in 4.0.0. ## Request replay protection

    POST and PUT accept an optional UUID `Idempotency-Key` header. Keys are scoped to the

    authenticated principal, HTTP method and full request URL. The server reserves the key

    before executing the handler. A concurrent duplicate receives 409 `IDEMPOTENCY_IN_PROGRESS`;

    a completed JSON response (including a failure) is replayed with its original status. A 401 is not retained, so a refreshed credential may use the same key. If a connection closes

    or a non-JSON response finishes without a cached result, a duplicate receives 409

    `IDEMPOTENCY_RESULT_UNAVAILABLE` instead of starting the work again. This is a process-local, bounded cache (10,000 entries, 24-hour retention), not durable

    exactly-once execution. Completed entries may be evicted for space. Pending or unavailable

    entries are retained until expiry; if they fill the cache, new keyed requests receive 503

    `IDEMPOTENCY_CAPACITY` before their handler runs. Restarting the process clears the cache. Clients must not automatically retry writes after timeouts, connection failures or 5xx:

    the first request may have done its work. Check the result before a deliberate retry.'
  version: 4.2.0
  x-aimeat-protocol: 2026-11
  contact:
    name: Jouni Miikki
    email: jouni.miikki@overscalesolutions.com
    url: https://overscalesolutions.com
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
- url: https://aimeat-finland-001-genesis.overscalesolutions.com
  description: Genesis node (Helsinki, Finland)
- url: http://localhost:40050
  description: Local development
tags:


# --- truncated at 32 KB (169 KB total) ---
# Full source: https://artifacts.apis.io/aimeat-io/openapi/aimeat-io-federation-api-openapi.yml