Shared monitoring for prediction-market teams
Use this for Team, Research Desk, committed API usage, custom categories, alert audit history, webhooks, and invoice billing.
Book a team demo
Leave an email and we will follow up with a short workflow review: what your team monitors, which alerts matter, whether you need API credits, and how audit/history should work.
Prefer direct email? Write to hello@orrery.me.
Team workflow
- Member roles and ownership
- Shared watchlists
- Team alert routing
- Signed webhooks
- Shared Daily Brief inbox
Research Desk
- Alert audit history
- Personal and team-owned API keys
- Custom categories
- Whale / wallet rollups
- Higher API limits
Commercial terms
- Monthly card checkout
- Committed API usage
- Invoice billing
- Private support
Team operations contract
same contract as productSales pilots are scoped around the same operational contract the product exposes: freshness, routing, delivery audit, API credits, and the research-only boundary.
Freshness SLA
Primary monitoring surfaces show current snapshot IDs, source health, and degraded states instead of silently mixing stale and live context.
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.
Delivery audit
Every server-delivered alert should be reviewable later: what fired, when it fired, where it was sent, and whether delivery succeeded.
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.
Research boundary
Team plans are built for verification, monitoring, and source review. They do not provide trade execution, picks, or buy/sell recommendations.
How the pilot starts
workflow first- 01Pick one team workflow: Daily Brief inbox, shared watchlist, alert routing, or API/agent monitoring.
- 02Decide which events go to email, signed webhook, Telegram/Discord when configured, or account-level audit only.
- 03Define which transitions matter: market moved, entered resolution-sensitive state, expired unresolved, source pending, or whale flow.
- 04Create personal or team-owned API-credit keys for internal jobs and keep x402 as the explicit paid fallback for deeper intelligence calls.