What does Orrery Team include?

Orrery Team includes shared watchlists, team alert routing, signed webhooks, shared Daily Brief delivery, audit history, and API credits.

Is Orrery Team for trading desks?

Orrery is a research and monitoring layer. It does not execute trades or provide buy/sell recommendations.

Can a team use Orrery with internal bots?

Yes. Teams can use signed webhooks, API credits, and Orrery agent/MCP workflows for internal monitoring.

Orrery for teams

Team monitoring layer

Put the same verification queue in front of every analyst.

Orrery gives teams a shared language for movement, evidence, source status, expiry, and alert history. It is built to reduce confusion before a market price becomes a screenshot in a deck, newsletter, or internal bot.

Team flow

Morning: shared Brief

Daytime: shared watchlists

Events: team alert routing

Afterward: audit and webhook history

Commercial path

Team $499+

Start with a short workflow review: what the team monitors, how alerts route, whether API credits are needed, and what audit history should retain.

Contact sales

Members and roles

Separate owners, admins, analysts, and agent consumers before alerts, keys, or source drops start flowing.

Shared watchlists

Keep researchers aligned around event clusters, resolution risk, and priority markets.

Team alert routing

Route movement, expiry, whale, trust-state, and source-risk alerts to the right inbox or system.

Signed webhooks

Deliver idempotent server-side notifications to internal bots and monitoring systems.

Shared Daily Brief

Route the morning verification queue to a desk inbox, channel, or API workflow.

Team operations contract

audit-ready

Team plans are not a louder dashboard. They are a shared verification workflow: freshness, role-aware routing, delivery audit, API credits, and the same research boundary across humans and agents.

Freshness SLA

Primary monitoring surfaces show current snapshot IDs, source health, and degraded states instead of silently mixing stale and live context.

Evidence: Public Status tracks upstream health, data-quality checks, x402 health, cron freshness, and Kalshi preview state.

Role-aware routing

Team workflows separate watchlist owners, alert recipients, and API/agent consumers so one desk can monitor without turning Orrery into an execution tool.

Evidence: Team routing uses members and roles, plan entitlements, paired identity, signed webhooks, and server-side delivery audit.

Delivery audit

Every server-delivered alert should be reviewable later: what fired, when it fired, where it was sent, and whether delivery succeeded.

Evidence: Email and webhook delivery use retry, idempotency, signature checks, and persisted audit rows.

API credit controls

Agents and internal jobs can use monthly API credits first, then x402 per-call settlement for paid depth when credits are exhausted.

Evidence: Account pages expose personal and team-owned API keys, monthly credit balances, and team workspace ownership after sign-in; B2B API pilots pin rate limits and schema-change notice.

Research boundary

Team plans are built for verification, monitoring, and source review. They do not provide trade execution, picks, or buy/sell recommendations.

Evidence: Public copy, API envelopes, share cards, and alert templates keep the language to observations, verification, and resolution risk.

How the pilot starts

4 steps

Map the shared queue

Pick one team workflow: Daily Brief inbox, shared watchlist, alert routing, or API/agent monitoring.

Choose delivery paths

Decide which events go to email, signed webhook, Telegram/Discord when configured, or account-level audit only.

Set trust gates

Define which transitions matter: market moved, entered resolution-sensitive state, expired unresolved, source pending, or whale flow.

Issue API access

Create personal or team-owned API-credit keys for internal jobs and keep x402 as the explicit paid fallback for deeper intelligence calls.

Good fits

B2B

Research desks tracking market movement and source risk

Newsrooms that need context before citing prediction-market prices

Funds and analysts monitoring event clusters without trade execution

AI-agent teams that need API credits, audit history, and safer tool access

Trust boundary

non-negotiable

Orrery is not a broker, market maker, or trade recommendation tool. Team workflows are designed for research, monitoring, source verification, and auditable alert delivery.