Digitalyser.io for developers

Digitalyser.io for developers

Connect your platform to Digitalyser.io in under an hour — and prove it before you sign.

Digitalyser.io exposes one contract in two shapes. Agents speak MCP; systems speak REST. Both read the same capability registry, resolve the same permissions, and return the same refusals — so what you learn on one transport carries to the other.

What you can do today

The registry describes what the product knows how to do — audits, content, editorial strategy, brand voice, local visibility. Every capability declares its effect, and that declaration is the whole safety model:

EffectWhat it meansHow you call it
readReturns data. Changes nothing.Directly
proposeComputes a change and returns a diff. Writes nothing yet.Directly, then confirm
writeApplies a diff a human already saw.Never directly — only through the proposal it came from

A write capability is not listed and not callable. That is not an omission: it is the reason an agent cannot modify your data without someone seeing the change first.

Access

The API, the MCP endpoint and outbound webhooks are part of the Enterprise Agency plan. Every page here is public — read it, evaluate it, and try it against the demo project before you talk to anyone.

A read-only demo project — no account, frozen data, real response shapes — is on the way. Until it ships, the quickstart walks the parts that need no credential at all: protocol discovery, and the exact refusal you get without one.

On this page