Skip to content

Product

Bounded authority for agent requests

An Agent Financial Permission defines scope. WAYLOCK evaluates each request against applicable controls.

Explore use casesRead the docsReview security

Sequence

Control before execution

  1. 01External agent
  2. 02Financial identity
  3. 03Bounded permission
  4. 04Policy and risk
  5. 05Human approval when required
  6. 06Authorization
  7. 07Compatible execution rail

Permission, policy, approval, authorization and execution are separate steps. Rails do not grant authority, and human approval does not establish settlement.

Decision

One outcome for each request

Agent

The agent requests

An external agent submits a request through its WAYLOCK identity. It cannot grant itself authority.

POST /v1/authorization-requests

WAYLOCK

WAYLOCK evaluates

  • Agent identity and state
  • Permission version and scope
  • Policy and limits
  • Approval threshold
  • ALLOWWithin the permission ceiling and below the approval threshold.The request is authorized. It is eligible for execution only through a compatible rail; authorized is not paid.
  • APPROVAL_REQUIREDAbove the approval threshold.A person reviews the exact request. A changed amount, currency, payee or purpose needs a new approval.
  • DENYOutside the permission or its policy.No executable instruction is produced, so nothing reaches a rail.

Architectural illustration. No live customer, market or provider is shown.

Control

What a person decides

Controls a person holds

Agent identity
Register the agent and its external agent identity in this workspace and environment.
Permission and limits
Set a ceiling and an approval threshold, separate from credentials.
Pause and revoke
Stop an agent, a verification or a credential when authority should end.

See a bounded request end to end.

Follow an illustrative request through permission, policy, human review when required, and authorization.

Explore use casesGet started