Production onboarding for verified market intelligence
A practical contract for teams and agents: API keys, monthly credit packs, x402 fallback, usage telemetry, rate limits, SLA expectations, and safety boundaries.
Personal and team-owned keys
managedIssue personal API keys for individual agents, team-owned keys for shared desks, and API-credit keys for managed allowance. Keys spend monthly plan or credit-pack allowance first, then fall back to x402 when credits run out.
x402 per-call settlement
account-lessPaid routes return HTTP 402 with a Base USDC quote. Replay the same request with X-PAYMENT and a verified proof to receive the paid envelope.
B2B credit packs
contractAgent Starter, Agent Pro, Agent Team, and Enterprise API packs set monthly usage allowance, support expectations, and rollout controls.
B2B API contract
SLA / rate limitsFreshness
Primary live snapshots target <=5 minutes when upstream probes are healthy.
Rate limits
Free discovery is deliberately capped; paid API-key and x402 calls use endpoint-level limits and return 429/rate_limited when throttled.
Schema stability
All paid endpoints use meta.schema_version=orrery.envelope.v1. Breaking envelope changes require a documented version bump.
Payment states
Public contract: free, settled, missing, rate_limited. Paid data is only returned after settled API credit or x402 proof.
Data boundary
Orrery returns verification context, source state, and resolution risk. It never returns buy/sell recommendations.
Privacy
Usage counters do not store payer addresses, payment proofs, request bodies, IPs, or public user identifiers.
Soft-launch access is not a formal uptime SLA. Enterprise contracts can pin committed capacity, support window, incident notification, retention, and schema-change notice terms.
Team/API alignment contract
shared operational languageThe B2B API is not a separate promise from the team product. The same operating contract governs human desks, internal bots, and agent workflows.
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.
Onboarding checklist
pilot ready- 01Pick the first workload: Brief, attention queue, market decision, resolution risk, share cards, or wallet context.
- 02Start with the free discovery API and OpenAPI spec so the agent can bind without payment friction.
- 03Create an API key for managed monthly credits, or wire an x402 payer for account-less settlement.
- 04For team pilots, assign member roles before creating team-owned keys so API usage and source-drop audit map back to the right workspace.
- 05Run the first paid endpoint until meta.payment_status returns settled.
- 06Check usage counters, receipts, and status pages before increasing volume.
- 07Agree a B2B cap: monthly credits, expected QPS, support path, and schema-change notification channel.
Proof before scale
settlement gateA pilot is production-ready only after one paid endpoint returns a 200 envelope with payment_status: settled, usage counters increment, and the request can be cited from admin telemetry or a redacted receipt.