Skip to content
Blinkin

Developers

Everything governed.Everything scriptable.

The same governed runtime your team uses in the browser is reachable from your tools — an MCP gateway, a CLI, an embeddable widget, and integrations that meet your stack where it already is.

Overview

Building on Blinkin doesn't mean going around its rules. Whatever your scripts, pipelines and tools publish lands in the same reviewable Inbox, under the same permissions and audit trail, as everything your team does by hand. The API surface is the governance surface.

Feature

An MCP gateway into every Space

Connect any MCP client — hosted or local — to a Space through one Streamable-HTTP endpoint. What your tools publish arrives as reviewable candidates, not as silent writes.

Sample
{
  "mcpServers": {
    "blinkin-space": {
      "url": "https://p2.blinkin.de/mcp/spaces",
      "headers": { "Authorization": "Bearer <machine-token>" }
    }
  }
}
Illustrative — full reference coming soon.

Feature

A CLI for publishing

Publish a file to a stable, versioned URL from a terminal or a CI pipeline — wrap it, share it, promote it — no browser session required.

Sample
$ blinkin-space publish-file report.html --wrap
✓ published — version 3
https://p2.blinkin.de/a/8f3k-quarterly-report
Illustrative — full reference coming soon.

Feature

Embed an agent anywhere

Any published agent runs as a chat widget on any website — same knowledge scopes, same approval gates, same record.

Sample
<script src="https://p2.blinkin.de/embed.js" data-agent="<agent-id>" defer></script>
Illustrative — full reference coming soon.

Feature

Integrations that behave

Microsoft Teams and Blinkwoot service inboxes route conversations into the governed runtime — drafts proposed, humans deciding.

Feature

A public API reference

Coming soon

Full developer documentation is coming. The runtime is contract-first under the hood — the reference will simply say out loud what it already does.

How it works

How it works

  1. Get a machine token

    An org admin issues an org-scoped token. No personal credentials in scripts.

  2. Point your tool at a Space

    MCP endpoint, CLI, or embed — each is scoped to exactly the Spaces you allow.

  3. Publish

    Files, findings, artifacts — from pipelines, agents or cron jobs.

  4. It arrives governed

    Everything lands as reviewable material with a full audit trail. Nothing becomes truth by API.

In practice

In practice

  • A data team's nightly pipeline publishes the morning report to a stable URL — versioned, access-gated, and ready before anyone logs in.

  • An internal research tool posts findings into a Space over MCP; the team reviews them in the same Inbox as everything else.

  • A release pipeline publishes the changelog page on every deploy — version bumped, URL unchanged.

Questions

FAQ

How do tools authenticate?

With org-scoped machine tokens issued by an org admin — no personal credentials in scripts, and revocable in one place.

Can the API write around the review gate?

No. API and MCP publishes arrive as reviewable candidates in the Inbox, exactly like uploads or signals. Nothing becomes Knowledge without a person.

Are there rate limits?

Publishing is governed by the same per-organization limits as the product — countable, visible, and enforced.

When do full API docs arrive?

They're coming soon. Until then, a demo includes the developer walkthrough — the endpoints above are real.

Related

Related

Governance

Governed by design

  • EU hosting

  • Per-organization data isolation

  • Full audit trail

  • Review-gated knowledge

  • Works with any AI model

Next step

Point one script at a Space and watch it arrive governed.

Book a demoSee it live