djangorestframework-pydantic-ai
Expose djangorestframework-services
services and selectors as a Pydantic-AI toolset, so a
plain pydantic_ai.Agent can call them as tools — no MCP server and no AG-UI
bridge in the path.
Every tool call routes through drf-services' transport-neutral surface
(dispatch_spec plus its off-HTTP helpers), so a tool call runs the same input
validation, the same permission_classes — both class-level has_permission
and object-level has_object_permission on the resolved row — and the same
serializer rendering your DRF views apply, just without the HTTP hop.
Install
pip install djangorestframework-pydantic-ai
It depends only on djangorestframework-services and pydantic-ai-slim. A model
provider is pulled in separately, the usual Pydantic-AI way (e.g.
pip install "pydantic-ai-slim[anthropic]").
Quickstart
from pydantic_ai import Agent
from rest_framework_pydantic_ai import AgentDeps, SpecToolset
toolset = SpecToolset(
{
"list_orders": orders_selector_spec, # SelectorSpec -> read-only tool
"create_order": create_order_spec, # ServiceSpec -> mutation tool
}
)
agent = Agent("anthropic:claude-opus-4-8", deps_type=AgentDeps, toolsets=[toolset])
result = await agent.run(
"create an order of 3 widgets",
deps=AgentDeps(user=request.user),
)
The agent acts as deps.user: each call builds an off-HTTP request/view context,
enforces the spec's permission_classes (class- and object-level),
dispatches the spec, and renders the result through the spec's serializer. List
selectors gain page / limit / order tool args, and return one page —
{"items": [...], "page": 1, "totalPages": N, "hasNext": bool} — so a model
reading a collection can tell whether it saw all of it.
Failures map onto the model loop so the agent self-corrects: invalid input, a bad
page / limit / order value, and unexpected (hallucinated) arguments come
back as ModelRetry; a business error or missing row becomes a readable
{"error": ...}; a denied permission raises PermissionDenied, which aborts
the run under a plain pydantic_ai.Agent. A host that installs a tool-failure
policy — django-pydantic-agent's build_agent does by default — turns that
denial into a failed-tool result instead, so the run continues; the call is
still denied either way. Unexpected arguments are rejected by default — pass
unknown_arguments= to SpecToolset (IGNORE / PASSTHROUGH) to change that.
See the documentation for the full reference.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for djangorestframework-pydantic-ai 0.23.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| djangorestframework_pydantic_ai-0.23.0.tar.gz | 213.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| djangorestframework_pydantic_ai-0.23.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 254.9 kB
Release files / djangorestframework_pydantic_ai-0.23.0.tar.gz
| Download URL | djangorestframework_pydantic_ai-0.23.0.tar.gz |
|---|---|
| Size | 213.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b3d11cca981b055fd06cf7e36c1beca3a5d46c0e45ff53050a6532c457237fa
|
|
BLAKE2b-256 checksum How to use checksums |
6c8dcc0600afb16cc1ceb21ed23dbe821c35cc893af52879a90b07aefe9adaab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency logRelease files / djangorestframework_pydantic_ai-0.23.0-py3-none-any.whl
| Download URL | djangorestframework_pydantic_ai-0.23.0-py3-none-any.whl |
|---|---|
| Size | 41.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
181a63facc20e8ce73961c2f9666862ed1df8a0521e1ab230ca19be79ccd0019
|
|
BLAKE2b-256 checksum How to use checksums |
897b2f3f6f57af61c340f5c2dcc021dc4c61628c22b4b7655fd931bcb796dd33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency log
