Give an agent your pipeline. Safely.
ilion speaks MCP. Point Claude, Cursor, n8n or something you wrote yourself at one endpoint and it can read your revenue data and propose work into it — without being able to email a customer, move money, or change what you charge.
curl https://ilionos.com/api/mcp \
-H "Authorization: Bearer ilion_live_…"
# → the tools this key can reach, and which of them need a humanEvery tool has a ceiling.
Risk is a property of the tool, decided on our side. An integration cannot argue its way past it, and neither can a prompt hidden in one of your records.
| Read | list_records · get_record · query_analytics · get_payment_history | Runs immediately. |
| Low | log_activity · update_record | Runs immediately. Internal and reversible. |
| Consequential | create_quote · draft_email · send_invoice · accept_quote | Becomes a pending action. A human approves it in ilion before anything happens. |
| Never | pricing config · bulk imports · suppression lists · deletes | Not reachable over the API at all. Not even listed. |
No trust, by design
An API key has no approval history, so it never earns autonomy. That is the point: the ceiling is fixed, not something an integration can grow into.
Proposals, not surprises
A consequential call lands in the same approval queue your own agents use, labelled as an external integration — never disguised as something ilion decided.
The whole motion, not just contacts
Quotes, contracts, invoices, subscriptions and renewals are first-class objects, so an agent can work a deal end to end instead of stopping at the CRM boundary.
REST, webhooks and Zapier.
MCP is the agent-native door. The same data is reachable the ordinary way when that suits you better.
REST API
Every object, paginated and org-scoped.
Webhooks
Signed deliveries with retries.
Zapier & n8n
No code required.
API access is included from the Growth plan up.