Build with Minds
Connect an application, script, or agent to a dedicated Mind with an explicit API contract.
Give your application a memory it can return to. A useful first integration stores one piece of context, retrieves it in a later request, and keeps the source information with the result.
Pick your path
| You want to… | Start here |
|---|---|
| Make a first scoped memory request | Connect over HTTP |
| Use JavaScript or TypeScript | TypeScript |
| Add memory to a Python workflow | Python |
| Work from a Go service | Go |
| Build an asynchronous Rust integration | Rust |
| Inspect or script engine operations from a terminal | cogs CLI |
| Use the terminal interfaces | Terminal interfaces |
| Connect an agent host | Agent integrations |
| Manage organizations, instances, and billing context | Platform API |
Know which credential you have
The dedicated engine can require a signed capability in x-akasha-capability. A legacy deployment can also require a Bearer JWT. Management API keys and signed-in dashboard cookies are separate credentials. Use the connection details issued for your particular Mind.
The SDKs currently expose different methods and do not all send the capability header by default. Start with the exact HTTP request below, then use the compatibility guide to choose supported client methods. A package's presence in this repository is not evidence that its published release or every endpoint has been verified.
Complete references
The language references preserve exported signatures, request/result types, and source locations. They cover 1,173 declarations in this source snapshot:
Examples use environment variables for private connection details. Replace the example content with a non-sensitive test record before adding a real application workflow.