Developers

One contract.
Many surfaces.

Every Dials surface — REST, CLI, MCP, webhooks — reaches the same scoped paths. Build against the API once and your agent, your CLI, and your dashboard all behave the same way.

Read the APIPlatform status

Same path, three ways

One call.
Three ways in.

The same scoped path runs under the dashboard, the CLI, and the MCP tool. Real filters, real validation, real usage event.

  • · Versioned REST
  • · Typed SDKs
  • · `dials` CLI
  • · MCP server
HTTP
GET /api/numbers/search
  ?areaCode=512
  &exchangeCode=555
  &localCallingArea=true
  &limit=25
CLI
dials numbers search \
  --area-code 512 \
  --exchange-code 555 \
  --local-calling-area \
  --limit 25
MCP
{
  "tool": "dials.numbers.search",
  "arguments": {
    "areaCode": "512",
    "exchangeCode": "555",
    "localCallingArea": true,
    "limit": 25
  }
}

All developer surfaces

Build it how you build.

REST API

HTTP, signed and scoped.

Versioned endpoints. Per-call usage events. Mock mode by default. The way humans, CLIs, and agents all reach Dials.

Read →
SDKs

TypeScript, Rust, more.

Typed clients in TypeScript, Rust, Python, Go, Swift, and Kotlin. One contract, six idioms.

Read →
Command line

`dials` from your terminal.

The same scoped paths the console uses, with bash-style flags and shell-friendly output.

Read →
MCP server

Native for agents.

The Dials MCP server exposes every verified path to any MCP-aware agent under the same scope model.

Read →
Webhooks

Signed events.

HMAC-signed, replay-protected event delivery with retry, DLQ, and per-tenant secrets.

Read →
Changelog

Versions you can read.

Every API change recorded with a date, a version bump, and a migration note when one is required.

Read →

Run the smoke flow.

Pull the SDK, run the smoke command, and watch the same audited path light up the console, the ledger, and the CLI.

Open the consoleTalk to us