Corin works your Infor queue.
Corin's surface is a tenant ION API catalog we verified ourselves: 45,272 operations across 23 suites and 27 products.
Hover or focus a system to trace its path.
44,216 M3 operations in the verified tenant catalog — the map is drawn from your access, never from a datasheet. Scope tags shown are illustrative; your tenant's map comes from your own login.
Infor AI agents, mapped from your login.
Log in once. Corin maps every action your access allows — and nothing more.
MI programs. IDOs. BODs.
Fluency is knowing which surface carries which write. Corin speaks all three — and files every receipt in the ledger — a record of every decision: what changed, who approved it, when.
- MI programs — Infor M3
- The M3 write path behind the ION API gateway: OIS100MI carries customer orders, CRS610MI the customer master. Corin calls them with your login's roles — never a super-user.
- IDOs — CloudSuite Industrial (SyteLine)
- CSI exposes its objects as IDOs on the Mongoose framework — the same collections your forms load. Corin reads and writes through them, schema-checked before any commit.
- BODs — ION Workflow
- Business Object Documents ride ION: the event stream that tells Corin an order changed, without polling. Approvals can stay inside your existing ION Workflow.
Every suite, counted.
The full tenant catalog, grouped by domain. Open a domain to see its suites — every count is summed from the export.
Rows in the tenant export (all_operations.json): REST + SOAP + MCP operations, merged and deduped. API suites listed in the tenant ION API metadata export (apisuites.json).
The operational heart: items, prices, orders, invoices, credit. Every sales and finance decision ultimately lands here.
- Infor M344,216
The gateway itself — ION routing and services, the OS portal, search, and the platform services every call passes through.
- Infor ION214
- IFS Service100
- Local.ly Services Platform65
- Infor Search14
- Infor OS Portal6
- Infor Session Service1
Embedded analytics: the numbers decisions get measured by.
- BIRST171
Harmonized storage, compute, and retention — the context layer and its guardrails.
- Infor Data Fabric106
- Data Compliance35
The central repository: POs, invoices, certs, and the paperwork decisions attach to.
- Infor Document Management82
Factory Track execution plus the Mongoose framework that custom M3 screens are built on.
- Infor FactoryTrack79
- Infor Mongoose79
- OutSystems7
Alerts and push channels that carry events to people and portals.
- Infor Notification Service19
- ION Notification Center8
- Infor Ming.le™ Push Notifications8
- Web Push Notification Listener5
Audit, multifactor authentication, health reporting, and process intelligence — the oversight surface.
- Auditing and Monitoring23
- Infor Multifactor Authentication20
- Infor Health Service10
- Infor Process Intelligence4
Every count summed from the tenant export at build time — nothing hand-typed.
Numbers you can re-derive.
The tenant-wide totals are summed in the explorer above. These three derive from the M3 core — the surface where decisions land.
Built for Infor and SAP. Not connected to them — fluent in them.
Fluent means the tenant catalog above, the MI programs by name, and a dry run before every write — not a logo on a slide.
The connection surface, as spec.
Every system Corin touches: the interface it connects through, the surface that carries the work, and what stays untouched in your landscape.
| System | Interface | Surface | Preserved |
|---|---|---|---|
| Infor M3 | ION API — REST + SOAP | Verified tenant catalog — 44,216 M3 operations across 3,143 services | Custom fields and Mongoose screens untouched |
| Infor CSI / SyteLine | ION / IDO (Mongoose) | IDO methods exposed through the ION API gateway | Approval rules and configurations stay in CSI |
| SAP S/4HANA Cloud | Released public APIs — OData V4/V2, SOAP | Sales Order A2X · Simulate A2X · Supplier Invoice · Journal Entry Post · Event Mesh · MCP Gateway | Clean core — released APIs and events only, no modifications |
| Microsoft 365 | Microsoft Graph + Entra ID | Shared mailboxes · Outlook drafts · Teams approvals | Mail stays in your tenant — nothing is auto-sent |
| EDI network | X12 850 / 855 / 856 / 810 / 820 | Orders · acknowledgements · ship notices · invoices · remittance | One network partner — no per-partner mapping projects |
| Bank & lockbox | BAI2 · camt.053 | Statements in · remittance matched · NACHA staged | Payments released only with human confirmation |
| D&B | Direct+ | Credit reports · proposed limits · monitoring | Credit policy stays yours — bureau data informs, procedures decide |
Infor now describes this category.
Infor's own launches — Velocity Suite, the Agentic Orchestrator, a growing agent library — describe an ERP that acts inside business rules, with people approving what matters. That is the loop Corin runs today, across Infor and SAP alike, as an independent layer. Describing the same category is not an endorsement, and none is implied.
How these numbers were produced.
01Exported from a real tenant
On 27 Jul 2026 the ION API metadata of a production Infor tenant was exported: the API suite list, the product list, and the full operation catalog. Tenant identifiers are scrubbed before the data enters this repository.
02Merged and deduped
REST, SOAP, and MCP operations were merged into one catalog and deduped. Suite and product counts come straight from the export's own lists; operation counts are the surviving rows.
03Computed at build, never typed
Every number on this page is computed from that export when the site builds. If the export is refreshed, the generator re-runs and the numbers change — nobody edits them by hand.
These counts describe one tenant Corin verified. They are not published by, endorsed by, or attributable to Infor, and they imply no partnership or affiliation. Infor and M3 are trademarks of Infor.