IAToolkit
Integration surface

The API for integrating corporate systems with IAToolkit.

If MCP is the access surface for AI clients, the API is the integration surface for your systems, portals, and workflows. Trigger agents, pass structured context, and retrieve results from your own flows.

  • Use one public entrypoint for execution, polling, and review.
  • Keep business identity, auditability, and per-user traceability.
  • Connect portals, back-office systems, CRMs, ERPs, and internal automations.
See platform Discuss your integration
Public contract

The integration surface for real systems.

One contract for execution, status polling, and result review from corporate systems.

Endpoints 
POST /<company>/api/invocations
GET  /<company>/api/invocations/<id>
PUT  /<company>/api/invocations/<id>/review

Use `POST` to start execution, `GET` for polling, and `PUT` for result review when your flow requires it.

Payload 
{
  "agent_name": "sales_2025",
  "user_identifier": "analyst@acme.com",
  "delivery_mode": "async",
  "client_data": { ... },
  "files": [ ... ]
}

The API accepts `agent_name`, `user_identifier`, `client_data`, attachments, and execution options in the same request.

Agent call example 
curl -X POST "https://app.iatoolkit.com/acme/api/invocations" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <token>" \
  -d '{
    "agent_name": "commercial_analyst",
    "user_identifier": "maria@acme.com",
    "delivery_mode": "async",
    "client_data": {
      "company_id": "acme_iberia",
      "account_id": "acc_2048",
      "workflow": "daily_commercial_pipeline",
      "requested_report": "opportunity_summary",
      "filters": {
        "stage": ["proposal", "negotiation"],
        "owner_region": "spain"
      }
    }
  }'

Your system invokes an IAToolkit-managed agent and gets either an immediate result or an `invocation_id` to continue the flow.

Asynchronous operations

Run agents in the background and follow every execution from the GUI.

The API does more than trigger executions. It also enables queues, asynchronous processing, and operational monitoring for agents that work outside the interactive request.

Request queue

Systems send work to be executed

inv_10428 commercial_analyst · pending
inv_10429 collections_agent · running
inv_10430 document_classifier · queued
POST /api/invocations
Workers / Agents
Status + result
GUI monitoring

The GUI centralizes status, errors, and traceability

Monitoring
Running12
Queue34
Errors2
inv_10418 completed inv_10429 processing inv_10397 review required
The API queues and triggers

A corporate system can start heavier work without waiting for the final answer in the same transaction.

`invocation_id` as the operational thread

The identifier supports polling, callbacks, review, and traceability for each async execution.

The console gives visibility

Operations and support teams review status, errors, activity, and results from one unified surface.