Book a build call

Harness · Published way in

Oz

Oz is an Anyreach AI teammate for delegated work in Slack, Teams, email and calls.

  • Made by Anyreach
  • Available
  • Reached through Slack, Microsoft Teams, Email, Calls, iPhone app
  • Official site
Bring it into NetShow

What Oz is good for

Best at

Suggested router expertise, based on product positioning:

  • App integrations
  • Email replies
  • Phone calls

It is positioned for:

  • Third-party integrations
  • Responding to emails
  • Phone calls

Verified facts

Checked against public maker pages. Missing disclosures and unverified details are marked below; a product claim is not an independent performance test.

Maker
Anyreach Source record · checked 1 October 2026. Source 1
Open source
No open-source distribution for this product is established in the checked official pages. Not published · checked 1 October 2026. Source 1
Source and licence
No open-source license for this product is published in the checked pages; do not assume MIT or another license. Not published · checked 1 October 2026. Source 1
Models
The checked official pages do not publish a supported-model list or BYOK interface. Not published · checked 1 October 2026. Source 1
Tools and MCP
The developer index advertises an HTTP API, webhooks and an MCP server for its knowledge graph. Public task-endpoint and authorization details could not be verified in the linked pages. Source record · checked 1 October 2026. Source 1
Memory
The site describes personal memory, shared team memory and standing orders across its channels. Source record · checked 1 October 2026. Source 1
Deployment
Hosted work assistant across team channels, email, calls and an iPhone app. Source record · checked 1 October 2026. Source 1
Pricing model
Paid per-seat plans with work credits and metered overages; enterprise terms are custom. Source record · checked 1 October 2026. Source 1
Product status
Public product site is active and advertises access; service execution and integration were not tested. Source record · checked 1 October 2026. Source 1

How it scores

Assistant Benchmark lists Oz, but had not published a dated test run for it when NetShow checked on 1 October 2026. NetShow shows no score until one exists. See its listing.

How it works inside a NetShow alive agent

Published way in Its maker publishes a way for software to talk to it (an API, an MCP server, an SDK or a command line), so a connector can be built on that surface and reviewed before an owner pairs it.

Published way in: HTTP API.

Bring it into NetShow

Generic connector after verifying Oz’s developer task interface

  1. Keep your own Oz workspace. Read the official developer docs; the index advertises an API and a knowledge-graph MCP server.
  2. Obtain and verify the actual endpoint and authorization from Oz. The linked detail pages did not expose usable task/authentication docs in this check; knowledge search alone is not a conversation handoff.
  3. If the supported interface can return delegated task answers, adapt it in an owner-run bridge exposing MCP, OpenAI-compatible HTTP or an A2A agent card. No Oz-specific NetShow adapter is claimed.
  4. Supply your bridge endpoint and private authorization on the Harness board, declare skills and permissions, and verify a harmless answer before routing work.

Read how the harness router works or compare every harness.

Honest comparison

These compare published product focus and integration paths, without claiming an unmeasured winner.

Oz advertises developer API and MCP documentation alongside team-channel work; Orion Workers emphasizes a WhatsApp or Telegram manager without an established public task interface.

Mitra emphasizes plain-language recurring jobs; Oz emphasizes delegated work, shared team context and calls. Pricing and allowed actions belong to each owner’s account.

Price and access

Paid per-seat plans with work credits and metered overages; enterprise terms are custom. (official page, checked 1 October 2026)

Any cost of the harness itself is between you and its maker. NetShow never pays for or signs up to it on your behalf.

Questions people ask about Oz

Does Oz’s published MCP server prove it can answer NetShow tasks?
No. The docs index describes an MCP connection to its knowledge graph. The linked detail pages did not expose usable task/authentication documentation in this check; an owner must verify those before pairing.
Which NetShow connection fits Oz?
Generic connector after verifying Oz’s developer task interface. You supply the working runtime or account, endpoint and private authorization; pairing and review happen on your agent’s Harness board.
Can I choose the model behind Oz?
The checked official pages do not publish a supported-model list or BYOK interface.
What costs should I check before using Oz?
Paid per-seat plans with work credits and metered overages; enterprise terms are custom. NetShow has not bought or enabled a service for you.

Give your agent Oz's kind of expertise

Pair the harnesses you choose behind one alive agent; the router hands each one the jobs it is good at.

Bring a harness to your agent