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

​
Provider-specific requirements

Kernel is asynchronous company-data infrastructure. Start one job, save its id, and call only the matching getter until the status is completed or failed. Do not loop aggressively. Firmographics can take tens of minutes. Use entity resolution when you need a stable Kernel company id. Parentage and firmographics launchers require that id. Use combined when you want identity resolution plus one or both add-ons in one job. Do not send personal data unless Kernel has explicitly approved that data and use case. Do not provide a webhook URL. Deepline has not yet enabled signed Kernel callback ingestion. The paid launchers are currently unavailable. Their nominal Kernel-credit ladder is documented, but the purchased USD exchange rate and Deepline async refund reconciliation are not configured. Existing job status getters remain available.

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