Build on Axiru.
Developer documentation for the REST API, the MCP server, the policy DSL, webhooks, decision sealing, replays, and cross-rail governance. If you are integrating Axiru programmatically, start here.
Connect Stripe and replay 90 days in 10 minutes
Shadow mode quickstart
Connect Stripe read-only, upload a CSV or import live, see what tighter policy would have caught.
Trust overview
Security architecture, isolation model, key handling, and the read-only enforcement boundary.
How Axiru works (operator walkthrough)
End-to-end product walkthrough for a finance or support lead evaluating the platform.
REST + MCP for programmatic access
API overview
Authentication, idempotency, error model, rate limits, and the canonical resource map.
Decisions API
Submit a refund, payout, or transfer for policy evaluation. Returns allow, require approval, or block with sealed evidence.
MCP server (for AI agents)
Public MCP endpoint at /api/mcp lets compatible agents list approvals, approve/reject, and inspect the audit ledger.
Cross-rail policy, approvals, decision ledger
Cross-rail governance
How one policy path covers refunds, disputes, payouts, transfers, and Connect application-fee refunds.
Policy DSL reference
Plain-language rule syntax, versioning, deterministic evaluation, replay semantics.
Decision ledger
Hash-chained sealing, replays, SIEM/S3 exports, evidence packaging.
Playbooks and templates
Files, manifests, and discovery
llms.txt
Short LLM-readable product index.
llms-full.txt
Expanded body content for retrieval-augmented LLMs.
ai-plugin.json
AI plugin manifest. Points at the MCP endpoint at /api/mcp.
security.txt
Security contact and disclosure policy.
robots.txt
Crawler policy. Explicit allow for 15+ AI crawlers.
sitemap.xml
Indexed marketing pages.
Ship outflow governance you can call from any stack.
REST, MCP, webhooks. Start in shadow mode, move to live enforcement when you are ready.
Start in shadow mode first. Move to live enforcement later.