It's a plug-and-play HTTP orchestrator that sits between AI agents/clients and merchant backends, handling reliable cart → checkout → payment flows with built-in support for emerging standards:

- UCP discovery (GET /.well-known/ucp + capability manifest) - A2A envelopes (/api/v1/a2a/checkout, /a2a/cart endpoints) - AP2 payment intents (consent proofs, handler binding, strict mode) - MCP conformance references

v0.2.0 updates (just tagged): - Durable payment state survives restarts/pod crashes - Stricter AP2 validation (structured proofs + optional trusted issuers allowlist) - Prod hardening (required PUBLIC_BASE_URL, single-replica K8s defaults, persistence alignment) - Updated docs, release notes, CHANGELOG

Built in Rust (multi-crate workspace, Actix/Axum), Dockerized, full K8s manifests (Deployment/HPA/PDB/NetworkPolicy/etc.), observability, idempotency/outbox/dead-letters/reconciliation.

No Rust needed to use: env-var config + point agents at it. Ops-ready with mocks/examples.

Why now: Google/Shopify UCP push + AP2/ACPA2A patterns mean merchants/agent devs need a neutral layer for protocol chaos + reliability.

Very early (single contributor), but looking for: - Feedback on API/protocol handling/edge cases - Deployment experiences or perf thoughts - Early pilots/testers (happy to debug integration)

Thanks to anyone in Rust, agentic AI, or e-commerce protocols for input!