motherduck-rest-api

Name: motherduck-rest-api
Availability: InStock
Author: MotherDuck

Automates Motherduck REST API control-plane workflows for provisioning, configuration, and embedding.

53|3|Updated Mar 30, 2026

Search Tags:#rest api #token management #motherduck #control plane #service accounts #duckling configuration #dive embed

Ready to run

npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-rest-api

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: motherduck-rest-api
Source: https://github.com/motherduckdb/agent-skills/tree/main/plugins/motherduck-skills-claude/skills/motherduck-rest-api
Command: npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-rest-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you safely automate MotherDuck control-plane administration, including service-account provisioning, token lifecycle operations, Duckling configuration, active-account inspection, and Dive embed-session creation.

Core Features & Use Cases

Service-account provisioning & management: Create service accounts and manage their lifecycle through the admin REST API, including destructive delete confirmation.
Access-token lifecycle operations: Create, list metadata, and invalidate admin-controlled tokens while preserving one-time secrets safely.
Duckling configuration & embed sessions: Read and update Duckling instance settings and mint Dive embed sessions for a specific service account.

Quick Start

Use the motherduck-rest-api skill to create a new service account and prepare the token and configuration steps you need to embed a Dive for that account.

Frequently Asked Questions about motherduck-rest-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate MotherDuck service account provisioning via REST API?▼

You can automate MotherDuck service account provisioning by making control-plane REST calls to create service accounts and manage their lifecycle. This requires bearer admin authentication and applies to provisioning operations rather than SQL data plane queries.

What is the difference between MotherDuck control-plane REST API and SQL data plane endpoints?▼

The MotherDuck control-plane REST API handles admin tasks like service-account provisioning, token lifecycle operations, and Duckling configuration. The SQL data plane or query endpoints are for application querying and should not be used for these provisioning and configuration operations.

How do I manage access token lifecycle for MotherDuck service accounts?▼

You manage MotherDuck access token lifecycle through admin-controlled REST API operations to create tokens, list metadata, and invalidate them. One-time secrets are preserved safely while requiring bearer admin authentication for all operations.

Can I configure Duckling instances and create Dive embed sessions through MotherDuck REST API?▼

Yes, you can read and update Duckling instance settings and mint Dive embed sessions for specific service accounts through MotherDuck REST API control-plane calls. This requires a read-before-write posture for configuration changes.

What authentication is required for MotherDuck control-plane REST API workflows?▼

MotherDuck control-plane REST API workflows require bearer admin authentication. Strict error handling surfaces status codes and response bodies, and destructive operations like service account deletion require explicit confirmation.

When should I not use MotherDuck REST API endpoints for database operations?▼

You should not use MotherDuck REST API control-plane endpoints for application querying or SQL data plane operations. These endpoints are intended strictly for provisioning, configuration, active account inspection, and embedding operations.