django-spec-agents

Pydantic-AI agents for Django, in two halves. The agent host takes an AgentConfig and a tool registry and returns a built pydantic_ai.Agent, with an audit trail over every tool call, a server-side approval gate for destructive tools, a failure policy, conversation and attachment stores, and an opt-in store app. It reads no Django settings of its own: a transport such as django-ag-ui owns its settings, builds the config and hands it down. spec_tools, behind the [specs] extra, serves django-service-specs specs to an agent as tools, in process, with each spec's own validation, permissions and rendering: SpecToolset, and SpecCapability over it.

The host was published as django-pydantic-agent and spec_tools as djangorestframework-pydantic-ai. This package carries both under one import path, django_spec_agents, and the root never imports spec_tools, so the host installs and runs without the extra.

Install

pip install django-spec-agents            # the agent host
pip install "django-spec-agents[specs]"   # and specs as agent tools

Python 3.10 or later and Django 4.2 or later. [specs] adds django-service-specs. The other extras: [drf-mcp] bridges a djangorestframework-mcp-server registry as a toolset, [harness] adds the pydantic-ai-harness capabilities, and [anthropic], [openai] and [google] add a model provider.

The store app is opt-in. To persist conversations, attachments, steps and memory in the database, add it to INSTALLED_APPS, where its label is django_spec_agents_store, and run migrate:

INSTALLED_APPS = [
    # ...
    "django_spec_agents.contrib.store",
]

Quickstart

An agent over tools you register:

from django_spec_agents import AgentConfig, AgentDeps, ToolRegistry, build_agent, tool

registry = ToolRegistry()


@tool(registry)
def list_orders(status: str) -> list[dict]:
    """List orders with the given status."""
    ...


agent = build_agent(registry, AgentConfig(model="anthropic:claude-sonnet-4-5"))
result = await agent.run("what is still pending?", deps=AgentDeps(user=request.user))

The same agent calling your specs beside the registry's tools, with [specs] installed. Each key is a tool name, distinct from the registry's; the description, the parameter schema and the return schema come from the spec. Each spec declares its permissions, which the toolset refuses to go without, because nothing over HTTP gates a call made in process:

from django_spec_agents.spec_tools import SpecToolset

toolset = SpecToolset({"list_invoices": list_invoices_spec, "create_invoice": create_invoice_spec})
agent = build_agent(registry, AgentConfig(model="anthropic:claude-sonnet-4-5", toolsets=[toolset]))

Documentation

https://artui.github.io/django-spec-agents/

• Concepts: how a config becomes an agent, and what belongs here versus in a transport.
• Tools: registering tools and what their metadata does.
• Storage: the store contracts, owner scoping and the store app.
• Policy: audit, the approval gate and the failure policy.
• Integrations: specs and MCP tools as agent tools.
• Spec tools: SpecToolset and SpecCapability in depth.
• Reference: the public API.

License

MIT. See LICENSE.