<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Praxis AI Documentation on Praxis</title><link>https://praxis.fast/ai/v0.4.1/</link><description>Recent content in Praxis AI Documentation on Praxis</description><generator>Hugo</generator><language>en</language><atom:link href="https://praxis.fast/ai/v0.4.1/index.xml" rel="self" type="application/rss+xml"/><item><title>Adding a Built-in AI Filter</title><link>https://praxis.fast/ai/v0.4.1/developing/adding-filters/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/developing/adding-filters/</guid><description>Add a built-in Praxis AI filter by following the filter contract and registering it with the product.</description></item><item><title>Agentic Protocols</title><link>https://praxis.fast/ai/v0.4.1/architecture/agentic-protocols/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/architecture/agentic-protocols/</guid><description>JSON-RPC 2.0 envelope parsing and protocol-specific metadata extraction for MCP and A2A agent traffic.</description></item><item><title>AI Inference</title><link>https://praxis.fast/ai/v0.4.1/architecture/ai-inference/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/architecture/ai-inference/</guid><description>Body-aware classification, routing, and enrichment for AI inference traffic, built on the filter pipeline and StreamBuffer body access pattern.</description></item><item><title>Anthropic Messages API</title><link>https://praxis.fast/ai/v0.4.1/anthropic-messages/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/anthropic-messages/</guid><description>Praxis supports the Anthropic Messages API (/v1/messages) through five composable filters. Operators can route, validate JSON envelopes, and transform Anthropic requests to reach any backend.</description></item><item><title>Anthropic Messages Replay Test Plan</title><link>https://praxis.fast/ai/v0.4.1/anthropic-messages-replay-test-plan/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/anthropic-messages-replay-test-plan/</guid><description>Defines the Anthropic Messages API request and response shapes Praxis AI should cover across replay, passthrough, and translation tests.</description></item><item><title>Features</title><link>https://praxis.fast/ai/v0.4.1/features/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/features/</guid><description>Praxis AI extends the Praxis proxy framework with AI-specific filters and provider integrations.</description></item><item><title>FIPS 140-3</title><link>https://praxis.fast/ai/v0.4.1/fips/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/fips/</guid><description>Praxis AI performs all of its cryptography in the system OpenSSL library.</description></item><item><title>FIPS Tooling</title><link>https://praxis.fast/ai/v0.4.1/developing/fips/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/developing/fips/</guid><description>Local, reproducible checks that a praxis-ai build is on the path to FIPS 140-3 compliance on Red Hat Enterprise Linux.</description></item><item><title>Getting Started</title><link>https://praxis.fast/ai/v0.4.1/developing/getting-started/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/developing/getting-started/</guid><description>compliance check and Red Hat&amp;rsquo;s scanner need podman on Linux)</description></item><item><title>llm-d Integration Testing</title><link>https://praxis.fast/ai/v0.4.1/developing/llmd-integration-testing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/developing/llmd-integration-testing/</guid><description>Praxis AI includes an AI-owned ext_proc compatibility layer for llm-d integration.</description></item><item><title>Migrating to 0.2.0</title><link>https://praxis.fast/ai/v0.4.1/migrating-to-0.2/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/migrating-to-0.2/</guid><description>Version 0.2.0 moves token usage parsing from praxis-ai-apis into the private token usage subsystem in praxis-ai-filters.</description></item><item><title>OpenTelemetry Routing Semantics</title><link>https://praxis.fast/ai/v0.4.1/architecture/opentelemetry/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/architecture/opentelemetry/</guid><description>Add Praxis AI routing decisions to the OpenTelemetry request traces exported by Praxis core.</description></item><item><title>Outbound callout security</title><link>https://praxis.fast/ai/v0.4.1/architecture/outbound-callouts/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/architecture/outbound-callouts/</guid><description>Praxis AI treats an outbound target, its resolved socket addresses, and the credentials attached to the request as one trust decision.</description></item><item><title>PostgreSQL Cryptographic Boundary</title><link>https://praxis.fast/ai/v0.4.1/architecture/postgres-cryptographic-boundary/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/architecture/postgres-cryptographic-boundary/</guid><description>The openai_response_store and openai_conversations filters can persist state to PostgreSQL.</description></item><item><title>Project Management</title><link>https://praxis.fast/ai/v0.4.1/developing/project-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/developing/project-management/</guid><description>All repositories in the praxis-proxy organization use a consistent workflow for planning, prioritizing, and tracking work.</description></item><item><title>Quickstart</title><link>https://praxis.fast/ai/v0.4.1/quickstart/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/quickstart/</guid><description>Build Praxis AI from source for local development, then route a Responses API request to an AI backend.</description></item><item><title>Release Process</title><link>https://praxis.fast/ai/v0.4.1/release/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/release/</guid><description>Praxis AI uses Semantic Versioning. The workspace version is the single source of truth, defined in workspace.package.version in the root Cargo.toml. All workspace crates inherit this version.</description></item><item><title>Response Store</title><link>https://praxis.fast/ai/v0.4.1/architecture/response-store/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/architecture/response-store/</guid><description>Durable persistence for OpenAI Responses API responses, enabling retrieval (GET), deletion (DELETE), and input-item pagination across proxy restarts.</description></item><item><title>Responses Store Schema Migration (v2 → v3)</title><link>https://praxis.fast/ai/v0.4.1/store/schema-migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/store/schema-migration/</guid><description>Replace the disposable v3 response store with a fresh v4 database before starting current releases; startup creates the required schema.</description></item><item><title>Run Codex or Claude Code through Praxis and vLLM</title><link>https://praxis.fast/ai/v0.4.1/developing/cli-vllm-through-praxis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/developing/cli-vllm-through-praxis/</guid><description>Connect Codex or Claude Code through a local Praxis AI gateway to inference served by vLLM.</description></item><item><title>Type Design</title><link>https://praxis.fast/ai/v0.4.1/developing/type-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://praxis.fast/ai/v0.4.1/developing/type-design/</guid><description>Make invalid states unrepresentable. The type system and serde should enforce constraints at parse time, not at runtime.</description></item></channel></rss>