Skip to main content
The pages an engineering team reaches first. There is no public API or MCP tool catalogue yet, so everything below is about what Beacon reads from your systems, what it will never do to them, and what it writes back.

Connect your tools

What Beacon reads, what each connection unlocks, and what connecting actually involves.

Connector catalogue

Every source Beacon reads, how each one connects, how often it refreshes, and whether it can write.

Boundaries

What Beacon will never do with your systems — each limit with the mechanism that enforces it and how to check it.

When a source is missing

What billing being down does, what any other missing source does, and what a refused read returns.

Access and grants

What a reader grant states, how outside software connects, and what a request outside a grant returns.

Data model

The objects Beacon publishes and the values on each one, with the account and deal objects in full.

Troubleshooting

What a figure that is missing, switched off, refused or stale is telling you, and what to do about it.