> ## 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.

# Keys and signatures

> Choose where keys are managed and store the identifiers needed for signatures

Keys connect authenticated actors to signed identities, agreements, and data. Applications should treat key creation, key identifiers, signing authority, and signature verification as separate concerns.

## Choose who manages keys

| Integration                     | Where keys are managed                                                                                                                                                   |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Agent API or an SDK built on it | The application asks the Neuron's Agent interface to perform supported cryptographic operations; it does not behave like a direct XMPP client holding those private keys |
| Direct XMPP client              | The client owns the direct connection and private keys                                                                                                                   |
| MCP                             | The AI application receives only the scoped tools made available by the MCP server; it must not infer access to arbitrary signing operations                             |

The Agent API acts through the Neuron's Agent interface. Its name does not indicate an AI-agent-specific API.

## Key workflow

```text theme={null}
Choose a supported algorithm
        ↓
Create a key in the correct account context
        ↓
Persist the returned key identifier
        ↓
Associate it with the identity or signing workflow
        ↓
Verify the resulting signature or signed object
```

Do not hard-code an algorithm across a long-lived application unless the supported workflow requires it. Query or follow the algorithm guidance for the Neuron version you target.

## Application rules

* Keep passwords, JWTs, key passwords, private keys, and signing secrets out of source control and logs.
* Persist returned identifiers rather than parsing them from display text.
* Make the actor, key, payload, and intended signing purpose explicit.
* Do not claim legal effect or non-repudiation solely because bytes have a valid cryptographic signature; the identity, authorization, contract, policy, and verification context also matter.
* Treat retries carefully. A signing operation may have effects that should not be duplicated unless idempotency is explicitly documented.

## Build with signatures

* [Create cryptographic keys](/neuron-api/guides/creating-cryptographic-keys)
* [Digital signatures](/build/digital-signatures/overview)
* [Cryptography reference](/neuron-api/api-reference/cryptography/overview)