Developer Documentation

What ships today

This page documents two surfaces that exist and several that do not yet. So it is unambiguous which is which:

REST API

The REST API publishes a curated catalog of 57 tools and runs 13 of them server-side; the rest are browser-only by design and the catalog says which is which. All endpoints return JSON.

Base URL

https://api.devtoolzy.com/devtoolzy/api

Endpoints

Example: Run a tool

curl -X POST https://api.devtoolzy.com/devtoolzy/api/tools/uuid-generator/run \
  -H "Content-Type: application/json" \
  -d '{"version": "v7", "count": 3}'

{
  "ok": true,
  "slug": "uuid-generator",
  "result": [
    "0192f4d0-e2c1-7000-8f0a-3c9b2e4a6d1e",
    "0192f4d0-e2c2-7000-9a1b-4d0c3f5b7e2f",
    "0192f4d0-e2c3-7000-ab2c-5e1d4060bf30"
  ],
  "type": "uuid-v7",
  "count": 3
}

Example: List tools

curl https://api.devtoolzy.com/devtoolzy/api/tools

{
  "tools": [
    {
      "slug": "uuid-generator",
      "name": "UUID Generator",
      "category": "generators",
      "description": "Generate UUID v4 (random) or v7 (time-ordered) identifiers.",
      "serverSide": true
    }
    // ... 56 more tools
  ],
  "count": 57,
  "categories": ["encoders", "formatters", "crypto", "generators", "network", "datetime", "text", "design"],
  "mcp": "https://api.devtoolzy.com/devtoolzy/mcp",
  "docs": "https://devtoolzy.com/mcp"
}

Authentication

The catalog, tool-run, flags, and health endpoints are open — no key. The three endpoints that reach a person or an LLM on our side (/chat, /contact, /subscribe) require an API key and reject a request without one with 401.

Passing the API Key

curl -X POST https://api.devtoolzy.com/devtoolzy/api/chat \
  -H "X-Api-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"messages": [{"role": "user", "content": "What is a UUID v7?"}]}'

MCP Server

The Model Context Protocol (MCP) server exposes nine Dev Tools ! functions as typed tool calls to any MCP-compatible AI client: Claude Desktop, Cursor, Cline, Zed, and more. It is a remote server over Streamable HTTP — there is no package to install and no key to pass.

Connection

// Claude Desktop — ~/Library/Application\ Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "devtoolzy": {
      "url": "https://api.devtoolzy.com/devtoolzy/mcp",
      "transport": "streamable-http"
    }
  }
}

Available MCP tools

Full MCP documentation →

npm CLI

Planned usage

Commands are positional — devtoolzy <command> [subcommand] [input] [flags] — and every text command also reads stdin.

devtoolzy base64 encode "Hello, World!"
devtoolzy base64 decode SGVsbG8sIFdvcmxkIQ==
devtoolzy hash sha256 "hello"
devtoolzy hmac sha256 my-secret "hello"
devtoolzy jwt decode eyJhbGciOiJSUzI1NiJ9...
devtoolzy uuid v4
devtoolzy uuid v7 --count 5
devtoolzy ulid --count 3
devtoolzy format json --indent 2 < data.json
devtoolzy regex test --pattern "\d+" --text "abc 123"
devtoolzy timestamp now
devtoolzy timestamp to-date 1751400060
devtoolzy case kebab "Hello World"
cat file.txt | devtoolzy base64 encode

Planned install

# Once published:
npm install -g @cosyslabs/devtoolzy
devtoolzy --help

# Or without installing:
npx @cosyslabs/devtoolzy uuid v7 --count 5

Want to know the moment it lands? Subscribe with the newsletter form in the footer, or ask us and we will follow up directly.

VS Code Extension

The plan is to bring the tool palette into the editor: run tools from the command palette (Ctrl/Cmd + Shift + P), from a sidebar panel, or from the context menu on a selection.

Planned features

• Tools accessible from the command palette
• Right-click selection → encode/decode/hash/format
• Sidebar panel with categories and search
• Output sent to a new editor tab or replaced inline
• Settings: preferred hash algorithm, UUID version, output format

Subscribe with the newsletter form in the footer to hear when it ships, or tell us what you need from it while it is still being designed.

SDK & Integrations

JavaScript / TypeScript — planned API

Every function takes an input object and resolves to { result, error? }, so the same call shape works for a CLI argument, an HTTP body, or an MCP tool call.

import { base64, hash, jwtDecode, generateUuid } from '@cosyslabs/devtoolzy-core';

// Base64
const { result: encoded } = await base64({ text: 'Hello, World!', mode: 'encode' });
const { result: decoded } = await base64({ text: encoded, mode: 'decode' });

// Hashing
const { result: digest } = await hash({ text: 'Hello, World!', algorithm: 'SHA-256' });

// UUID
const { result: id } = await generateUuid({ version: 'v7', count: 1 });

// JWT — decode only, no signature verification
const { result: claims } = await jwtDecode({ token });

Rate Limits

Every endpoint that costs us something — tool runs, chat, contact, subscribe — is rate-limited per client IP. Exceed a limit and the API returns 429 Too Many Requests with a plain-language message in the detail field.

We are not publishing per-endpoint numbers while the API is in preview: the limits are deployment configuration and would go stale here the first time we tune them. Assume a modest per-minute allowance, back off on a 429, and talk to us before building anything that needs sustained throughput.

Errors

Errors come back with the HTTP status below and a detail string explaining what went wrong:

{
  "detail": "'color-picker' runs entirely in the browser. Use https://devtoolzy.com/tools/design/color-picker instead."
}