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 our multilingual publication library. It is not the authenticated Ziva product API. It cannot read an account, upload a file, create a project, access customer knowledge, search the Tender Universe dataset, or mutate product state.
Tender discovery boundary
The marketing website shows a limited live preview with open or planned records, date-only business fields, and opaque preview references. Tender search, result details, history, and product workflows require an authenticated Ziva account. The website preview transport is not published as an API, MCP tool, WebMCP tool, or reusable integration contract.
Authentication and permissions
The public Discovery and documentation MCP operations require no client token. They are deliberately read-only and operate only on published Zephior content. Never send credentials, tender files, customer names, or private prompts to these interfaces. Ziva uses OAuth 2.0 and OpenID Connect through auth.zephior.com, plus organization roles, explicit permissions, and subscription checks. A valid identity does not grant every product action.
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. Ziva product limits and cache behavior are part of the authenticated product contract, not this public API.
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.
Tender access, agents, and MCP
Tender discovery authenticates through Ziva and its access-policy plane. Public agents never connect directly to Tender Universe PostgreSQL, Qdrant, NATS, or its private delivery API. Public Discovery and MCP interfaces return published Zephior content only, never Tender Universe, subscription, or customer data.
MCP Streamable HTTP
The public documentation MCP endpoint exposes company and published-resource tools. A separate product-decision MCP surface compares published Ziva capacity checkpoints and Zephior service boundaries. Neither exposes tender search or Tender Universe records. 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.