0xroboros
Integration Architecture

Where 0xos sits relative to the NeuralSeek stack

Prepared for NeuralSeek· 2026-08-20· 0xroboros LLC· Confidential
NeuralSeek Client or calling service session token is optional state, not authentication NeuralSeek API and UI how a caller authenticates in is not documented mAIstro workflow engine NTL templates, parallel execution, scheduler agents run unattended on a timer Agent Registry selectAgent returns "send_email" maistro executes that string no signature, no key, no attestation membership in a local list is the trust model Integration nodes REST · SQL · S3 · SharePoint · GitHub SMTP · search · LLM · knowledge bases destination is a typed string credential proves us to them, nothing proves them to us The two seams Seam A · agent to agent Is this the agent the registry meant, and can anyone else prove it afterward? Seam B · system to endpoint Is this the endpoint the operator configured, or one that answers to the same name? 0xroboros 0xos verification layer company.endpoint.api.0xos identity issued at the anchor, verified by a light client the counterparty runs, with nothing trusted in the path Handshake, root held by key
What the layer supplies

A durable identity for an endpoint or an agent, issued at a canonical anchor and signed against a root that is owned outright rather than leased. Verification is performed by the counterparty's own light client against chain state. No certificate authority, no registrar, and no 0xroboros gateway sits in the trust path.

Nothing inside NeuralSeek changes shape. The identity attaches to positions the workflow already addresses.

What it does not supply

It is not an authorization engine. It establishes which party is acting. It does not decide what that party is permitted to do, and it does not replace the registry, the guardrails, or the governance surface.

It is also not a payment rail and not a metering system. Those are separate questions and are stated here so that the boundary is drawn before the pilot rather than during it.

Scope note

A deployment running with complete network isolation, as the Flex plan permits, removes most of Seam B by construction. In that configuration the value of this layer is small and it should not be sold there.

Seam A persists in every configuration, because it is internal to the workflow engine rather than a property of the network boundary.