Built to be understood. Safe to call.
A read-only discovery API and MCP server for Zephior services and published knowledge. No API key, no customer data and no mutation.
Public REST API
curl "https://zephior.com/api/v1/site?locale=en"curl "https://zephior.com/api/v1/search?q=RFP%20automation&locale=en"MCP
curl -X POST "https://zephior.com/mcp" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"example","version":"1.0.0"}}}'Start with the smallest useful surface
The public Zephior Discovery API lets agents identify Zephior, distinguish Ziva, Zelius, Zeke and Zenith, and search our multilingual publication library. It is not the authenticated product API. It cannot read an account, upload a file, create a project or access customer knowledge. Use the site overview for entity and service questions. Use search only when a task needs a specific published topic, then follow the canonical result URL for the complete authored resource.
Authentication and permissions
The two public discovery operations and the MCP server require no token. They are deliberately read-only and operate only on public website data. Never send credentials, tender files, customer names or private prompts to these interfaces. The Zephior product separately uses OAuth 2.0 and OpenID Connect through auth.zephior.com. Product access is further limited by organization roles and explicit permissions. A valid identity does not grant every product action.
Rate limits and caching
Public discovery clients may send up to 120 requests per 60-second window per client. Responses expose RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and RateLimit-Policy. A 429 response also includes Retry-After. Back off for the stated interval instead of polling continuously. Responses may be cached briefly because their source is published content. The interfaces never start background work.
Typed errors and recovery
API errors use application/problem+json. Every problem contains a stable code, HTTP status, readable detail, instance URL, resolution guidance and documentation URL. Invalid locales, queries and result limits return 400. Unknown versioned routes return 404. Rate-limit exhaustion returns 429. MCP uses JSON-RPC 2.0 errors for protocol failures and tool results with isError for invalid tool arguments.
Versioning and deprecation
The REST surface uses major URL versions beginning with /api/v1. Additive response fields may appear within a major version, so clients should ignore unknown fields. A breaking change receives a new major path. If a public version is retired, Zephior will publish Deprecation and Sunset response headers and document a migration path with at least 180 days notice.
MCP Streamable HTTP
The MCP endpoint exposes get_zephior_overview and search_zephior_resources, plus overview, service-selection and developer-guide resources. The stateless transport at /mcp supports initialize, tools/list, tools/call, resources/list and resources/read. Use MCP for declared schemas and structured output, REST for ordinary HTTP integrations, llms.txt for concise instructions and llms-full.txt for the complete publication index.
Need a product integration?
Tell us the workflow, data boundary and required actions. We will identify the right product or service route.