Log in once.Corin maps the rest.
The Tool Map: every SAP and Infor action your access allows — nothing more.
Hover or focus a system to trace its path.
TOOL MAP — 3,143 M3 API services
Every service comes from a Corin-verified tenant ION API metadata export (2026-07-27); your login scopes the subset. Scope tags shown are illustrative — your tenant's map comes from your own login.
The MCP server your login builds.
Corin maps every action your access allows — and nothing more.
Three steps, no integration project.
01Sign in once
Your existing SAP or Infor login, standard OAuth. No new accounts, no copied credentials.
02Corin maps your tools
It enumerates what that identity can reach — tool by tool, scope by scope — and nothing more.
03Agents work, you approve
Work starts flowing at the rung you chose: Watch, Draft, Approve, Autopilot.
Corin sees only what your login sees. It inherits your existing SAP and Infor permissions — and never grants new ones.
Your assistants call Corin, too.
Streamable HTTP with OAuth: ask for a dry run from Claude, check a case from ChatGPT, approve from Copilot Studio — same tools, same gates, same ledger.
01corin.simulate
Run the dry run against live context — the outcomes on the table before anything posts.
02corin.quote
Draft an ERP-priced quote from an RFQ, margin and terms attached.
03corin.decide
Collapse a dry run to a recommendation — reasoning and runners-up included.
04corin.approve
Confirm a staged decision. The ledger row carries your identity.
05corin.status
Where this order, quote, or invoice stands right now.
06corin.search_workgraph
Query the work graph — one live view of every job: customers, orders, invoices, cases.
Snippets show the shape. Your endpoint is issued when you connect — nothing here is public-internet reachable.
Corin speaks MCP in both directions — a governed client of 100+ servers, and an MCP server your own copilots can call, behind the same policy gates.
Corin interoperates with other agents — including SAP Joule agents — via the open Agent2Agent (A2A) protocol.
Powered by the Model Context Protocol — the same open standard behind Claude and ChatGPT connectors.
The MCP gateway you don't have to buy.
The controls enterprises buy as a separate MCP gateway are built into Corin itself.
- Allowlisted catalog
- Corin calls only servers in its certified catalog. No dynamic discovery of unknown servers — a tool that isn't listed doesn't exist.
- Identity binding
- Every call runs as a known identity with your existing permissions — never a shared service account with more rights than you.
- Parameter validation
- Arguments are checked against the tool's contract before the call leaves — malformed or out-of-policy calls stop at the gate.
- Approvals + the ledger
- Writes wait at your gate, and every call lands in the ledger — a record of every decision: what changed, who approved it, when.
Every MCP tool is untrusted until it is certified into the catalog.
The platforms are building for agents. Corin plugs in.
SAP MCP Gateway
SAP Integration Suite exposes released APIs as MCP tools — Corin consumes them through the governed gateway, not screen-scrapes.
Infor's agent runtime
The Agentic Orchestrator — Infor's MCP-based agent runtime (announced April 2026) — explicitly welcomes third-party agents. Corin connects as one.
The curated ION toolset
The verified tenant catalog — 45,272 operations across 23 suites — is curated into governed agent tools with scopes, rate limits, and audit.
Events
SAP Event Mesh, Infor Data Fabric, bank files, and EDI documents keep the work graph current.
Operation counts from a Corin-verified tenant ION API metadata export (2026-07-27).