Greene Comply
Quickstart

Integrate in 5 minutes.

Five REST calls. No SDK install required. Run each one against your sandbox endpoint and watch decisions appear live in your dashboard.

01

Get your API key

Sign in and mint a sandbox or live key from Settings or the Developer hub (sidebar: Integrations → Developer). Sandbox keys never touch real money.

# Sandbox keys start with gc_test_, live keys start with gc_live_
export GC_KEY="gc_test_..."
02

Register an agent

Tell Greene Comply who is spending. Returns an agent id you reference from every vault and token.

curl -X POST https://api.example.com/agents \
  -H "Authorization: Bearer $GC_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Research bot", "agent_type": "claude" }'
03

Create a policy context

A policy context is a named container for one agent or workload — budget limit, period, vendor rules, and approval thresholds. Money never moves to Greene.

curl -X POST https://api.example.com/vaults \
  -H "Authorization: Bearer $GC_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Research vault", "agent_id": "agt_...", "daily_limit": 50, "max_single_transaction": 20 }'
04

Run your first authorization check

Before any spend, your agent asks Greene Comply for a decision. Approved means you can charge — denied surfaces a reason your agent can act on.

curl -X POST https://api.example.com/authorize \
  -H "Authorization: Bearer $GC_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "token": "dlt_...",
    "amount": 12.50,
    "merchant_name": "OpenAI",
    "merchant_category": "developer_tools"
  }'
Sample response
{
  "authorized": true,
  "transaction_id": "txn_8a7f...",
  "remaining_balance": 487.50,
  "message": "Transaction approved"
}
05

See it in your dashboard

Every approval, denial, and pending-approval shows up live in your dashboard with a full audit log entry.

06

Optional: Model Context Protocol

Run the official stdio MCP server from packages/greene-mcp. Register it in Cursor or Claude Desktop with GREENE_BASE_URL and GREENE_API_KEY so the model can call authorize_spend as a tool.

cd packages/greene-mcp
npm install && npm run build
export GREENE_BASE_URL="https://your-deployment.example"
export GREENE_API_KEY="gc_test_..."
node dist/index.js

Production hosts and request paths are shown in your workspace after you sign in.

That's the whole integration.

Sandbox is free forever. When you're ready to go live, switch your key prefix from gc_test_ to gc_live_.