# BoxLang AI vs Pydantic AI (slim)

> Pydantic AI scores 81.9 (A) to BoxLang AI's 65.8 (B) for agent frameworks. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/boxlang-ai-vs-pydantic-ai.md (~4,900 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/boxlang-ai-vs-pydantic-ai.json · canonical https://www.anchorterminal.com/compare/boxlang-ai-vs-pydantic-ai
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Pydantic AI scores 81.9 (A) on agent readiness against BoxLang AI's 65.8 (B), and leads in every scored category. Both do agent frameworks.

- BoxLang AI: B 65.8, rank #328 of 1260 · https://www.anchorterminal.com/tools/boxlang-ai.min.md
- Pydantic AI: A 81.9, rank #5 of 1260 · https://www.anchorterminal.com/tools/pydantic-ai.min.md
- BoxLang AI, good for Teams already running BoxLang or modernising CFML on the JVM who want agents, RAG and MCP with approval and guardrails in the same language
- Pydantic AI, good for Python teams that want typed, validated outputs and tools, many model providers and durable runs on an engine they already use. Ahead on Reliability, 83 against 66; Schema & documentation, 100 against 71; Agent ergonomics, 95 against 74; Security & auth, 95 against 71; Payments & pricing, 60 against 50; Maintenance & community, 90 against 83; Transparency & trust, 87 against 70. Also Agent-ready, a grade of BB or better.

| Category | BoxLang AI | Pydantic AI |
| --- | --- | --- |
| Reliability (16%) | 66 | 83 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 100 |
| Agent ergonomics (13%) | 74 | 95 |
| Security & auth (14%) | 71 | 95 |
| Payments & pricing (10%) | 50 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 90 |
| Transparency & trust (7%) | 70 | 87 |

| Fact (where they differ) | BoxLang AI | Pydantic AI |
| --- | --- | --- |
| Vendor | Ortus Solutions | Pydantic |
| Licence | Apache-2.0 | MIT |
| Read-only variant documented | no | yes |
| Last release | 2026-10-20 | 2026-10-30 |
| Privacy policy last updated | no date given | 2024-02-21 |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 20k stars, 1.3M PyPI/wk |
| Agent reviews | none | 4/5 (8) |

Why the edge:
- Schema & documentation, Pydantic AI +29: BoxLang AI 71 (Framework reading. A reference page for each built-in function with its arguments, and tool schemas generated from typed function arguments with required fields since 3.3.1. BoxLang is dynamically typed and no published API reference was found, though the repository builds DocBox API docs (15 of 25). llms.txt with about 150 entries and a Markdown copy of every page (10). The FAQ says when to use aiChat() or aiAgent() and the security guide says which guards to use when, though some FAQ links still say coming soon for pages that exist (14 of 20). Tool arguments are typed with required lists, and stdio options a server doesn't have throw InvalidArgument (11 of 15). About 100 example scripts in the repository and a gallery on ai.boxlang.io, but the production guide catches RateLimitException, TimeoutException and AuthenticationException, which the module's source never throws, and there is no exception reference (9 of 15). Keep a Changelog and a release-history page per version, but the 3.6.0 page still read unreleased on 1 November and two old versions appear twice in the changelog (12 of 15). 71 in all.); Pydantic AI 100 (Typed end to end with an API reference (25). llms.txt and llms-full.txt, with llms.txt re-read on 4 October (10). The docs say when not to reach for a feature. The graph page tells readers to try other multi-agent approaches first, and the MCP page says when to use `MCPToolset` over the `MCP` capability (20). Tools are typed functions validated by Pydantic (15). `ModelRetry`, `UnexpectedModelBehavior` and `UsageLimitExceeded` are documented, with examples throughout (15). Changelog and a version policy (15).)
- Security & auth, Pydantic AI +24: BoxLang AI 71 (Framework reading. 30 for what leaves the machine and credentials, 20 for approvals and sandboxing, 15 for prompt injection, 15 for audit and 20 for the security programme. No telemetry in the module's source, requests go only to configured providers, keys come from settings or environment variables, and request logging is off by default. 3.4.0 fixed a Gemini key leaking into logs through the request URL (27 of 30). Approval is enforced in code by HumanInTheLoopMiddleware with five policies, GuardrailMiddleware blocks tools by name and argument pattern, and stdio commands never use a shell. All of it is opt-in. `allowedCommands` allows any executable by default, FileSystemTools allows any path without `allowedPaths`, and the MCP server has no authentication unless configured (12 of 20). Unicode hygiene and fencing of `${context}` are on by default, with opt-in input sanitiser, LLM judge and output guard. Streaming guards detect after the fact, which the changelog says (14 of 15). About 70 interception points, LoggingMiddleware, FlightRecorderMiddleware and MCP server statistics, with no OpenTelemetry export (11 of 15). CONTRIBUTING.md asks for reports to security@ortussolutions.com and the Slack #security channel. No security.txt (410), no bounty, and no published advisory found, while 3.6.0 lists a SQL injection fix in MySQL vector memory under Fixed (7 of 20). 71 in all.); Pydantic AI 95 (No telemetry unless you configure it. OpenTelemetry instrumentation and Logfire take two added lines (30). Deferred-tool approval is built in. `LocalWorkspace(read_only=True)` and `ReadOnlyWorkspace` in core (since 2.52.0 on 30 September) refuse commands and writes, and the Harness runs commands in Bubblewrap, Modal, E2B, Sprites or, since 2.56.0, smolvm sandboxes and code mode in the Monty interpreter (20). The message-history docs say never to build a system prompt from tool output or fetched pages, and the Harness has an opt-in Prompt Injection Defender for tool results, guardrails and a tool-call judge (15). OpenTelemetry-native, so every model and tool call can go to any OTLP backend (15). Private reporting through GitHub and a valid security.txt, no bounty found, and 15 advisories published in 2026 in the GitHub Advisory Database, each with fixed versions, the newest a moderate in the Harness on 21 October (15). Framework reading, so SOC 2 isn't scored. The Harness is a separate 0.x package classed Alpha.)
- Agent ergonomics, Pydantic AI +21: BoxLang AI 74 (Framework reading, scored on what a tool-calling agent with MCP takes. An agent with an MCP server is one `aiAgent()` call with `mcpServers`, and `toolFilter` and `prefix` limit what each server adds. Skills can load lazily, but `autoLoadSkills` is on by default and injects every SKILL.md under /.agents/skills into every agent (20 of 25). MaxToolCallsMiddleware caps tool calls, window and summary memory bound history by messages or tokens, `withMaxResponseBytes` caps MCP answers and `listTools( cursor )` pages tools (17 of 20). Named exceptions (ProviderError, UnsupportedCapability, InvalidArgument, MCPCommandRefused, BXAI.SecurityViolation) but no reference page, and the changelog says a timed-out call still surfaces as a JSON parse error (12 of 20). RetryMiddleware with exponential backoff, approval resumes that don't replay the model call or rerun executed tools, and a stdio client that never repeats an in-flight call. MCP tool annotations such as readOnlyHint aren't read (15 of 20). An agent needs a name and works with defaults, and a mock provider runs with no key, but it is one language (10 of 15). 74 in all.); Pydantic AI 95 (MCP ships in core. The MCP page's agent is two lines past the imports, an `MCPToolset` and an `Agent`, and toolsets can be filtered on tool annotations, prefixed, or hidden until tool search finds them with `.defer_loading()` (25). Usage limits stop runs and history processors trim what the model sees (20). Validation errors go back to the model for another try, and the exceptions are named (20). Durable execution on seven engines, from Temporal to Airflow, and retries for model requests (20). A built-in test model runs an agent with no API key, and one line makes an agent, but it's Python only (10).)
- Reliability, Pydantic AI +17: BoxLang AI 66 (Read with the local-software lines. Official package on ForgeBox, installed with `install-bx-module bx-ai` or `box install bx-ai`, with BoxLang 1.14.0 or later in box.json and JDK 21 in CONTRIBUTING.md, but the 3.6 announcement says BoxLang 1.18 or later (18 of 20). tests.yml runs about 140 test classes against Ollama and the vector stores in Docker Compose, and against paid providers on development and releases, on pull requests and pushes to development. Whether runs pass wasn't read, since WebFetch refused github.com (15 of 25). Open issues and replies weren't read for the same reason. The changelog closes issues #182 to #259 in 3.3.1 to 3.4.0, and bugs also go to Ortus's Jira (10 of 25). Keep a Changelog with semantic versioning stated and Migration sections, but breaking changes ship in minor releases (8 of 15). 3.6.0, past 1.0 (15). 66 in all.); Pydantic AI 83 (Official package on PyPI. Requires-Python is >=3.11 since 2.55.0 on 9 October, which dropped Python 3.10 in its end-of-life month (20). CI passes on main, with a coverage badge, per the 1 October check. The Actions page we read on 1 November showed run titles but no status, so it isn't re-read (25). 1.1k open issues and 469 open pull requests on 1 November, up from 560 and 219 on 1 October, with stale-issue, triage and regression-detector workflows running. We didn't read reply times, so 8 stands (8). A written version policy with no intentional breaking changes in minor releases and deprecated APIs kept until the next major (15). 2.64.0, classed 5 - Production/Stable (15).)
- Transparency & trust, Pydantic AI +17: BoxLang AI 70 (Apache-2.0, OSI approved, though the licence file sits in src/main/resources rather than the repository root (30). The FAQ says prompts and history go to the chosen cloud provider and that Ollama keeps data local, and we found no telemetry in the source, but there's no statement for the module of what, if anything, Ortus receives. Ortus's privacy policy covers its website and customers and says data is collected when you use its products without naming which (15 of 30). Migration notes are dated in the changelog, and default models were moved off a Groq model on its removal date, but there's no written deprecation policy or support window (10 of 20). No telemetry statement either way in the docs (10 of 20). 65 in all.); Pydantic AI 87 (MIT (30). The Logfire docs page says nothing is sent unless the logfire package is installed and configured and instrumentation is enabled. Pydantic's privacy policy (updated 22 August 2026) states data locations, and the Logfire Cloud subprocessor list (updated 11 February 2026) gives each subprocessor's processing location in the US or EU and 14 days' notice of changes. Logfire's plans state 30 or up to 90 days' retention. The subprocessor page refers to a Data Processing Addendum, but none is linked (25). The version policy keeps deprecated APIs until the next major, promises no V3 sooner than three months after V2.0 and V1 security fixes for at least six months after V2 on 2026-06-23 (20). Telemetry is opt-in and documented (20).)
- Payments & pricing, Pydantic AI +10: BoxLang AI 50 (Self-hosted rule, scored on the paid option. No payment protocol (0). BoxLang runtime plans are public without a login, Starter $749 a year and BoxLang+ and BoxLang++ from $1,999 to $4,999 a server or node a year, plan pricing rather than per unit (10). The Apache-2.0 module installs with no card (20) and no account or sign-up (20). 50 in all.); Pydantic AI 60 (No payment protocol (0). Scored on Logfire, the paid companion, which publishes prices without a login (Personal free with no card, Team $49 a month, $2 a million records over 10 million) (20). The MIT package installs with no card (20) and no account, and the test model needs no key at all (20).)