An AI agent connected to your ERP or any system with an API.
If your system has an API, your agent can use it. We start from its OpenAPI docs, a Postman collection or the cURL calls that already work, and define with you which operations it can use and within what limits.
Connector · Customer portal APIExampleHas my order 4471 shipped yet?
GET /customers?phone=… → 200 · 0.3 s
GET /orders/4471?customer_id=1182 → 200 · 0.8 s
Yes, it left today on the North route and arrives tomorrow between 10 am and 2 pm.
Your system, with an agent that knows how to use it.
- Keep your ERP
The agent works on your system as it is. No data migration, nothing to replace.
- Defined operations, not improvised ones
The agent never builds calls on its own: it only uses the operations we configure with you.
- Only the data it needs
We trim API responses down to the useful fields. Sensitive data never reaches the agent.
From your documentation to operations the agent can use.
- 01You bring the documentation
OpenAPI or Swagger, a Postman collection with its environments, cURL commands or endpoint by endpoint.
- 02We choose the operations
For example, look up an order or search for a product. Every other call stays out of the agent's reach.
- 03We set limits
Timeouts, retries, which fields the agent fills in and which the system sets, such as the customer's phone number.
- 04We test in your staging environment
Before production, with real cases. Credentials are stored encrypted and the agent never sees them.
- Use only the operations we configure
- Look up data for the customer who is writing
- Write with confirmation and without duplicate records
- Build new calls on its own
- See your access credentials
- Receive fields marked as sensitive
Built so your system stays under your control.
- Your API's authentication
OAuth 2.0 client credentials, a header key or username and password. Stored encrypted.
- Separate environments
Drafts are tested against your staging environment, and only published versions use production.
- Writes without duplicates
Operations that create records use an idempotency key: if a request arrives twice, only one record is created.
What do I need to connect my system?
An accessible REST API and some documentation: an OpenAPI spec, a Postman collection or cURL calls that already work.
Does it work with a custom-built ERP?
Yes, if it exposes an API. If it only has a database, we review it during discovery.
Can the agent change data?
Only through the write operations you enable, and with the customer's confirmation where it applies.
Who configures the operations?
Your Lummy implementer, together with the person on your team who knows the system.
BOOK A DISCOVERY CALLThat backlog of work
already has a next step.
Tell us which system you use and whether its API is documented.
We start with what your business needs solved.