Skip to main content
Beacon reads the systems a recurring-revenue company already runs and maintains one agreed set of figures across them. This site is the reference: what Beacon connects to, what each figure means, and where its limits are.

Connect your tools

Sources Beacon reads, what each one enables, how connections are authenticated, and what happens when one is missing.

Boundaries

Read-only scopes, credential and permission handling, what outside readers can see, and how access is revoked.

Data model

The objects Beacon publishes, the values on each one, and the doors every value travels through.

Definitions

What each figure means, how it is calculated, what it is built from, and what it is not.

​
Published, not yet served

API reference · MCP tools Both publish a contract ahead of the interface that will serve it. The names, shapes and availability are fixed, so anything written against them will not have to change when they arrive — but nothing on either page can be called today, and each says so before its contract.

​
Not yet published

Event catalogue · fields Beacon writes back · task guides. Pages appear here as the surfaces they describe ship. Where a page publishes the shape of a value before the interface that serves it exists, it says so in the first paragraph.