# Deepline documentation map > Deepline is the execution layer for repeatable GTM work done by coding > agents. ## How to use this index - Each topic below points to the one documentation page that owns that job or contract. Compatibility routes and legacy duplicate pages are intentionally not listed. - A maintained Play's live contract owns its current input schema, output schema, route, and Deepline-credit price. Inspect it before a paid or production run. - A result, a no-result state, and an approval to activate data are different outcomes. Keep them distinct in a workflow. ## Start with the interface you have - [Quickstart](https://deepline.com/docs/quickstart): For a shell-capable coding agent. Install Deepline, authorize one workspace, and run one request. - [Claude plugins](https://deepline.com/docs/claude-plugins): Use Deepline from Claude Code or Claude Cowork. - [Set up Deepline MCP](https://deepline.com/docs/mcp/setup): Connect a remote MCP client when it cannot use a shell. - [SDK quickstart](https://deepline.com/docs/sdk-v2/quickstart): Run a first code-owned workflow through inspect, pilot, review, and scale. ## System model - [What is Deepline?](https://deepline.com/docs/introduction): Explains the execution model for coding-agent GTM work. - [Plays](https://deepline.com/docs/plays/plays-overview): Versioned code for repeatable GTM work that runs inside Deepline. - [Prebuilt Plays](https://deepline.com/docs/plays/tasks-overview): Maintained bounded lookups; use a workspace-owned Play when you need your own code or control flow. - [Monitors](https://deepline.com/docs/plays/monitors): Accept supported events pushed from an external source, write accepted events to the Database, and trigger a Play. - [Where data lives](https://deepline.com/docs/data-lifecycle): Use a CSV for a small pilot, the Database for durable working state, and a CRM for approved operational records. - [Query Database](https://deepline.com/docs/database-access): Query workspace data through the API or SDK; use a direct PostgreSQL URI only when a database-native client genuinely needs one. - [Designed for agents](https://deepline.com/docs/designed-for-agents): How the CLI, SDK, typed Plays, and run records fit agent workflows. ## Choose a workflow - [Choose a workflow](https://deepline.com/docs/plays/decision-tree): Choose a workflow from the data you have and the result you need. - [Email Waterfall](https://deepline.com/docs/plays/email-waterfall): Find a work email from a name and company domain or from a LinkedIn URL. - [Choose a research workflow](https://deepline.com/docs/recipes/research-workflow): Choose an evidence-first workflow for a specific GTM decision. - [Signal playbooks](https://deepline.com/docs/plays/signal-playbooks): Apply the shared evidence, qualification, ownership, and activation pattern to a signal. - [Competitive and ad intelligence](https://deepline.com/docs/plays/play-ad-intelligence): Collect source-backed competitor evidence before a campaign or positioning decision. - [Lead scoring and signal discovery](https://deepline.com/docs/plays/play-qualify-lead-fit): Score existing accounts using firmographic fit and account evidence. - [Personalize Outbound with a Deepline Play](https://deepline.com/docs/plays/play-personalize-outreach): Use research-backed account and prospect context to draft a specific outreach angle for review. - [Job changes and CRM cleanup](https://deepline.com/docs/plays/play-job-change-alerts): Detect confirmed job changes, refresh records, and prepare re-engagement decisions. - [Warm outbound from Warmly](https://deepline.com/docs/recipes/warm-outbound-web-intent): Qualify visitor events before an approved CRM or campaign action. - [Paid ads audiences](https://deepline.com/docs/ads-audiences): Build consented, suppressed, and reviewed Google Ads, Meta, or LinkedIn audiences from first-party data. - [Migrate from Clay](https://deepline.com/docs/migrate-from-clay): Translate a Clay table workflow into a code-owned Deepline workflow. ## Prebuilt lookup guides - [Find work email](https://deepline.com/docs/plays/task-find-work-email): Use a maintained work-email Play for one person or a CSV; review no-result states and live usage before scale. - [Find personal email](https://deepline.com/docs/plays/task-find-personal-email): Find a personal-email candidate for a named person, then review the result and applicable policy before activation. - [Find a phone number](https://deepline.com/docs/plays/task-find-mobile-phone): Find and review a phone candidate for a known person; line type is not a guarantee of mobile coverage. - [Find a LinkedIn profile](https://deepline.com/docs/plays/task-find-linkedin-profile): Resolve and review a LinkedIn profile candidate from a named person and company context. - [Find decision makers](https://deepline.com/docs/plays/task-find-decision-makers): Find role-matched company contact candidates and inspect their evidence before further enrichment. - [Enrich a company](https://deepline.com/docs/plays/task-enrich-company): Enrich a known company using the live contract, then map only reviewed fields downstream. - [Validate an email before outbound](https://deepline.com/docs/plays/task-email-waterfall-with-validation): Check an existing email with a dedicated validation action before a send or sync. - [Email to person enrichment](https://deepline.com/docs/plays/person-enrichment-from-email-waterfall): Inspect the narrow reference for person and company context when you already know an email address. ## Signal decision guides - [Champion tracking](https://deepline.com/docs/plays/signal-champion-tracking): Qualify a confirmed former-customer job change before a re-engagement decision. - [Hiring signals](https://deepline.com/docs/plays/signal-hiring): Qualify a relevant job posting as account evidence before outreach. - [Fundraising signals](https://deepline.com/docs/plays/signal-fundraising): Qualify a dated funding event before proposing an account action. - [Company news and public engagement](https://deepline.com/docs/plays/signal-company-news): Qualify a public company event or discussion before proposing an account action. - [Competitive intelligence signals](https://deepline.com/docs/plays/signal-competitive-intel): Decide whether dated competitor evidence is relevant to a particular account. - [Deal risk and signal combination](https://deepline.com/docs/plays/signal-deal-risk): Combine related evidence into one account decision rather than separate touches. ## Concepts and operating boundaries - [Waterfall enrichment](https://deepline.com/docs/features/waterfall-enrichment): Explains ordered provider routing, stopping conditions, and the limits of a waterfall result. - [Bring Your Own Keys](https://deepline.com/docs/features/bring-your-own-keys): Connect a provider key and understand the billing boundary. - [Email sequencer integration](https://deepline.com/docs/features/email-sequencer-integration): Use a Play to prepare and push reviewed leads through a sequencer operation. - [Deepline Skills](https://deepline.com/docs/features/claude-code-skills): Find the packaged operating instructions for a recurring Deepline GTM job. - [Cost control](https://deepline.com/docs/cost-control): Inspect live contracts, pilot representative rows, measure usage, and set a workspace cap before paid work. ## Primary references - [REST API](https://deepline.com/docs/api-reference): Authentication, REST calls, and run inspection. - [CLI and configuration reference](https://deepline.com/docs/sdk-v2/reference): Current command patterns, bindings, identifiers, and operational failures. - [SDK authoring reference](https://deepline.com/docs/sdk-v2/sdk-reference): Generated reference for Play authoring primitives, runtime context, dataset handles, and tool results. - [Runtime API reference](https://deepline.com/docs/sdk-v2/api-reference): Generated HTTP and SDK runtime contract. - [HTTP and Python](https://deepline.com/docs/sdk-v2/http-and-python): Call Plays from Python or another HTTP-capable runtime. - [Semantic layer](https://deepline.com/docs/semantic-layer): Inspectable definitions for warehouse metrics, dimensions, filters, relationships, and funnels. - [Pricing](https://deepline.com/docs/pricing): BYOK, managed credits, billing modes, rate cards, and spend checks. - [Troubleshooting](https://deepline.com/docs/troubleshooting): Resolve common setup, authorization, run, and data-access problems. ## Provider guides Provider guides own connection setup and their supported operation family. Use the live tool contract for exact request fields and price. - [AI Ark](https://deepline.com/docs/providers/ai-ark/guide) - [Google Ads Audiences](https://deepline.com/docs/providers/google-ads-audiences/guide) - [Google Sheets](https://deepline.com/docs/providers/google-sheets/guide) - [LinkedIn Ads Audiences](https://deepline.com/docs/providers/linkedin-ads-audiences/guide) - [Meta Audiences](https://deepline.com/docs/providers/meta-audiences/guide) - [Smartlead](https://deepline.com/docs/providers/smartlead/guide)