Skip to content
GARD

Developers

Add GARD before execution.

Give autonomous applications a policy and transaction-decision layer with a simple integration.

Conceptual integration

Planned
agent.ts
const decision = await gard.evaluate({
  wallet,
  asset: "USDC",
  amount: 500,
  recipient,
  purpose: "Purchase API credits",
});

if (decision.decision === "ALLOW") {
  await wallet.send(tx);
}

Conceptual API

POST /v1/evaluate

Submit a proposed transaction and receive a decision before anything is executed.

Planned
Request
POST /v1/evaluate

{
  "wallet": "0x...",
  "asset": "USDC",
  "amount": 500,
  "recipient": "0x...",
  "purpose": "Purchase API credits"
}
Response
{
  "decision": "REVIEW",
  "confidence": 0.91,
  "reasons": [
    "new_recipient",
    "unusual_transaction_size"
  ]
}

Planned API interface — example only. No production endpoint is available yet.

Integration lifecycle

Six steps from request to record.

  1. 1

    Create request

    Your agent or app builds the proposed transaction with its purpose.

  2. 2

    Submit to GARD

    Send the request to the evaluate endpoint before signing.

  3. 3

    Receive decision

    GARD returns ALLOW, REVIEW, or BLOCK, with reasons.

  4. 4

    Apply application policy

    Your application decides how to handle each outcome.

  5. 5

    Execute or stop

    Proceed on ALLOW, route to a person on REVIEW, halt on BLOCK.

  6. 6

    Record result

    Store the decision and outcome for audit and analysis.

Developer benefits

Built for the people wiring up autonomous money.

  • Simple API

    One request, one decision. Minimal surface to integrate.

  • Structured output

    Machine-readable decisions and reason codes.

  • Policy-first architecture

    Explicit rules sit alongside risk evaluation.

  • Auditability

    Decisions are designed to be recorded and reviewable.

  • Designed for autonomous systems

    Built for software that spends without a person in the loop.

SDKs and interfaces

Planned SDKs.

None of the following are available yet. They describe the interfaces we intend to provide.

  • Planned

    TypeScript

    Typed client for browser and server runtimes.

  • Planned

    Node.js

    Server-side helpers and webhook verification.

  • Planned

    REST API

    Plain HTTPS and JSON for any language.

  • Planned

    Webhooks

    Notifications for REVIEW decisions and outcomes.

See the flow end to end.

Read the documentation, or try the demo with a mock evaluator.