Warp, typed and ready to call.

Warp's agent runs real shell commands, so the Deepline CLI works out of the box — call 97+ GTM integrations as typed tools without leaving the terminal.

Agent CLIWarpSupportedCLI · MCP
# Warpconnect
curl -s https://code.deepline.com/api/v2/cli/install | bash
01Connect over the CLI

Connect Warp to Deepline. Same tools as every other surface.

warp
  1. // Step 1
    Install the Deepline CLI
    curl -s https://code.deepline.com/api/v2/cli/install | bash — one binary, no per-provider SDKs.
  2. // Step 2
    Call typed tools
    Run deepline tools call <action> --json {…} — the same typed surface every agent uses, with per-call cost shown before each run.
02What you can do

Same typed tools as Claude Code and Codex

Per-call cost preview and spend caps on every run

No per-provider API keys to wire up

Save results to a Postgres database you own

The provider catalog is identical on every surface. Browse all providers →

03FAQ

Can I use Deepline with Warp? Yes.

Can I use Deepline with Warp?
Yes. Deepline ships as one CLI plus an MCP server, so Warp can call all 97+ GTM integrations as typed tools — over cli · mcp, with no per-provider setup.
How do I connect Deepline to Warp?
Install the Deepline CLI, then Call typed tools. curl -s https://code.deepline.com/api/v2/cli/install | bash — one binary, no per-provider SDKs. Full steps are on this page.
Does Warp need a Deepline-specific plugin or integration?
No. Warp uses the same CLI · MCP surface as every other agent — there's no bespoke connector to build or maintain, and new providers appear automatically.
What can Warp do with Deepline?
Same typed tools as Claude Code and Codex; Per-call cost preview and spend caps on every run; No per-provider API keys to wire up — all priced per call with a spend cap you set, and results saved to a Postgres database you own.
// Try it

Your first GTM job,
shipping in two minutes.

Install once, then prompt Deepline from Claude Code.

// paste in your terminal
Book onboarding →Go to quickstartLive · cached responses across the network