Capitao.Consulting developer portal

Quickstart

No API key is required for the public service catalog or MCP tools. These interfaces are informational and read-only: they do not create projects, send messages, book meetings, or expose private customer data.

curl https://capitao.consulting/api/v1/services
curl https://capitao.consulting/openapi.json

Public REST API

GET /api/v1/services returns the current public AI consulting service catalog. Pass locale=pt, en, es, or fr to select a language. Errors use RFC 9457-style problem details with a stable code and a recovery hint.

The complete OpenAPI 3.1 contract includes a unique operationId, typed parameters, response schemas, examples, and the versioning policy. Versioned paths remain compatible within v1; breaking changes require a new major path.

• OpenAPI: https://capitao.consulting/openapi.json
• API catalog: https://capitao.consulting/.well-known/api-catalog
• Authentication: none for documented read-only operations
• Sandbox: the production read-only endpoint is safe for exploratory requests

Versioning and deprecation

Stable API versions use the major version in the URL path. Additive, backward-compatible fields may be introduced within v1; breaking changes require a new major path.

A deprecated operation is announced at least 90 days before removal in this developer portal and the OpenAPI description. During that period its responses include Deprecation, Sunset, and Link headers identifying the retirement date and replacement documentation.

Model Context Protocol

The Capitao.Consulting MCP server exposes read-only tools for listing AI consulting services and retrieving public contact details. It uses Streamable HTTP and requires no credentials.

• Server card: https://capitao.consulting/.well-known/mcp
• Registry manifest: https://capitao.consulting/server.json
• AI catalog: https://capitao.consulting/.well-known/ai-catalog.json

MCP endpoint: https://capitao.consulting/mcp

Command line

The zero-install Capitao.Consulting CLI is a small POSIX shell client for the public service catalog. Download it before running so the command remains inspectable.

curl -fsSL https://capitao.consulting/cli -o /tmp/capitao
sh /tmp/capitao services en
sh /tmp/capitao contact

When to use these interfaces

• Use the REST API when software needs a typed, cacheable service catalog.
• Use MCP when an AI agent needs to discover services or public contact routes as tools.
• Use the website assistant or contact page when a person wants to discuss a project, assess fit, or arrange a discovery conversation.
• Do not use these public interfaces for private proposals, customer data, admin operations, or assumptions about capabilities not listed in the returned data.