HTTP
Local signed requests.
Applications bind identity and the exact action through a certificate envelope before calling protected memory operations.
Bring the agent. Keep one memory authority.
AIMOS is independent of the model subscription. Agents and applications connect through signed local HTTP or MCP surfaces while canonical memory stays under one set of owners.
Two public surfaces
Different transports.
The same guarantees.
Neither surface receives direct database access or a privileged path around canonical save and recall.
MCP
Agent-native tool access.
Compatible agent clients use the same memory and security owners through an MCP integration surface.
Provider independence
Identity is not
a model subscription.
Provider and model choice may be carried as signed policy, but the enrolled agent identity remains independent of the model used for a particular task.
Replaceable intelligence.
The client may change without becoming the permanent owner of remembered history.
Stable enrolled identity.
Authority belongs to a verified principal, not to a brand name sent in a request field.
Canonical local custody.
Save, recall, and evidence remain governed by AIMOS regardless of transport.
Connection guide
Sign the request.
Respect the boundary.
The repository contains the canonical agent and tool connection guide, certificate envelope contract, deployment workflow, and release-qualified requirements.
Local by default