Get to the right Deepline resource.
Use email for questions that need a person. For a technical integration, start with the published documentation so your team or agent has the same current contract.
Product and support
Email team@deepline.com for product questions, account help, implementation context, or feedback. Include the relevant workspace or run identifier when it is safe to share; that gives the team a concrete starting point without requiring back-and-forth to identify the issue. Do not include API keys, passwords, or other secrets in email.
If you are evaluating a workflow, describe the outcome you need rather than only naming a provider. Deepline can then point you to the most relevant Play, integration documentation, or setup path. For self-serve implementation, begin with the quickstart and use a small test input before applying a workflow to a full dataset.
Developer and agent integrations
Deepline publishes the Runtime API at a stable base URL and a separate OpenAPI document for programmatic discovery. An MCP client can connect to the remote Streamable HTTP endpoint and follow the standard authorization flow. The llms.txt index, full agent context file, sitemap, and MCP metadata document provide predictable entry points for agents that need to find the right interface before they call it.
Read the API reference before calling an endpoint, inspect a tool schema before executing it, and use the error response’s code and resolution field to decide the next safe step. For help choosing between the CLI, API, and MCP, use the MCP setup guide or email the team with the client and workflow you are integrating.