Core Concepts

    How xBPP Works

    Understand the building blocks of execution boundary policy.

    The Evaluation Flow

    YOUR AGENT

    Proposes an Action

    XBPP INTERPRETER

    Evaluates against Policy

    RESULT

    Verdict Returned

    Key Concepts

    Action

    What the agent wants to do

    An Action is a payment request from your agent. It includes the amount, currency, recipient, and any context about why the payment is being made.

    "Pay $50 USDC to 0xABC on Base for API access"

    Policy

    The rules that govern behavior

    A Policy is a JSON document that defines what your agent is allowed to do. It specifies limits, verification requirements, and how to handle edge cases.

    { maxSingle: 100, dailyBudget: 1000, askMeAbove: 500 }

    Verdict

    The decision: ALLOW, BLOCK, or ESCALATE

    The Verdict is what xBPP returns after evaluating an Action against a Policy. It tells your agent whether to proceed, stop, or ask for human approval.

    { decision: "ALLOW", reasons: [], confidence: 0.95 }

    Posture

    Default risk tolerance

    Posture determines how xBPP handles ambiguous situations. AGGRESSIVE favors action, CAUTIOUS favors safety, and BALANCED is the default middle ground.

    posture: "BALANCED" // Unknown vendor → ESCALATE

    The Three Decisions

    ALLOW

    Proceed with the payment. The action is within policy.

    When: Amount is within limits, recipient is verified, no red flags.

    BLOCK

    Stop immediately. This violates policy.

    When: Exceeds limits, blocked recipient, security threat detected.

    ESCALATE

    Pause and ask a human to approve.

    When: High value, first-time vendor, low confidence, unusual pattern.

    Ready to see it in action?