Sales

Request early access to the B2B API pilot

Use this for committed API usage, API-credit keys, x402 settlement, usage reporting, schema-change notices, support expectations, and safe agent workflows. Access is manually reviewed before the first cohort is entitled.

API pilotResearch, not trading advice

Scope an API pilot

Leave an email and we will map the first agent/API workflow: which endpoints matter, expected volume, credit-pack size, x402 fallback, reporting, support path, and manual entitlement scope.

Prefer direct email? Write to hello@orrery.me.

API workflow

  • Free discovery API
  • Personal and team-owned API keys
  • x402 per-call fallback
  • Usage and receipt reporting

Pilot contract

  • Member roles and ownership
  • Freshness expectations
  • Rate-limit contract
  • Schema-change notice
  • No trade advice boundary

Commercial terms

  • Monthly card checkout
  • Committed API usage
  • Invoice billing
  • Private support

Team operations contract

same contract as product

Sales 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
  1. 01Pick one team workflow: Daily Brief inbox, shared watchlist, alert routing, or API/agent monitoring.
  2. 02Decide which events go to email, signed webhook, Telegram/Discord when configured, or account-level audit only.
  3. 03Define which transitions matter: market moved, entered resolution-sensitive state, expired unresolved, source pending, or whale flow.
  4. 04Create personal or team-owned API-credit keys for internal jobs and keep x402 as the explicit paid fallback for deeper intelligence calls.
Contact sales - Orrery | Orrery