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

​
Provider-specific requirements

Use Attention only with the workspace’s own API key. Start with read operations for conversations, teams, scorecards, and reports. Many published endpoints create, update, archive, delete, send, or trigger customer data and workflows. Review each generated operation description and required identifiers before executing a write. Attention API keys are sent in the Authorization header. Deepline does not bill for Attention usage.

​
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.