Skip to content
Current State: ALPHA - Use at your own risk / Work in Progress
  • architecture
  • connectivity overview

Connectivity Overview

Eryxon MES provides a comprehensive set of connectivity options for integrating with external systems, industrial automation, and AI agents.

Integration Architecture

Section titled “Integration Architecture”

Eryxon MES uses a Unified Event Dispatcher to coordinate communication across different protocols.

Authentication

Section titled “Authentication”

API Key Authentication

Section titled “API Key Authentication”

All external API calls currently require a Bearer token in the Authorization header:

Authorization: Bearer ery_live_xxxxxxxxxxxxxxxxxxxx
  • ery_live_: Production keys.
  • ery_test_: Sandbox/testing keys.
  • Keys are hashed with SHA-256 and validated in edge functions with constant-time comparison.

For the detailed API contract, see REST API Reference.

MCP Authentication

Section titled “MCP Authentication”

Model Context Protocol keys are configured separately in the Admin panel to allow AI agents like Claude to securely interact with your shop floor data. See the MCP Server Setup Guide for complete deployment instructions.

Real-time Subscriptions (Inbound)

Section titled “Real-time Subscriptions (Inbound)”

Eryxon uses Supabase Realtime (WebSockets) to push updates to the frontend and connected clients instantly.

Hooks for Developers

Section titled “Hooks for Developers”

The current app standardizes realtime subscription behavior around shared subscription utilities and tenant-aware hooks used by operator, issue, notification, and dashboard flows.

The important behavior is:

  • subscriptions are tenant-scoped
  • cleanup is explicit on unmount
  • debounced realtime handlers are canceled during teardown

AI Integration (MCP)

Section titled “AI Integration (MCP)”

The Model Context Protocol (MCP) enables AI agents to interact with Eryxon MES programmatically through 55 specialized tools across 9 modules.

AI agents can:

  • Fetch and update jobs/parts
  • Start and complete operations
  • Report or resolve quality issues
  • Monitor dashboard statistics
  • Perform batch operations
  • Analyze scrap trends and quality metrics

Learn more:

Event System

Section titled “Event System”

All major actions (job created, operation started, issue reported) trigger events in our internal dispatcher, which then forwards the data to configured Webhooks and MQTT brokers simultaneously.

Data Portability

Section titled “Data Portability”
  • Export: Admins can export all tenant data in JSON or CSV (ZIP) formats for backup or migration.
  • Import: Supports bulk CSV imports for jobs, parts, cells, and resources.

Error Codes & Rate Limiting

Section titled “Error Codes & Rate Limiting”

Common Error Codes

Section titled “Common Error Codes”
  • 401 Unauthorized: Invalid API key.
  • 402 Payment Required: Plan limit reached.
  • 429 Too Many Requests: Rate limit exceeded.

Rate Limits

Section titled “Rate Limits”

Limits are enforced per tenant plan in the edge-function auth layer. In the current implementation these are conservative daily limits rather than RPM-based examples:

  • Free: 100 requests/day
  • Pro: 1,000 requests/day
  • Premium: 10,000 requests/day
  • Enterprise: unlimited
Section titled “Related Docs”