Skip to main content
Human guide: work with your agent → Inspect one Edges.run action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use this provider only for LinkedIn, Sales Navigator, or Recruiter Lite actions whose account-execution policy is controlled by Deepline. Public actions run through Deepline-managed LinkedIn identities. Do not ask users or agents to provide identity_ids or identity_mode. public schemas intentionally hide those fields and the runtime forces managed execution. Actions that cannot be forced to managed execution are internal-only. Treat internal actions as account-sensitive because they may require a caller-owned LinkedIn, Sales Navigator, or Recruiter Lite identity. Engagement actions such as message, InMail, connect, follow, like, comment, invite, accept, withdraw, and visit can change account-visible LinkedIn state. Keep them out of public discovery unless a separate safety review approves limits and user confirmation.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.