Cosmo by Humanizing developer resources

All resources below are public, read-only and need no credentials. Base URL: https://cosmo.humanizing.com.

• OpenAPI 3.1 specification/openapi.json — Every operation with a unique operationId, typed parameters and response schemas.
• Cosmo API reference/developers/api — Endpoints, query parameters, examples and the shared JSON error envelope.
• Cosmo MCP server/developers/mcp — Streamable HTTP endpoint that exposes the API as Model Context Protocol tools.
• MCP server manifest/.well-known/mcp.json — Machine-readable description of the MCP endpoint and its tools.
• llms.txt/llms.txt — Condensed product guidance for large language models.
• Sitemap/sitemap.xml — Every public URL on cosmo.humanizing.com.

A read-only JSON API that returns the same product, pricing and company facts the marketing pages show, so agents do not have to scrape HTML. Five operations, all GET, all under /api/v1.

curl -s https://cosmo.humanizing.com/api/v1/products | jq
curl -s "https://cosmo.humanizing.com/api/v1/pricing?interval=monthly" | jq
curl -s https://cosmo.humanizing.com/api/v1/company | jq

Errors always use the same envelope, with a machine-readable error.code and an error.resolution that names the next step. The full reference is on the Cosmo API reference page.

The Model Context Protocol server at https://cosmo.humanizing.com/mcp speaks JSON-RPC 2.0 over the Streamable HTTP transport and exposes 6 read-only tools: list_cosmo_products, get_cosmo_product, get_cosmo_pricing, get_cosmo_company_profile, list_cosmo_pages, get_cosmo_page_markdown.

claude mcp add --transport http cosmo https://cosmo.humanizing.com/mcp

Setup for other clients, the tool schemas and worked examples are on the Cosmo MCP server page.

Every page of this site is available as Markdown from the same URL that serves HTML, following the acceptmarkdown.com convention. Ask for it with an Accept header, or append .md to any path.

curl -sH 'Accept: text/markdown' https://cosmo.humanizing.com/pricing
curl -s https://cosmo.humanizing.com/pricing.md

Markdown responses carry Content-Type: text/markdown; charset=utf-8 and Vary: Accept, Accept-Encoding, so a shared cache cannot hand the HTML variant to a client that asked for Markdown. A request that accepts neither HTML nor Markdown gets a 406 Not Acceptable with a JSON body listing what is supported.

Unknown paths return a real HTTP 404, never a 200 with an app shell. Clients that did not ask for HTML get a short Markdown body pointing at the sitemap, llms.txt and these developer resources, so an agent can recover without a second guess.

curl -s -o /dev/null -w '%{http_code}\n' https://cosmo.humanizing.com/no-such-page
# 404

Setting up an agent, connecting channels and configuring knowledge is covered in the product documentation at docs.cosmo.humanizing.com. Questions about these interfaces: contact@humanizing.com.