ZooIQ Sign in

API & MCP

ZooIQ exposes its knowledge to people and to AI assistants through a small REST API and a Model Context Protocol server. Public content needs no credential; Internal and Restricted content needs a bearer credential with the matching tier.

Authentication

Send it as Authorization: Bearer <token>. Rate limit: 60 requests per minute per address.

REST endpoints

MethodPathPurpose
GET/api/v1/appsApplication registry
GET/api/v1/docsDocuments in the caller's tier (metadata)
GET/api/v1/docs/{app}/{slug}One document (metadata + sections)
GET/api/v1/search?q=…&limit=…Full-text search
POST/api/v1/ask {"question": "…"}Grounded answer with numbered sources
GET/api/v1/openapi.jsonOpenAPI 3.1 description
GET/healthzLiveness (public)
curl -s "https://iq.zoobd.com/api/v1/search?q=zoo+id+sign+in" | jq '.results[0]'

MCP server

Endpoint https://iq.zoobd.com/mcp — Streamable HTTP transport, stateless JSON-RPC 2.0 (protocol 2025-06-18). Tools: list_applications, search_docs, get_document, ask.

curl -s https://iq.zoobd.com/mcp -H 'content-type: application/json' -H 'accept: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_docs","arguments":{"query":"CalZoo bookings"}}}'

Connecting assistants

Verified so far: the MCP endpoint and REST API pass ZooIQ's own test-suite (JSON-RPC conformance, tier isolation). Connections from Claude, ChatGPT or ZooGPT have not been exercised end-to-end yet and are not claimed to work until they are.

Answer mode

Current mode: Retrieval mode (no AI provider configured). Retrieval mode returns verbatim passages with citations; no text is generated. An administrator can switch to Claude by setting ZOOIQ_AI_PROVIDER=anthropic and ANTHROPIC_API_KEY in the service environment.