Five steps. One API call before any spend.
Sandbox in 60 seconds. Live in production the moment your policy is set. No SDK install required for the first call.
- 01
Register and verify
Sign up and start in sandbox immediately — pre-seeded with a demo policy context, agent, and sample decisions. Verify identity (KYC / KYB) only when you switch to live keys or a regulated workload.
Browser-first capture · encrypted handling · KYC gated to go-live, not signup - 02
Define a policy context
A policy context is a named container for one agent or workload: budget limit, billing period, vendor allow/deny, single-transaction max, monthly cap, and an approval threshold. Pick a template or compose your own.
Money never moves to Greene. Budgets are policy, not deposits. - 03
Mint a delegate token
Generate a scoped, time-bound token tied to your policy context. Hand it to the agent. The token is shown once — afterwards we only see its SHA-256 hash. Revocable in one click.
Zero secrets in URLs. Every check recomputes the hash and looks it up. - 04
Authorize every spend
Before your agent calls Stripe, ACH, or any payment rail, it sends the spend intent (amount, vendor, context) to Greene. We evaluate identity, period budget, vendor rules, and counterparty trust — and return approved, denied, or pending.
Approved → signed authorization token. Denied → reason code. Pending → human review. - 05
Your rail executes. We pin the receipt.
Pass the signed authorization token as metadata to your existing payment call. Every approval, denial, freeze, and policy change lands in the immutable audit log with timestamp, actor, and reason — ready for export to your SIEM or auditor.
Append-only · hash-chained · exportable as JSON or CSV
What it looks like in production.
Ready to plug in?
Sandbox is free forever and lets you prove the integration end-to-end before a single dollar moves.