Prodigi IntelligenceEnterprise integration

From request to action

Simulation

Follow a request through Prodigi Intelligence — model, tools, APIs and retrieval — to your business systems and back as an answer or an action.

Choose a scenario

Scenario
Customer

Where is my order?

Flow

  1. User

    A person or an application makes a request.

  2. Prodigi Intelligence

    Orchestration: identity, permissions, prompts, policies and logging.

  3. AI model

    Understands the request and decides which tools it needs.

    • Claude
    • OpenAI
    • Gemini
    • Azure AI
    • Open models
  4. Tools · APIs · RAG

    Permissioned operations and retrieval over approved knowledge.

    • APIs
    • RAG
    • Functions
    • Policies
  5. Business systems

    CRM, ERP, databases, e-commerce, documents and internal tools.

    • CRM
    • ERP
    • Databases
    • E-commerce
    • Documents
    • Internal tools
  6. Result · Action

    An answer with sources, or an action — approved where required.

Trace

Simulated

Press Play, or use Next, to follow the request layer by layer. Each step shows what happens and a sample of the data passed along.

Learn

About this experience

This is a simulation: scenario data is local to the page and no request is sent anywhere. The layers are the ones Prodigi designs and builds for production integrations.

How does AI integration work?

AI integration works in layers. A user or application sends a request to an orchestration layer; the orchestration layer calls an AI model with instructions and permitted tools; the model uses those tools — APIs, database queries or retrieval over documents (RAG) — to fetch business context; the result is checked against rules and returned as an answer or passed on as an action. Credentials, permissions and logging stay on the server side.

Are the AI demos on this site connected to a real AI model?

Not by default. The chat, agent, search, voice and integration experiences run in demo mode on a local engine that uses this website’s own content and scripted steps, so they work without a backend and never touch real systems. The interfaces are built on the same service contracts a production AI backend would implement.