Built to be understood. Safe to call.
Read-only APIs and agent tools for published Zephior knowledge. 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"}}}'Go SDK and CLI
go get github.com/Zephior/zephior-agent-toolkit@latest
go install github.com/Zephior/zephior-agent-toolkit/cmd/zephior@latestAgent Skills
npx skills add Zephior/zephior-agent-toolkitStart with the smallest useful surface
The public Zephior Discovery API identifies Zephior, distinguishes Ziva from Zelius, and searches published website content. It does not provide access to customer or private service data.
Tender discovery boundary
The marketing website shows a limited live preview with open or planned records, date-only business fields, and opaque preview references. The website preview transport is not published as an API, MCP tool, WebMCP tool, or reusable integration contract.
Public access boundary
The public Discovery API and documentation MCP require no client token. They are read-only and operate only on published Zephior content. Never send credentials, tender files, customer names, or private prompts to these interfaces.
Rate limits and caching
The public Discovery API applies 120 requests per 60 seconds per client. Respect RateLimit and Retry-After headers. Published discovery responses use explicit cache policies.
Typed errors and recovery
Versioned Discovery API errors use application/problem+json with a stable code, status, readable detail, instance URL, resolution guidance, and documentation URL. MCP uses JSON-RPC 2.0 errors for protocol failures and tool results with isError for invalid arguments.
Versioning and deprecation
The Discovery REST surface uses major URL versions beginning with /api/v1. Additive response fields may appear, so clients should ignore unknown fields. A breaking change receives a new versioned path. If a public version is retired, Zephior will publish Deprecation and Sunset headers and document a migration path with at least 180 days notice.
Published content only
Public Discovery and MCP interfaces return published Zephior pages and resources only. They do not expose private datasets, subscriptions, customer data, or internal service infrastructure.
MCP Streamable HTTP
The public MCP endpoints expose company, service, pricing, and published-resource information for discovery. They do not expose private records or customer data and cannot change application state. Both stateless transports support initialize, tools/list, tools/call, resources/list and resources/read.
Need a product integration?
Tell us the workflow, data boundary and required actions. We will identify the right product or service route.