Catalog compatibility view

Forty-eight listings, labelled by maturity.

Five listings are live in BearScope. Forty-three are delivered only through managed early access. A listing is not proof of public package availability, self-service installation, vendor endorsement, or feature parity. The marketplace is the canonical catalog.

48Catalog listings
30Connectors
8Operators
5 / 43Live / managed
Reference recipes

Illustrative cross-domain plans, not live installs.

See an example →
Weather × Facilities awareness

Review weather alongside facilities procedures.

See the plan → Grid × HVAC

Model a grid-aware HVAC plan.

See the plan → Air quality × Ventilation

Model an air-quality review plan.

See the plan → Seismic × Emergency awareness

Review public seismic data with human procedures.

See the plan →
Category

Click any row for details

// any system you run → a governed connector
defineConnector({
  id:         "your-system",
  capability: "sense.orders",
  auth:       oauth("…"),
  tools:      [ pull, watch, act ],
})
// single-flight · idempotent · fail-closed
Don't see your system?

Request a managed connector review.

A system being readable does not make a connector available or safe to deploy. Tell us the source, tenant boundary, permissions, action surface, duplicate behavior, and recovery limits. We will separate live capability from early-access work.

  • / Current source, tenant, credential, and action boundaries
  • / Reference contract review; no public SDK package is offered
  • / Deployment-specific validation, duplicate controls, records, and recovery limits
Request managed review → Review the reference contract
How a connection works

A reference connection contract. Validate every deployment.

01

Sense

The reference contract attaches source and tenant context to events. Live BearScope paths use governed real data; a new connector must prove its own mapping and fallback behavior.

02

Reason

The generalized design separates model proposals from deterministic checks. Whether an action is allowed, reviewed, or blocked depends on the implemented product path and policy.

03

Act

Single-flight and idempotency keys are intended to reduce duplicate effects. Supported paths can record actions; downstream reversibility and isolation must be verified for the deployment.

This catalog is free to browse; the platform is not a public free entitlement. There is no self-service install or checkout. Managed deployment scope and rates are confirmed in writing. See the indicative planning model on pricing.