Python

The OpenAI Agents SDK lets you build production-grade multi-agent pipelines in Python with fewer than 100 lines of core logic. Install it with pip install openai-agents, define agents with instructions and tools, connect them via handoffs or an orchestrator, and run with asyncio. This tutorial walks through a complete three-agent pipeline from setup to deployment. What Is the OpenAI Agents SDK and Why Does It Matter in 2026? The OpenAI Agents SDK is an open-source Python framework that provides four production-grade primitives — Agents, Handoffs, Guardrails, and Tracing — for building multi-step AI workflows without the boilerplate overhead of earlier frameworks. Released in early 2026 and reaching version 0.13.4 in April with full MCP server support, the SDK emerged as a response to a clear market need: 57% of organizations now deploy agents for multi-stage workflows, yet most teams were still stitching together ad-hoc pipelines using raw LLM calls and custom orchestration code. The SDK abstracts that complexity into composable primitives where each Agent is a configuration object wrapping an LLM with instructions, tool access, and optional output schemas. Handoffs allow agents to delegate work to peers; Guardrails validate inputs and outputs; Tracing captures every decision step for debugging and observability. The SDK is also model-agnostic — it supports any provider conforming to the chat completions API format, and integrates with 100+ LLMs via LiteLLM. For teams evaluating agentic frameworks in 2026, the SDK’s minimal surface area and tight OpenAI integration make it the fastest path from prototype to production. ...

Gemini Flash-Lite Batch API cuts your LLM costs in half by processing requests asynchronously — submit a JSONL file, get results back within 24 hours, and pay $0.125/1M input tokens instead of $0.25. For teams running thousands of daily classification, translation, or summarization jobs, this single change can reduce monthly AI spend from hundreds of dollars to tens. What Is the Gemini Batch API and Why Does It Matter The Gemini Batch API is Google’s asynchronous processing mode that applies a 50% discount on all paid Gemini models for non-real-time workloads. Instead of sending individual HTTP requests and waiting for each response, you package hundreds or thousands of requests into a JSONL file, submit it as a batch job, and retrieve results once the job completes — typically well under 24 hours. Launched alongside the Gemini 3 family in early 2026, the Batch API targets the large class of AI tasks where latency is irrelevant: overnight content moderation queues, bulk data extraction pipelines, weekly report generation, and offline document analysis. The mechanism is simple: Google processes your batch during off-peak capacity windows, passes the savings directly to you, and guarantees completion within one day. For startups and enterprises alike, this transforms formerly expensive batch pipelines into genuinely affordable infrastructure. At $0.125/1M input tokens with Flash-Lite, you can process an entire Wikipedia-scale corpus for under $10 — a threshold that makes previously cost-prohibitive use cases like fine-tuning dataset generation or full-catalog product description rewrites financially viable. ...

Databricks managed MCP servers give AI agents secure, governed access to your Lakehouse data — Genie (NL-to-SQL), Vector Search, and UC Functions — with zero infrastructure overhead and Unity Catalog permissions enforced automatically on every call. What Are Databricks Managed MCP Servers? Databricks managed MCP servers are hosted, serverless endpoints that expose Lakehouse capabilities — structured data queries, vector search, and custom functions — to any MCP-compatible AI client through the Model Context Protocol standard. Unlike self-hosted MCP servers that require you to provision infrastructure, manage TLS, and handle scaling, Databricks-managed servers run entirely on Databricks serverless compute with on-behalf-of-user authentication baked in. Every tool call automatically inherits the caller’s Unity Catalog permissions, which means a data analyst connecting Claude Desktop to a Genie space can only query tables their UC role allows — no manual ACL syncing required. Databricks announced general availability of managed MCP servers in early 2026 alongside a broader “Week of Agents” initiative, and the platform has seen multi-agent workflow usage grow 327% in four months. The practical upshot for developers: you get enterprise-grade governance without writing a single line of server-side authentication code. ...

CAI (Cybersecurity AI) is an open-source framework from Alias Robotics that lets security engineers build, orchestrate, and deploy autonomous AI agents for offensive security tasks — from reconnaissance to exploitation, bug bounty automation to CTF solving. Install it with pip install cai-framework, point it at a target, and it handles the full pentest loop without step-by-step human direction. What Is CAI? The Open-Source Cybersecurity AI Framework Explained CAI is an open-source cybersecurity AI framework developed by Alias Robotics that provides a structured, modular foundation for building autonomous security agents capable of performing offensive tasks — reconnaissance, vulnerability scanning, exploitation, and privilege escalation — with minimal human intervention. Unlike running an LLM against a system prompt and hoping for the best, CAI wraps the AI loop in a production-ready architecture: structured agent definitions, reusable tool libraries, handoff protocols between agents, input/output guardrails, and human-in-the-loop (HITL) checkpoints. The framework supports over 300 AI models including OpenAI GPT-4o, Anthropic Claude, DeepSeek, and local deployments via Ollama — meaning you can run fully air-gapped without a cloud dependency. ...

Building an MCP server in Python takes under 30 minutes with FastMCP. Install fastmcp, decorate a Python function with @mcp.tool(), and any AI client — Claude, ChatGPT, Cursor, or Copilot — can call it immediately. This tutorial walks from a 9-line working server through PostgreSQL integration, Docker deployment, and security hardening. What Is MCP and Why It Matters in 2026? Model Context Protocol (MCP) is an open standard developed by Anthropic that lets AI clients connect to external tools and data sources using a single, universal interface. Think of it as USB-C for AI integrations: you build a server once, and every compliant AI client — Claude, ChatGPT, Gemini, Cursor, VS Code Copilot — can use it without any client-side code changes. MCP uses JSON-RPC 2.0 as its transport layer and defines three core primitives: tools (functions the AI can call), resources (data the AI can read), and prompts (reusable instruction templates). As of early 2026, MCP SDK downloads hit 97 million per month across Python and TypeScript, with over 12,000 active servers live on the internet (8,600 verified on PulseMCP). OpenAI adopted MCP in March 2025, Google DeepMind in April 2025, Microsoft in May 2025, and the Linux Foundation took over governance in December 2025 — making MCP the undisputed standard for AI tool connectivity. Early enterprise deployments report up to 70% AI operational cost reduction through on-demand data fetching versus context stuffing. The takeaway: MCP is no longer experimental infrastructure — it’s the production-grade integration layer for the AI era. ...

Building an AI agent from scratch in 2026 means choosing LangGraph or LangChain, wiring in custom tools, and adding persistent memory — all in under 200 lines of Python. This guide walks every step from environment setup through production deployment, with runnable code and cost estimates under $2.00 in API calls. Why 2026 Is the Year to Build AI Agents The AI agents market reached $7.63 billion in 2025 and is projected to hit $182.97 billion by 2033 at a 49.6% CAGR, according to Grand View Research. More practically: Gartner projects 40% of enterprise applications will integrate task-specific AI agents by end of 2026, up from less than 5% today. McKinsey’s 2025 State of AI Survey found 62% of organizations are at least experimenting with AI agents — 23% actively scaling. The gap between experimenters and producers is closing fast, and the Python tooling in 2026 is mature enough to bridge it. LangGraph crossed 126,000 GitHub stars in April 2026, making it the dominant orchestration framework. The window for competitive advantage belongs to developers who can ship working agents now, not teams still debating which framework to pick. ...

OpenAgents is an open-source framework for building persistent AI agent networks — systems where agents continue to exist, learn, and collaborate long after an initial task completes. Unlike LangGraph or CrewAI, which treat agents as stateless task runners, OpenAgents gives every agent a durable identity, a shared workspace with a persistent URL, and native support for both MCP (Model Context Protocol) and A2A (Agent-to-Agent) protocols from day one. What Is the OpenAgents Framework? OpenAgents is an open-source Python framework designed specifically for building persistent, interoperable AI agent networks. Launched in early 2026, it addresses the fundamental limitation of most agent frameworks: agents disappear once a task finishes, losing all learned context. OpenAgents agents maintain a durable workspace accessible at a stable URL (e.g., workspace.openagents.org/abc123), enabling teams to bookmark a network and return to an evolved, context-rich system days or weeks later. The framework ships with three core components — Workspace, Launcher, and Network SDK — and natively implements both the MCP and A2A protocols, which means agents built with different underlying frameworks can collaborate without custom glue code. In 2026, as 85% of developers regularly use AI tooling, the demand for long-running, team-aware agent infrastructure has grown sharply, and OpenAgents is purpose-built to fill that gap. The key distinction from alternatives is its architectural commitment: persistence and interoperability are first-class features, not afterthoughts bolted on via plugins. ...

Pydantic AI is a Python agent framework built by the Pydantic team that brings type-safe, validated LLM interactions to production. Install it with pip install pydantic-ai, define your agent with a Pydantic BaseModel as the result type, and the framework automatically validates LLM output — retrying if validation fails — without any manual JSON parsing or schema wrestling. What Is Pydantic AI? Pydantic AI is an open-source Python agent framework, released in November 2024, that applies Pydantic’s battle-tested validation engine directly to LLM interactions. With 16,500+ GitHub stars and 2,000+ forks as of April 2026, it has become one of the fastest-adopted agent frameworks in the Python ecosystem. Pydantic already powers the validation layer for OpenAI SDK, Google ADK, Anthropic SDK, LangChain, LlamaIndex, and CrewAI — Pydantic AI extends this same validation philosophy to the agent orchestration layer itself. Unlike LangChain, which relies on prompt engineering and string parsing to coerce LLM outputs into structure, Pydantic AI uses native Python type annotations and BaseModel schemas so your IDE catches type errors at write time, not at runtime. The design goal — as stated in the official docs — is to bring the FastAPI ergonomics of type-safe, auto-documented APIs to GenAI agent development: define the schema, wire up the model, and let the framework handle validation, retries, and error recovery automatically. ...

The OpenAI Responses API is the new primary interface for building stateful, agentic AI applications — replacing the Assistants API (being sunset H1 2026) and extending beyond what Chat Completions can do. This tutorial walks through everything from your first API call to building multi-step agents with built-in tools like web search and file retrieval. What Is the OpenAI Responses API? The OpenAI Responses API is a stateful, tool-native interface for building AI agents and multi-turn applications — launched in March 2025 as OpenAI’s replacement for the Assistants API and a significant evolution beyond Chat Completions. Unlike Chat Completions, which is stateless (every request requires you to resend the full conversation history), Responses API maintains conversation state server-side using previous_response_id. A 10-turn conversation with Chat Completions resends your entire history on turn 10, making it up to 5x more expensive for long dialogues. Responses API sends only the new message each turn — the server already holds context. Built-in tools (web search at $25–50/1K queries, file search at $2.50/1K queries) are first-class citizens rather than custom function definitions, and reasoning tokens from o3 and o4-mini are preserved between turns instead of being discarded. OpenAI has moved all example code in the openai-python repository to Responses API patterns — it is where the platform is going. ...

LangGraph is a Python and JavaScript framework for building stateful, graph-based AI agents. Unlike simple chain-based approaches, LangGraph lets you define agents as directed graphs where nodes are processing steps and edges determine flow — including loops, conditionals, and human approval gates. With 126,000+ GitHub stars as of April 2026, it’s the most widely adopted open-source framework for production AI agents. What Is LangGraph and Why Use It in 2026? LangGraph is an open-source orchestration framework built on top of LangChain that models AI agent workflows as graphs — nodes represent computation steps (calling an LLM, running a tool, parsing output) and edges represent transitions between those steps, including conditional branching. Released in 2023 under the Apache 2.0 license, LangGraph reached version 1.1.6 in April 2026 with over 126,000 GitHub stars. The core insight is that production AI agents are inherently cyclic: an agent reasons, acts, observes, then reasons again until done. Simple chain frameworks force you to unroll those loops manually; LangGraph handles them natively. State persists across the entire graph execution via checkpointers (SQLite, PostgreSQL, in-memory), making it trivial to pause mid-workflow, resume after a crash, or implement human-in-the-loop approval gates. Compared to CrewAI (role-based team abstraction) or AutoGen (conversational multi-agent), LangGraph gives you lower-level control — you explicitly wire the graph topology rather than letting the framework infer it from roles. That control pays off at production scale: parallel tool execution, fine-grained error recovery, and streaming output all come standard. ...