MCP connections
Future tool connections should declare capabilities, request narrowly scoped permissions and expose clear approval points.
04 / DEVELOPERS
Connect. Build. Extend.
A planned developer ecosystem for well-defined capabilities and explicit permissions. Public documentation will describe safe interfaces—not reveal AURA’s proprietary intelligence internals.
MILESTONE 03–04 · INTEGRATION DIRECTION
Open interfaces. Clear boundaries.
MCP and API integration are roadmap directions, not currently available public endpoints or SDKs.
Versioned APIs
Public contracts and authentication requirements will be documented only after interfaces exist and pass review.
Safe disclosure
Documentation will explain supported interfaces without publishing proprietary algorithms, secrets or private implementation details.
SDK roadmap
Versioned SDKs and typed integration interfaces planned for future releases.
Capability registry
Discover what approved tools and agents can do, without broad file-system access.
Auditable handoffs
Trace work state, decisions, evidence pointers and permitted transfers.
Sandboxed execution
Constrain untrusted extensions by permissions and process boundaries.
Developer documentation
Practical examples and contract tests once APIs are implemented.
Testing first
Compatibility, accessibility, security and failure-mode checks before production exposure.