> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Federation

> Distinguish per-Neuron Agent API sessions from explicitly federated operations

An Agent API account and its JWT belong to the Neuron host that issued them. Build a separate client and session for each host.

Some documented operations can work with objects or actors on another Neuron. Examples in the current specification include retrieving or signing federated contracts and sending XMPP messages to another address. Remote Quick Login has a separate session-oriented description.

## Confirm support for each operation

* Do not send a JWT to a different host.
* Do not reuse a host-bound HMAC signature against another host.
* Do not assume every identifier can be resolved or mutated across federation.
* Use only the federation behavior explicitly described for the operation and verified on the target deployments.
* Treat acceptance by the local Neuron and completion across the network as separate states when the workflow is asynchronous.

See [Trust and federation](/platform/trust-and-federation) for the conceptual model and [Events and asynchronous state](/neuron-api/events-and-asynchronous-state) for completion handling.