Public API and MCP

Read published profiles anonymously within daily limits, or use a verified Customer account to create a public-read API key. Keys cannot manage profiles or access Owner or Admin operations.

• Backend API reference
• OpenAPI specification — check operation implementation status.
• MCP Streamable HTTP: https://api.zynor.io/mcp

REST and authentication

API root: https://api.zynor.io/api/v1. Read cities, categories, /portals/search, and /portals/by-slug/SLUG. Send an API key with Authorization: Bearer KEY. Handle 429 and Retry-After; hidden profiles return 404.

MCP tools

The POST endpoint supports search_providers, get_provider, list_cities, and list_categories. Use an MCP Streamable HTTP client with the same public-read authentication. The endpoint is outside /api/v1. Availability on the production host depends on deployment.

Profiles also have a Markdown representation at /p/SLUG.md. Claimed status indicates maintenance access, not endorsement.