Cookbook - Engini Developer Docs

Every recipe is a self-contained script - the runnable originals live in engini-sdk/python/examples (PEP 723 scripts: uv run <file> installs their deps automatically).

REST API walkthrough

Zero to executed tool with nothing but cURL - discovery, an OAuth connection, execution.

CLI walkthrough

The same journey from the terminal - as a human, and as an agent using resumable gates.

monday.com assistant

The canonical agent loop: Claude answers questions about your boards through Engini tools. Start here.

Gmail agent with attachments

The same loop plus file uploads - the model picks attachments by reference key, your code controls the bytes.

Priority ERP assistant

The agent pattern pointed at an ERP - orders, invoices, customers, inventory.

Scripted automation (no LLM)

The SDK as a plain typed API client - the shape of a cron job or data sync.

The two integration paths

High-level, with Toolset - bind app → connection once, then two calls per turn:

ts = client.toolset(connections={"salesforce": conn_id})
tools   = ts.tools()                  # provider-shaped tool schemas
results = ts.handle_tool_calls(reply) # resolves connection + runs each call

Low-level, without Toolset - drive the pieces yourself (fetch schemas, wrap, parse calls, execute, format results) - see the pattern in LLM providers. Or skip the LLM entirely and just call client.tools.execute(...) (scripted automation).

⌘I