API & integrations¶

Dezycro exposes its functionality two ways:

	MCP server	Public REST API
For	AI clients (Claude Code, Cursor, custom MCP clients)	Programmatic access from any HTTP client
Transport	Streamable HTTP (MCP protocol)	Standard JSON over HTTPS
Endpoint	`https://mcp.dezycro.ai/mcp`	`https://api.dezycro.ai/api/v1/...`
Auth	`Authorization: Bearer dzy_...` (PAT)	`Authorization: Bearer dzy_...` (PAT)
Best for	Conversational tooling, agent workflows	CI scripts, custom integrations, dashboards

Both surfaces are backed by the same services and the same permission model — your PAT's workspace roles apply equally.

Quick start¶

MCP¶

claude mcp add dezycro \
  --transport http \
  --url https://mcp.dezycro.ai/mcp \
  --header "Authorization: Bearer dzy_..."

See the MCP server reference.

REST¶

curl -H "Authorization: Bearer dzy_..." \
  https://api.dezycro.ai/api/v1/workspaces

OpenAPI spec is available under the PUBLIC tag at https://api.dezycro.ai/v3/api-docs — import into Postman / Insomnia or feed to openapi-generator for any major language.

Auth¶

PATs are bearer tokens prefixed with dzy_. Create one from Settings → Personal Access Tokens in the web app. Pass on every request:

Authorization: Bearer dzy_<your-token>

PATs inherit your workspace role on each call. Tenant-level operations (member management, billing) require Tenant Owner. Full details: Authentication & access.

Rate limits¶

Tier	Public API + MCP requests / minute
Free	60
Pro	600
Team	2,000
Enterprise	Custom

429 responses include a Retry-After header. MCP returns rate-limit failures as MCP error responses with code: -32603.

Webhooks¶

Dezycro can POST event notifications for workbook + verifier events. Configure under Settings → Webhooks.

Events: verifier.run.completed, feature.lifecycle.transitioned, journey.status.changed, intent_violation.recorded, coverage.gap.detected.

Each request includes an X-Dezycro-Signature HMAC header so you can verify origin. Failed deliveries retry with exponential backoff for up to 24 hours.

SDKs¶

No official SDKs yet. The MCP server's tool schemas auto-generate client signatures in MCP-compatible IDEs (Claude Code, Cursor). For REST, generate a client from the OpenAPI spec.