ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

How ibl.ai Integrates with Open edX

Jeremy WeaverMay 8, 2025
Premium

ibl.ai installs in Open edX as an LTI 1.3 Advantage tool, so a single OIDC‑signed launch JWT logs users straight into the AI agent with their exact course and role while Deep Linking, Names & Roles, and Assignments & Grades services handle roster sync and real‑time score return to the Open edX gradebook. Instructors just drop an LTI component (XBlock) in Studio, choose ibl.ai’s launch URLs, and the platform auto‑embeds AI activities as native units—all secured by the Sumac‑release LTI 1.3 implementation.

ibl.ai (an AI-driven tutor/agent platform) connects to Open edX using the LTI 1.3 Advantage standard. Open edX (Sumac release and later) is fully LTI Advantage certified, meaning it supports the core LTI 1.3 launch flow and the three Advantage services (Deep Linking, Assignments/Grades, Names & Roles). In practice, an instructor adds a LTI component (an XBlock) in Studio and configures it with ibl.ai’s tool endpoints. Students then click the ibl.ai link to launch the tool with single-sign-on, and data flows (user identity, context, scores, roster, etc.) are exchanged securely. The result is a seamless experience: ibl.ai content appears as part of the Open edX course, students never have to log in again, and instructor-configured content and scores are synced automatically.

  • Configuration: In Studio’s Course Outline, the instructor adds an LTI Component (XBlock) and sets “LTI Version = 1.3”. They enter ibl.ai’s Tool Launch URL (redirect URL) and OIDC Login URL (login endpoint), as provided by ibl.ai. They also paste ibl.ai’s public key into the settings; this lets Open edX verify the signature on incoming LTI messages. (Studio then displays generated values – Client ID, Deployment ID, Keyset URL, etc. – which are copied into ibl.ai’s tool configuration.)

  • OIDC Launch Flow: When a user clicks the ibl.ai link, Open edX initiates the LTI 1.3 launch using an OpenID Connect handshake. The platform (LMS) sends an authentication request to ibl.ai’s OIDC login URL. ibl.ai validates the request and responds with a signed ID Token (JWT) containing the launch parameters. This JWT includes claims for the user’s identity, role (Instructor or Learner), course context, resource link ID, and any custom parameters. Open edX verifies the JWT signature with the public key, establishes the user’s identity, and opens the ibl.ai interface.

  • Security and Data: By using OIDC and signed JWTs, the launch is secure. The JWT payload transports user and course information without extra login prompts. Because ibl.ai trusts the JWT signature, it knows exactly which student or instructor has launched it, and under which course and unit. (Open edX’s LTI component explicitly calls out that the Tool Public Key is required to “check if the messages and launch requests received have the signature from the tool”.)


Deep Linking (Content Selection)

  • Enable Deep Linking: In the LTI component settings, the instructor toggles Deep Linking to True and enters ibl.ai’s Deep Link Launch URL (often the same as the normal launch URL).

  • Configure in Studio: The LTI block in Studio now shows a “Configure tool link” button. Clicking this sends the instructor to ibl.ai’s deep-link interface.

  • Select Content: Within ibl.ai, the instructor picks or creates the desired content (for example, an AI-generated quiz, study guide, or interactive tutorial). Once they finish, ibl.ai returns a configured resource link to Open edX.

  • Result in Course: Studio inserts the selected ibl.ai content as an LTI resource in the course. Students will see this new activity in the unit. When launched, it goes directly into that specific ibl.ai content (instead of a blank tool), thanks to the deep-link configuration.


Names & Roles Provisioning (Roster Sync)

  • Enable NRPS: In the same LTI component settings, enable LTI Names and Roles Provisioning (NRPS).

  • Roster Retrieval: With NRPS on, ibl.ai can call the LTI Names and Role Provisioning service endpoint. This returns the course roster of enrolled users. For each user, ibl.ai gets limited profile details (full name, email, username) and their role and enrollment status.

  • Use Cases: Having the roster allows ibl.ai to personalize interactions (e.g. addressing students by name) and to manage permissions (e.g. know which learners should have access to the course’s ibl.ai). It also lets ibl.ai verify which students are active in the course. (Note: By default Open edX only returns NRPS data for courses with up to 1000 users for performance; an administrator can raise this limit if needed.)


Assignment and Grade Services (Score Return)

  • Enable AGS: In the LTI component, set the LTI Assignment and Grades Service mode (e.g. Programmatic for multiple grades).

  • Passing Grades: When students complete tasks or quizzes in ibl.ai, the tool can use the LTI Assignments & Grades (AGS) API to post scores back to Open edX. For example, ibl.ai could submit a numerical score or percentage via LTI’s grade return calls.

  • Gradebook Integration: Returned scores automatically populate the Open edX gradebook under the LTI component’s entry. Instructors see the ibl.ai results alongside other assignments.

  • Standards-Compliant: Because Open edX is LTI-Advantage certified, this grade passback works reliably. (Alternatively, a deep custom integration could use Open edX’s own grading APIs, but LTI AGS is the standard method.)


Embedding ibl.ai in Courses

  • LTI Consumer XBlock: The integration uses Open edX’s built-in LTI Consumer XBlock. This XBlock “implements the consumer side of the LTI specification enabling integration of third-party LTI tools”.

  • Course Authoring: Instructors simply add the LTI XBlock to a unit (just like adding a problem or video). Once configured, it appears in the course outline. Students click it to launch ibl.ai.

  • Studio View: Instructors see the LTI block’s settings and can edit or reconfigure it. Deep-linked content appears as links (with the title from ibl.ai). The Studio interface lets them manage all ibl.ai LTI blocks without coding.

  • No Extra Plugins Needed: No special client-side app is required; the LTI XBlock handles everything. (If desired, an advanced team could build a custom ibl.ai XBlock, but it is not needed since the standard LTI workflow suffices.)


Streamlined User Experience

  • Single Sign-On: Students and instructors experience one-click access. Clicking a ibl.ai activity logs them in automatically via the LTI handshake (no separate username/password).

  • Role-Specific UI: ibl.ai knows the user’s role from the launch data. Instructors get access to course management and content-creation features, while students see the personalized agent/tutor interface. The tool can even tailor questions or hints based on the user’s identity and course progress.

  • Instructor Workflow: Instructors set up ibl.ai content through Studio (deep linking or parameters), then ibl.ai appears as part of the normal course flow. There is no need for manual roster exports or score entry, as those sync automatically.

  • Scores and Feedback: Any grades or feedback from ibl.ai flow back to the LMS gradebook in real time, so instructors can monitor student performance in one place. Students see their ibl.ai quiz scores right in Open edX as well, completing the feedback loop.

Want to know how your institution can become AI-driven by utilizing the ibl.ai platform on Open edX? Learn more at ibl.ai

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.

  • Model-agnostic

    Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

Related Articles

How ibl.ai Integrates with OpenAI: A Guide to Model Options and Deployment Flexibility

ibl.ai’s guide walks campuses through plugging any GPT model—using a self-managed key or private Azure cluster—while keeping data FERPA-safe. Its middleware routes prompts, logs and meters token spend, and unlocks embeddings, Whisper, and DALL·E upgrades without changing course code.

Jeremy WeaverMay 6, 2025

NVIDIA's Open Routing Layer: Why the Model Stopped Being the Moat

NVIDIA shipped an efficient open model and an open routing library on the same day. Together they commoditize the model layer and move the durable advantage to the routing layer — which is the one piece you should refuse to rent. What routing saves, what open weights do not buy you, and the three layers worth owning.

ibl.ai EngineeringAugust 12, 2026

Nemotron 3.5 Lightning and NeMo Switchyard: Why Agents Need an Open Routing Layer

NVIDIA released Nemotron 3.5 Lightning (30B total, 3B active) and NeMo Switchyard, an open routing library. Together they make the model the cheapest part of an agent deployment — and move the value to the routing layer. Here is what enterprises should own, and the cost math for routing by task.

ibl.ai EngineeringAugust 11, 2026

On-Premise Foundation Models: Which Vendors Allow It

Which foundation model vendors actually permit on-premise deployment, sorted into open-weight, contracted-private, and API-only tiers — and why picking a model vendor is not the same decision as picking the platform that runs it.

Miguel AmigotAugust 10, 2026

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work — so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope · fixed timeline

A time-boxed proof of value on your real data — not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time · not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data · run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Six figures

perpetual license · you own the stack

We transfer the full source code. You own and self-host the entire platform — outright.

Best for: Government, defense, and enterprises that require perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable · zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM — Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY