zeriq-team
The official Python SDK for the Zeriq Teams API: your AI teammates' knowledge, answers, rooms, action items and meetings, from your own systems.
- Python 3.9+, sync and async clients, built on
httpx. - Results are plain dicts, typed with
TypedDicts generated from the API's OpenAPI spec (zeriq_team.types). - Retries 429, 5xx and network errors with backoff, and honours
Retry-After. Every POST gets anIdempotency-Key, so retries never create anything twice.
pip install zeriq-team
Quick start
from zeriq_team import Zeriq
zq = Zeriq() # reads ZERIQ_TEAM_API_KEY (and ZERIQ_TEAM_BASE_URL)
# Knowledge: upsert by your own id, then search (no AI model, no credits)
zq.knowledge.documents.upsert(external_id="wiki:refunds", title="Refunds", text="…")
hits = zq.knowledge.search(query="refund policy", top_k=5)["data"]
# Ask an AI teammate (no tools unless you allow them)
answer = zq.personas.ask("prs_…", input="Draft a reply to this customer: …")
print(answer["answer"], answer["usage"])
# Rooms: create, post, stream the replies as they arrive, end
room = zq.rooms.create(title="Pricing review", personas=["prs_…"])
sent = zq.rooms.messages.send(room["id"], content="Should we add annual plans?")
for event in zq.rooms.stream(room["id"], run_id=sent["run_id"]): # ends with the run
if event["event"] == "message.created":
print(event["data"]["message"]["content"])
zq.rooms.end(room["id"])
# Lists return the first page; iterate to walk every page
for item in zq.action_items.list(status="open"):
zq.action_items.update(item["id"], external_ref="https://linear.app/…")
Async is the same API, awaited:
from zeriq_team import AsyncZeriq
async with AsyncZeriq() as zq:
answer = await zq.personas.ask("prs_…", input="…")
async for item in zq.action_items.list(status="open"):
...
The default server is https://api.zeriq.app; set base_url (or ZERIQ_TEAM_BASE_URL) to use another environment.
Webhooks
endpoint = zq.webhooks.endpoints.create(url="https://example.com/zeriq", event_types=["action_item.created"])
secret = endpoint["secret"] # shown only now
# In your handler, with the raw request body:
from zeriq_team import webhooks, WebhookVerificationError
event = webhooks.verify(raw_body, headers["Zeriq-Signature"], secret)
if event["type"] == "action_item.created":
...
Errors
Every API error is an APIError with status, code, param and request_id. Subclasses:
InvalidRequestError (400), AuthenticationError (401), CreditsExhaustedError (402 — retry with
allow_downgrade=True), PlanLimitError (402), InsufficientScopeError (403, param is the
missing scope), ToolNotPermittedError (403), NotFoundError (404, also for other workspaces'
objects), RateLimitError (429 after retries), plus APIConnectionError / APITimeoutError.
Results carry the ID too: answer.request_id.
Options
Zeriq(api_key=..., base_url=..., timeout=60.0, max_retries=2, http_client=httpx.Client(...))
zq.rooms.create(title="x", idempotency_key="my-key")
Documentation
- Guide (authentication, scopes, rooms, knowledge sync, webhooks, live room events, MCP): zeriq.app/developers
- API reference: zeriq.app/developers/reference
- Changelog:
CHANGELOG.mdin this package
Metadata
Release files for zeriq-team 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zeriq_team-0.1.1.tar.gz | 22.6 kB | With provenance | Details for zeriq_team-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zeriq_team-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for zeriq_team-0.1.1-py3-none-any.whl |
Total release size: 42.2 kB
Release files / zeriq_team-0.1.1.tar.gz
| Download URL | zeriq_team-0.1.1.tar.gz |
|---|---|
| Size | 22.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b70a171f76d9ae196a4f826487928b8aa3ac5745b88b1f69ea477da68779d9d
|
|
BLAKE2b-256 checksum How to use checksums |
ea2a725e36608e2831eb3628a65533f916de88ef5d3d865d9718a4dae417fa41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logRelease files / zeriq_team-0.1.1-py3-none-any.whl
| Download URL | zeriq_team-0.1.1-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c07bc4165497c805c8536c156f69988738eb9ea428be8edbb67a8484d76031d
|
|
BLAKE2b-256 checksum How to use checksums |
be24c7c0925d3e7b4c869a7c1a1873825e4bbddc08260ed9dec9855536c34f33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logSecurity for zeriq-team 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for zeriq_team-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.