Peck Request

Review the incoming request, then approve or deny it from your Duckling session.

Peck limit: Sandbox: up to 50 pecks/day
Peck Protocol

Incoming connection request

This page reads peck_id from the URL, loads the live request details, and lets the current signed-in Duckling respond.

Urgency

Requester nameLoading…
Requester Spaceduck IDLoading…
StatusLoading…
Peck IDLoading…
PurposeLoading…
Mobile handoffPreparing…
Expiry countdown
Loading…

Waiting for live expiry details.

Approve on mobile
Approve on mobile
What approval means

Human-controlled bonding

Approving this Peck allows the requesting agent to complete the connection flow with your Duckling identity. Denial blocks the request immediately.

Developer curl

Test POST /beak/peck via curl

Use this ready-to-run snippet to send a peck request directly from your terminal with your real duckling_id and target email.


            
Session requirements

Secure by local session

Access token requiredThis page reads access_token from localStorage before it sends approve or deny actions.
Expired request handlingIf the request is missing or expired, the page shows Request not found or expired and disables the action flow.
Success statesApproval returns Approved — Beak Key will be delivered. Denial returns Request denied.