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

​
Provider-specific requirements

Connect a personal or workspace access token from Grain API settings. Personal tokens see the user’s data. workspace tokens can see all workspace data. Deepline does not bill for these tools. Grain account limits still apply. List recordings first, then use recording_id for details or JSON transcripts. Pass the returned cursor to fetch another page. Use include to request optional participants, highlights, AI summaries, action items, or notes. Updates, tags, sharing changes, and hook creation/deletion modify Grain data. Creating a hook also sends a reachability test to hook_url. It must return 2xx. Creating an upload URL requires filename and, for workspace tokens, user_id. Upload the file separately to the returned URL. An upload_status hook receives processing results. The create-upload action itself does not upload a recording. Team sharing, OAuth exchange, binary downloads and text exports are not exposed. See docs.txt for the conflicting team-sharing URL and exact excluded operations.

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