Cloud

Publishing partner API docs shouldn't become a website project

Integration is done and the partner asks for a link. Finish descriptions locally, verify real calls, and publish versioned hosted docs and MCP from the same workspace, with no doc-tool rollout attached.

Read article →

One spec, two audiences: the human reading your docs and the agent calling your API

Inventory APIs get consumed by developers reading docs and by agents discovering tools. Separate web docs, prompt pastes, and hand-written schemas guarantee drift; one OpenAPI file produces both.

Read article →

We gave a partner’s AI agent 12 of our 47 endpoints. Here is how.

A concrete Cloud walkthrough: publish a managed Streamable HTTP MCP endpoint from one spec, expose twelve operations out of forty-seven, gate agents with a rotated bearer key, inject upstream auth, and pin the partner to an immutable version.

Read article →

Your API already describes the tools your AI agent needs

Hand-writing tool wrappers around existing order and inventory endpoints means maintaining every contract twice. Generate the MCP server from the OpenAPI spec, start with read-only tools, and widen the surface deliberately.

Read article →

From an OpenAPI spec to a hosted MCP server in under five minutes

AI agents need tools, and hand-writing MCP wrappers around your API recreates the exact drift problem OpenAPI solved. Powerduck Cloud turns one spec into hosted docs and a ready-to-use MCP endpoint.

Read article →