What Parmana is
Think of how a card network authorizes a purchase. Visa doesn’t stock the shelves or move the money itself. It decides, quickly and cryptographically, whether the transaction is allowed, then hands the merchant’s bank a signed authorization to act on. Parmana plays that role for automated business actions. An agent proposes an action. Parmana’s policy engine decides, deterministically, whether it’s allowed. If approved, Parmana issues a signed, single-use, time-bounded authorization. Your own systems, through a Connector, are what actually execute it. Parmana never touches your systems directly, the same way a card network never touches the goods on the shelf.The trust chain, at a glance
packages/api/src/server.ts) wires the Execution Gateway unconditionally: there is no
code path where a request skips it. See How Parmana thinks for what
each stage guarantees and why.
Status tags used throughout this site
[AVAILABLE]
Built and tested in this repo today. Cites the source file(s) and/or test(s)
that prove it.
[PARTIAL]
Exists, but incomplete. States exactly what works and what doesn’t.
[ROADMAP]
Designed, not yet built. Says so in the first sentence, never documented as
if it ships.
Where to go next
Quickstart
Install to first authorized execution in under 10 minutes, using the
in-memory server.
How Parmana thinks
The concepts behind the diagram above: policy, authorization, the gateway,
trust records.
End-to-end: agent to Paytm
The same flow against a real connector and real infrastructure, start to
finish.
SDKs
TypeScript and Python, both published, both with a builder that removes the
most common integration mistake.