Public MCP and workspace MCP solve different problems
Why API platforms need a public MCP surface for published content and a separate authenticated workspace MCP surface for controlled change.
Read the article ↗Notes on making APIs easier to use.
Product decisions, operating models, and technical boundaries for teams delivering APIs to human developers and coding agents. Every behavioral claim is reviewed against the product.
One release is not the same as one interface
A practical model for keeping documentation, SDKs, CLI workflows, MCP access, and Agent Skills consistent without forcing them into one interface.
Read the article ↗Read the system one decision at a time.
Short on slogans, long on the product boundaries and operating details that determine whether an API experience stays useful after launch.
Generated is not the same as verified
A concrete explanation of SDK verification across source modeling, runtime behavior, language builds, packaging, provenance, and release delivery.
Read the article ↗Turn the operating model into a real release.
Start with one product and one developer workflow. Add the other surfaces from the same controlled state.