Skip to main content

PRAXO-CORE: Python Agent Framework

PRAXO-CORE is a dependency-free Python framework for building tool-using AI agents. It provides the agent runtime, not a model or hosted service, so you keep control of your models, tools, storage, and sandboxing.

It is for teams that want a small, explicit agent loop instead of a large orchestration platform:

  • Async-first models, tools, events, and sessions.
  • Policy hooks, approvals, path checks, PII redaction, and call limits.
  • Context budgets, checkpoints, middleware, and fallback models.
  • Streaming, cancellation, and an OpenAI-compatible adapter.
  • No runtime dependencies; Python 3.11 or newer.

Install

pip install praxo-core==0.3.0

For a source checkout:

pip install ./language/python

Quickstart

import asyncio

from praxo.agent import Agent, AgentOptions, Session
from praxo.event import Event
from praxo.model import Message, Response, Usage
from praxo.tool import FuncTool, Registry


class EchoModel:
    async def generate(self, request):
        return Response(message=Message(role="assistant", content="hello"))


class LogSink:
    async def emit(self, event: Event) -> None:
        print(event.to_wire())


async def main() -> None:
    tools = Registry()
    tools.register(FuncTool("echo", "Echo input", lambda args: args))
    agent = Agent(
        AgentOptions(model=EchoModel(), tools=tools, events=LogSink())
    )
    result = await agent.run(Session(id="session-1"), "hi")
    print(result.output, result.steps, result.usage)


asyncio.run(main())

What you get

Area Included
Agent loop Tool calls, multi-step runs, parallel tools, structured output
Governance Policy hooks, tool selection, PII middleware, call limits, HITL interrupts
Runtime Context budgets, checkpoints, events, streaming, cancellation
Integration OpenAI-compatible adapter; bring your own model and tools

Contract and status

The normative contract is spec/; Go remains the reference implementation. This package supports SPEC_VERSION 0.2.0 and passes all eleven conformance vector groups. Source version 0.3.0 is published from tag python/v0.3.0; the PyPI package is published by that tag. VFS and plugin hosts are not yet implemented.

Requirements

  • Python 3.11 or newer
  • No runtime dependencies

Contract Surface

Module Contract
praxo.model Model, Request, Response, messages, tool specs, usage
praxo.tool Tool, Registry, FuncTool
praxo.event Event, Sink, MultiSink, FilterSink
praxo.policy Hook, Action, Decision, PathChecker
praxo.memory Store, Record, MemoryStore, ContextAssembler
praxo.checkpoint Checkpoint, Allowlist
praxo.agent Agent, AgentOptions, Session, Result
praxo.hitl Interrupt, InterruptDecision, approve/edit/reject/respond handlers
praxo.context ContextBudget, ModelSummarizer, Offloader, load_agents_md
praxo.middleware call limits, fallback, PII, structured output, tool selection
praxo.toolcall parse_tool_call, strip_tool_call_markup
praxo.jsonschema Schema, ValidationError
praxo.plugin Manifest v1 parsing and validation

Wire codecs preserve the Go names, including image_url, runId, contentBlocks, and plugin plugin_id.

Conformance

From this directory:

python conformance/run.py
python -m unittest discover -s tests -v

Both commands read ../../spec/vectors/*.json. A released Core implementation must pass every vector and keep spec/parity.md current.

API Reference and Build

See API.md. Refresh the checked-in symbol snapshot after a public API change:

python api-snapshot.py
python api-snapshot.py --check
python api-signatures.py --check
python -m build --wheel --sdist .

The name snapshot and signature snapshot are checked independently. The signature baseline covers class constructors, dataclass fields/defaults, methods, properties, functions, and exported constants. Both are source-API gates, not runtime or ABI guarantees.

CI installs the built wheel and sdist into separate clean virtual environments and runs tests/installed_smoke.py from outside the source tree. This verifies the packaged artifacts, not the checkout. It does not prove PyPI publication or installation from a package registry.

License

MIT. See LICENSE.

Metadata

Release files for praxo-core 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for praxo-core 0.3.0
File Size Uploaded Provenance Actions
praxo_core-0.3.0.tar.gz 91.5 kB With provenance Details for praxo_core-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for praxo-core 0.3.0
File Interpreter ABI Platform Actions
praxo_core-0.3.0-py3-none-any.whl Python 3 none any Details for praxo_core-0.3.0-py3-none-any.whl

Total release size: 135.1 kB

Release files / praxo_core-0.3.0.tar.gz

Download URL praxo_core-0.3.0.tar.gz
Size 91.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9c636907fa6aa1dee221b5088a05d993bb906dba3d39f2ac5b6566a0642b3fb3
BLAKE2b-256 checksum
How to use checksums
ba951aa6b5aef5f018dfdeb1b69cbe919a2f8576cccbcab816d23c978d01ace1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / praxo_core-0.3.0-py3-none-any.whl

Download URL praxo_core-0.3.0-py3-none-any.whl
Size 43.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a310f7c7bb78dc60076b1eb5fd913f1d098e6c2e58fcf41b5b8d829142586b31
BLAKE2b-256 checksum
How to use checksums
b91ac9b7fe12e2d2df4683d1e1319bfdf8045bb3f31ad14f13c2e1ed447906c1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Security for praxo-core 0.3.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for praxo_core-0.3.0.tar.gz

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 Nov 2, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page