EELML INTEGRATION DOCUMENTATION
These documents describe the public integration boundaries that exist today. Authentication is explicit, tenant identity is server-derived, and managed model routing never exposes provider credentials to the client.
Updated October 2, 2026
01 · CONTROL PLANE
Use the EELML control-plane API for account, catalog, order, subscription, and approved application workflows. Public catalog reads need no token; user data and write operations require an EELML bearer token.
External API →02 · MANAGED INFERENCE
Choose local inference for supported .eelml packages or the managed Cloud Model Gateway for online reasoning. Harness keeps one task flow while the local Runtime Service and server-side policy router remain separate execution paths.
Inference API →03 · BUSINESS TOOLS
Finance ERP exposes its authorized business capabilities through standard MCP JSON-RPC. The recommended public path uses the signed-in ERP user token, allowing the server to restore the tenant, user, store, role, and permission boundary instead of trusting client-supplied identity headers.
AI SaaS MCP →