Packages
Five packages, one operability ladder. Each unlocks more capability and a different setup path.
| Package | You get | Setup asks for |
|---|---|---|
| Audit | Diagnosis + proof package | No credentials |
| Install | Agent-ready assets installed | An install path + technical owner |
| Monitor | Drift + health over time | A monitor target + alert destination |
| Commerce | Commerce prepared for agents + agent access and protocol readiness | Shopify / VTEX / custom stack + API / OAuth / scope details |
| Enterprise | Governance + integrations + auth.md, MCP/API and delegated access readiness review | Owners + governance review + API / OAuth / service-account details |
Protocol readiness is a layer, not a separate product
- ·Protocols (llms.txt, auth.md, MCP/API, scopes, allowed actions) are pieces of agentic readiness. AgenticFy identifies what is missing, recommends, generates drafts, installs when applicable, validates and governs that layer. It assesses and drafts; it does not provide live auth.md/MCP support, and auth.md ships as a readiness plan your team approves.
See the per-package quickstart for the exact steps. Pricing and pilot timelines are on the pricing page.