IDENTITY · ACTION CONTROL · EVIDENCE

Every agent gets an address. Every consequential action gets a boundary.

Give your agents a stable identity, decide what they can do alone, and preserve attributable evidence for what happens next.

Start with one controlled action See how approval works

Open early access · Open protocol · No runtime migration

action.requestOPEN EARLY ACCESS

fromfinance@yourcompany.com

intentpayment.instructionUSD 48,300.00

POLICY DECISIONhuman approval requiredbank details changed 4 days ago

bound to immutable intentsha256:84c9...f12a

THE ACCOUNTABILITY GAP

Agents can act. The hard part is proving they were allowed to.

A payment, access grant, contract, or production change can cross the point of no return in seconds. Logs tell you that code ran. Beckon records which identity acted, which policy applied, who approved the exact intent, and what the other side actually acknowledged.

01Which agent and key originated it?
02Was it allowed to act alone?
03Who approved the exact payload?
04Did that payload change?
05What did the counterparty acknowledge?

Identity

A stable, domain-backed Agent Address and cryptographic keys, independent of model, runtime, cloud, and transport.

Action control

Evaluate immutable intent before execution. Allow, deny, or require approval at the irreversible edge.

Evidence

Preserve attributable facts without collapsing signature, authorization, delivery, processing, and outcome into one checkmark.

THE CASE THAT PAYS FOR ITSELF

The bank details changed. Should your agent still pay?

Beckon does not claim to know whether an account is fraudulent. It applies your policy, routes the decision to the right person, binds approval to the exact payment, and keeps the evidence.

Invoice received and payment prepared

Policy detects bank details changed 4 days ago

Human approval required

CFO reviews the exact intent

Approved intent locked to its digest

Execution released and evidence recorded

The supplier was genuine. The account was new. Policy stopped the release until an accountable decision existed.

HUMAN APPROVAL

Approve the action, not the conversation.

Amount, counterparty, destination, and context are frozen before anyone is asked. If the agent changes the action afterward, the approved digest no longer matches and execution fails closed.

beckon approval

finance@yourcompany.com

Pay Supplier XYZ

supplier: Supplier XYZ
invoice: NF-1283
amount: USD 48,300.00
destination: ••••8392

Approval required: bank details changed 4 days ago.

ApproveDeny

Decision will be bound tosha256:84c9...f12a

The channel reaches a person. Assurance tells you what proved their decision.

WhatsApp can collect a response or carry a link to an authenticated review. Those are different evidence levels, and Beckon keeps them different.

REACH THE APPROVER

WhatsAppnotification or response

SMSnotification

Emailnotification or review link

Voicenotification

VERIFY THE DECISION

Channel observedpossession evidence

Corporate SSOauthenticated session

WebAuthncryptographic authentication

Signing keycryptographic decision

Approval assurance profiles

Profile	Typical mechanism	What the receipt can state	Availability
Observed	Messaging channel	Response received through a channel linked to the approver	Early access
Authenticated	Beckon review + corporate SSO	Decision made in a session authenticated by the customer IdP	Planned
Cryptographic	WebAuthn or signing credential	Decision authenticated with a credential bound to the approver	Roadmap

THE BECKON RECEIPT

A receipt is evidence, not a green checkmark.

Some facts Beckon can verify. Some it only observes. Others remain unavailable. Every claim keeps its source and certainty.

If the recipient later provides a signed processing acknowledgement, Beckon issues a new immutable evidence snapshot. It does not rewrite this one.

BECKON RECEIPTrcpt_8s1k2m

IDENTITY

agentfinance@yourcompany.comAgent signed

signing keykey_4c81...9ea2Ed25519

domain controlyourcompany.comDNS verified

POLICY & APPROVAL

policypayments-v4Customer policy

decisionapproval requiredBeckon recorded

approverCFO · usr_71baAttributed

authenticationchannel observedPossession evidence

INTENT INTEGRITY

approved intentsha256:84c9...f12aVerified

executed intentsha256:84c9...f12aVerified

digest matchmatchExecution gate

REMOTE STATE

transport accepted14:31:12 · HTTP 202Observed

recipient processedno attestation availableUnavailable

business outcomenot claimedUnavailable

manifest digestsha256:51ba...a91c

HOW IT WORKS

Four steps to your first controlled action.

Verify your domain

One DNS TXT record proves control of the namespace.

_beckon.yourcompany.com

Create the Agent Address

The logical identity survives changes to model, framework, cloud, and endpoint.

finance@yourcompany.com

Set the autonomy boundary

Declare what runs alone and what needs a human, using Beckon policy or your existing engine.

Connect your runtime

Keep your tools and runtime. Beckon operates when a consequential action requires identity, policy, approval, or evidence, inside or outside your organization.

DEVELOPER EXPERIENCE

Policy runs before the send.

The workload authenticates, Beckon verifies its exact Agent delegation, evaluates the immutable intent, and releases execution only when the evidence matches.

01signed intent
02policy decision
03approval state
04receipt after execution

const finance = new Beckon({ apiKey: process.env.BECKON_API_KEY })
  .agent("finance@yourcompany.com")

const action = await finance.actions.create({
  to: "billing@supplier.com",
  type: "payment.instruction",
  payload: { invoice: "NF-1283", amountMinor: 4830000, currency: "BRL" }
})

action.decision      // "approval_required"
action.intentDigest  // "sha256:84c9..."
action.approval      // { status: "pending" }

HONEST CERTAINTY

What each check means, and what it does not.

BECKON CAN STATEIT DOES NOT STATE

signature validthe action was authorized

domain control verifiedthe counterparty is safe

message deliveredthe recipient processed it

message processedthe business outcome completed

PROTOCOL NEUTRAL

The address stays stable. The transport can change.

A2A, MCP, HTTPS, SMTP, and future transports solve different parts of agent communication. None of them defines the Beckon identity.

A2AinterfaceMCPinternal toolsHTTPSnative transportSMTPcompatibilityfinance@company.com

QUESTIONS BUYERS ASK FIRST

Before you connect an agent.

Does the other side need Beckon?

No. Beckon can control and record your side of the action first. Native counterparties add bilateral signed evidence later.

Is a WhatsApp approval a digital signature?

No. It is a response observed through a channel linked to a person. Higher-assurance policy can require corporate SSO or a cryptographic credential.

Must policy move into Beckon?

No. A decision may come from Beckon or your existing OPA, Cedar, IAM, or fraud system. Beckon binds its reason to the exact intent.

Does Beckon replace A2A or MCP?

No. Beckon reuses compatible interfaces and keeps the Agent Address independent from transport.

What happens if Beckon is unavailable?

Sensitive actions fail closed or follow an explicit timeout and escalation policy. Availability targets will be published before production commitments.

Is Beckon a workflow engine?

No. Beckon stays narrow: identity, addressing, reachability, messaging, and optional control and evidence at the irreversible action boundary.

OPEN EARLY ACCESS

Start with the action you cannot safely release today.

Tell us which consequential agent action needs a clear autonomy boundary.