# Instance API

The complete registered Akasha HTTP surface, organized by capability and tied to its source contracts.

Source: https://docs.minds.sh/docs/api/instance



The instance API is the data and compute interface of an individual Mind. It stores memory, searches knowledge, manages model workloads, and exposes the state of the Akasha engine. The platform API manages accounts, organizations, provisioning, and billing; those are separate contracts.

The product contract is a dedicated Firecracker VM-based Akasha instance on both Free and Pro. The API families belong to that same engine on both plans. This reference verifies daemon source contracts; it does not certify that the current provisioning implementation already satisfies the Firecracker deployment requirement.

This reference accounts for **246 HTTP operations across 231 paths** in the current daemon source. Every operation links its registration and handler, documents declared request fields, records response assembly, and identifies service dependencies. Registered does not mean available on every deployment: service configuration, credentials, and implementation status still apply.

## Start with the connection contract [#start-with-the-connection-contract]

1. Use the instance base URL supplied by your deployment. The direct daemon defaults to `http://localhost:8080`; that is a listener default, not the hosted production address.
2. Read [authentication and authority](/docs/api/instance/authentication). Hosted instance requests use signed namespace capabilities; some operator and integration routes use separate credentials.
3. Check [availability and implementation limits](/docs/api/instance/coverage) for the capability you need.
4. Use the method and path shown in the reference. An SDK method name is not evidence that a corresponding daemon route exists.

```bash
curl "$AKASHA_INSTANCE_URL/v1/keyspaces" \
  -H "x-akasha-capability: $AKASHA_CAPABILITY"
```

The variables represent your configured instance URL and issued credential. Keep credentials in your application’s secret storage. This example does not mint a capability or change your instance.

## Memory and knowledge [#memory-and-knowledge]

| Capability                                     | Reference                                                   |
| ---------------------------------------------- | ----------------------------------------------------------- |
| Events, observations, and decisions            | [Episodic memory](/docs/api/instance/episodic-memory)       |
| Stored routines                                | [Procedural memory](/docs/api/instance/procedural-memory)   |
| Documents and resource metadata                | [Resource memory](/docs/api/instance/resource-memory)       |
| Sensitive values                               | [Vault](/docs/api/instance/vault)                           |
| Thoughts, sessions, and interactions           | [Cognitive memory](/docs/api/instance/cognitive-memory)     |
| Hybrid retrieval, emissions, and memory status | [Memory](/docs/api/instance/memory)                         |
| Active context and attention                   | [Working memory](/docs/api/instance/working-memory)         |
| Pattern recall                                 | [Associative memory](/docs/api/instance/associative-memory) |
| Relationships, graph queries, and history      | [Knowledge graph](/docs/api/instance/knowledge-graph)       |
| Knowledge lineage                              | [Lineage](/docs/api/instance/lineage)                       |
| Review and acceptance of incoming knowledge    | [Learning isolation](/docs/api/instance/learning-isolation) |
| Auditable removal                              | [Forgetting](/docs/api/instance/forgetting)                 |

## Computation and agents [#computation-and-agents]

| Capability                          | Reference                                                   |
| ----------------------------------- | ----------------------------------------------------------- |
| SQL and data sources                | [Analytics](/docs/api/instance/analytics)                   |
| Vector indexes                      | [Vectors](/docs/api/instance/vectors)                       |
| Retrieval and symbolic rules        | [Reasoning](/docs/api/instance/reasoning)                   |
| Cognitive cycles                    | [Cognitive cycle](/docs/api/instance/cognitive-cycle)       |
| Training tasks and continual state  | [Continual learning](/docs/api/instance/continual-learning) |
| Spiking networks and federation     | [Spiking networks](/docs/api/instance/spiking-networks)     |
| Unified inference jobs and backends | [Inference](/docs/api/instance/inference)                   |
| Embedding, generation, and training | [Machine learning](/docs/api/instance/machine-learning)     |
| Model downloads and lifecycle       | [Model management](/docs/api/instance/model-management)     |
| Text chunking                       | [Text chunking](/docs/api/instance/text-chunking)           |
| MCP tool calls over HTTP            | [MCP](/docs/api/instance/mcp)                               |
| Cambium projections and tool advice | [Cambium](/docs/api/instance/cambium)                       |

## Storage and operation [#storage-and-operation]

| Capability                                      | Reference                                                               |
| ----------------------------------------------- | ----------------------------------------------------------------------- |
| Keyspaces, records, and primitive import/export | [Key-value storage](/docs/api/instance/key-value)                       |
| Transaction lifecycle                           | [Transactions](/docs/api/instance/transactions)                         |
| Dataspaces and replication links                | [Namespaces and replication](/docs/api/instance/namespaces-replication) |
| Attached storage                                | [Storage volumes](/docs/api/instance/storage-volumes)                   |
| Backups, compaction, and indexing               | [Maintenance](/docs/api/instance/maintenance)                           |
| Health, metrics, and instance information       | [Operations](/docs/api/instance/operations)                             |
| Operator-only service controls                  | [Administration](/docs/api/instance/administration)                     |

## Other transports and reference material [#other-transports-and-reference-material]

* [gRPC, Arrow Flight, and MCP transport boundaries](/docs/api/instance/protocols)
* [Errors and request limits](/docs/api/instance/errors)
* [Exact data types](/docs/api/instance/schemas)
* [Coverage and known gaps](/docs/api/instance/coverage)

The maintainable source artifacts live under `minds-docs/reference/instance/`: `openapi.json`, `routes.json`, `coverage.json`, `handler-sources.json`, and `schema-sources.json`. Regenerate them with `python3 minds-docs/scripts/generate-instance-reference.py`; use `--check` to detect source drift. Dynamic response objects remain unconstrained in OpenAPI when the source does not establish a fixed schema.