First Resonance

First Resonance builds ION, a modern Factory Operating System (MES) for companies manufacturing complex hardware in aerospace, defense, robotics, medical devices, and clean energy. ION provides digital work instructions (Procedures and Runs), part and inventory traceability, mBOM/aBOM management, quality and compliance workflows, production scheduling (ION AutoPlan), and analytics. For developers, ION exposes a GraphQL API (api.buildwithion.com) secured with OAuth 2.0 client-credentials API keys, cursor-based (Relay) pagination, webhook subscriptions for realtime events, and a beta hosted MCP server so AI agents can operate the factory system. This profile was enriched from First Resonance's public developer manual.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

How we profile First Resonance

Each block below is one kind of artifact we hold for First Resonance. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 1

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

ION GraphQL API

The ION Factory OS GraphQL API. A single GraphQL endpoint for reading and writing manufacturing data in ION: Runs, Procedures, Parts, mBOM/aBOM, inventory, notifications, and we...

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

first-resonance-mcp.yml

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

First Resonance Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

First Resonance Authentication

oauth2 · 1 scheme

SECURITY

First Resonance Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

First Resonance Trust Center

SOC 2, FedRAMP, GDPR, FIPS 140

SECURITY

Resources

Every other property we hold for First Resonance — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

← All providers · Data indexed from github.com/api-evangelist/first-resonance · machine-readable index on apis.io