# For AI and machines

> Machine-readable IZT Blink facts for AI assistants and agents: llms.txt, llms-full.txt, sitemap.xml, /api/facts.json, the OpenAPI description and the MCP endpoint.

Canonical page: https://blink.izt.app/for-ai · Markdown: https://blink.izt.app/for-ai.md

Ask an AI assistant about IZT Blink and you want a correct answer. This site gives assistants the same verified facts people read here: one-file summaries (llms.txt, llms-full.txt), Markdown versions of every page, a facts and search feed, and an MCP server your assistant can connect to. Everything is read-only and free to use, with no sign-up. These endpoints describe the product; they do not connect to or control any session.

Every page on this site has a Markdown twin (append `.md` to the path; the home page is `/index.md`), and page URLs return Markdown when the request prefers `Accept: text/markdown`.

## Endpoints

### llms.txt

`GET /llms.txt` · text/plain (Markdown)

A short Markdown index for language models in the llmstxt.org format: summary, key facts (Support and Access, organizations, plans, cloud or on-premises) and links to every page, feature and the customer documentation.

```sh
curl https://blink.izt.app/llms.txt
```

### llms-full.txt

`GET /llms-full.txt` · text/plain (Markdown)

The whole site as one Markdown document: product, Support and Access start to finish, every feature, MSPs, plans, security and privacy, the full FAQ and what not to claim about Blink.

```sh
curl https://blink.izt.app/llms-full.txt
```

### Markdown twins

`GET /<page>.md` · text/markdown

Any page as Markdown: add .md to the path (/features.md, /features/remote-terminal.md; the home page is /index.md). Page URLs also return Markdown when the request prefers Accept: text/markdown.

```sh
curl https://blink.izt.app/security.md
curl -H 'Accept: text/markdown' https://blink.izt.app/faq
```

### Facts JSON

`GET /api/facts.json` · application/json

The full content registry as JSON (product, Support and Access modes, supported systems, flow, features, plans, MSP, security, FAQ, docs links, what Blink does not claim, pages) with schema_version and updated date. CORS-enabled.

```sh
curl -s https://blink.izt.app/api/facts.json | jq '.features.items[].name'
```

### Search JSON

`GET /api/search.json?q=` · application/json

Keyword search over features, FAQ, security statements, the glossary and plans. Parameters: q (required), limit (1 to 50, default 10) and kinds (comma list of feature, faq, security, glossary, plan). Results link to the exact section. CORS-enabled.

```sh
curl 'https://blink.izt.app/api/search.json?q=unattended+access&limit=5'
```

### Ask Blink

`POST /api/ask` · text/event-stream

The Ask Blink assistant. POST the conversation as {messages:[{role, content}]} and read the answer as server-sent events. GET returns whether it is available and its limits. Rate-limited; when the assistant is not configured it answers 503 with search results instead.

```sh
curl -N https://blink.izt.app/api/ask \
  -H 'content-type: application/json' \
  -d '{"messages":[{"role":"user","content":"Can we deploy the Access agent from our RMM?"}]}'
```

### MCP server

`POST /mcp` · application/json

A Model Context Protocol endpoint (Streamable HTTP), so AI assistants can search and read the Blink facts as tools. Connect an MCP client to it rather than calling it by hand.

```sh
claude mcp add --transport http blink https://blink.izt.app/mcp
```

### OpenAPI

`GET /openapi.json` · application/json

An OpenAPI 3.1 description of the facts, search, Ask Blink and MCP endpoints.

```sh
curl https://blink.izt.app/openapi.json
```

### Sitemap

`GET /sitemap.xml` · application/xml

Every page and feature page, with last-modified dates.

```sh
curl https://blink.izt.app/sitemap.xml
```

## MCP client configuration

For clients that read an `mcpServers` configuration with HTTP servers, such as a project `.mcp.json` in Claude Code:

```json
{
  "mcpServers": {
    "blink": {
      "type": "http",
      "url": "https://blink.izt.app/mcp"
    }
  }
}
```

Or from the Claude Code command line:

```sh
claude mcp add --transport http blink https://blink.izt.app/mcp
```

In Claude Desktop or claude.ai, add it as a custom connector with the URL https://blink.izt.app/mcp.

Tools (all read-only):

- `search_blink`: keyword search across every verified page
- `get_overview`: what Blink is, who it is for, Support and Access, supported systems, availability and the support code
- `list_features` / `get_feature`: features, filterable by session kind, computer and plan
- `get_plans`: Blink Core and Blink Pro prices per technician (annual and monthly), cloud or on-premises terms, unlimited Access devices, the Blink View add-on and the comparison
- `get_faq`: verified answers to common questions
- `get_security_facts`: security and privacy, as the customer and the buyer see it
- `check_claim`: checks a sentence about Blink against the facts

## Ask Blink

People can ask questions at https://blink.izt.app/ask. Answers come from the same registry as these endpoints.

## What Blink does not claim

IZT Blink is remote support and remote access, available in the cloud or on-premises. Describe it only with what this site says; these are the topics where it is most often described wrongly.

- **Prices.** Prices are only those on the pricing page, in US dollars per technician per month. There is no free tier, money-back offer or other discount.
- **Trials.** There is no self-serve sign-up or checkout. Start a trial is a request form, and IZT sets the trial up with you.
- **Seats and devices.** Plans are priced per technician seat, with no seats included free. Access devices are unlimited on both plans.
- **Cloud or on-premises.** Blink Core is cloud only. On-premises is Blink Pro only, billed annually.
- **Blink Core.** Blink Core differs from Blink Pro only in session recording, terminal history, session timeline and Blink Notify.
- **Add-ons.** Blink View is the only add-on today.
- **Blink Notify.** Blink Notify is part of Blink Pro, not Blink Core, and reaches Windows Access devices only, not Macs or support sessions. Messages are plain text with no clickable links or templates, and the sender cannot type a sender name.
- **Customers.** No customer names, logos, testimonials, counts, ratings or awards are published.
- **Unattended Access.** Unattended Access is for Windows 10 or later, 64-bit. Macs, Linux, ChromeOS, phones and tablets are not Access devices.
- **Attended Support.** Support covers Windows PCs and Macs. Linux, ChromeOS, phones and tablets are not supported, and Blink View shows a phone’s camera without controlling the phone.
- **System versions.** Supported systems are Windows 10 or later (64-bit, x64) and macOS 12.3 or later.
- **Mac.** On a Mac the customer sees a menu bar item rather than a banner. Run as admin, Install Access, Backstage, reboot, Safe Mode and sending files to the technician are Windows only.
- **Technician apps.** Technicians work in a web browser; there are no technician mobile or desktop apps.
- **Compliance.** Blink claims no compliance certifications or badges. It is available in the cloud or on-premises; talk to us about the option that fits your policies.
- **Encryption.** Blink does not publish encryption schemes. Type text and admin credentials are protected before they leave the browser and never stored, and secret messages are shown once and never kept.
- **Performance.** No latency, frame rate, bandwidth, connect-time, uptime, service-level or data-location figures are published.
- **Sign-in.** Every person has their own Blink account with a password and a passkey or authenticator app code. There is no company directory sign-in and no text-message or email codes.
- **Two-factor.** Two-factor is always on for every account and cannot be turned off.
- **Invites.** Invite links are copied and sent by your team. Instance owners reset sign-ins; there is no self-service password reset.
- **Users.** Users are disabled rather than removed. Disabling signs them out everywhere and frees their seat.
- **Owner rights.** Terminal and full-control Backstage rights are granted on purpose, never by instance ownership alone.
- **Activity and alerts.** Activity is viewed in the console. Owner alerts show in the console and can go to one webhook; there is no export or alert email.
- **Typing.** Logs record what happened, not what was typed or copied.
- **IZT.** IZT receives only diagnostics your team chooses to send, and gets no access to your Blink.
- **IP and country rules.** Rules cover the console and each organization’s Access devices. Customers joining Support are never restricted.
- **Opening the tool.** Windows or macOS may show a warning when the customer opens the download; the customer confirms it.
- **Mac permissions.** Only the person at the Mac can grant Blink’s permissions.
- **Presence.** Support is attended and started by the customer. Access is unattended access to the computers you manage, without a banner or approval prompt.
- **Recording.** Session recording is part of Blink Pro, not Blink Core, and has no per-session off switch.
- **Support codes.** Support codes are nine digits by default, work once, expire after 15 minutes if unused, and work only on the Blink address that created them.
- **Dropped connections.** A support session waits up to 2 minutes for a dropped computer to come back.
- **Chat.** Chat is text only. In a Support session either side can open it; on an Access device only the technician starts it and the user replies. Messages to an offline device are not kept for later, and there are no calls.
- **Audio.** The technician hears the computer’s sound, one way only. There is no voice channel.
- **Clipboard.** The shared clipboard carries text only, up to 64 KB at a time.
- **Files.** File transfer has no remote file browser: technicians send files to the computer, and in Windows support sessions files come back only when the customer chooses Send file.
- **Admin rights.** Run as admin always needs the customer to click Yes.
- **Backstage.** Backstage is in Beta, on Windows Access devices only.
- **Tools.** Blink does not offer screen blanking, annotation, remote printing, Wake-on-LAN, patching, device health monitoring or inventory.
- **Install and networks.** The Access agent installs with a signed installer, a script or from a support session. Blink needs a direct secure web connection.
- **RMM tools.** RMM support is step-by-step guides and ready-made scripts for 24 tools, not built-in connectors.
- **Updates.** Agents update themselves and roll back automatically if a new version keeps failing; no further guarantees are made.
- **Revoke.** Revoking a device stops its access at once but does not remove the agent from the computer.
- **Licenses.** A lapsed license or a reached limit never disconnects devices already enrolled.
- **Protection figures.** Guessing protection, fleet limits and similar safeguards are described without figures.

## Get started

- Start a trial: https://blink.izt.app/trial (a short request form; there is no self-serve sign-up, and we set the trial up with you in the cloud or on-premises)
- Talk to us: https://blink.izt.app/contact
- See plans and pricing: https://blink.izt.app/pricing
- Customers with a code: https://blink.izt.app/join
- Documentation: https://docs.blink.izt.app

---

IZT Blink is made by IZT Apps and is available in the cloud or on-premises. Start a trial: https://blink.izt.app/trial · Talk to us: https://blink.izt.app/contact · Documentation: https://docs.blink.izt.app
Everything about the product: https://blink.izt.app/llms-full.txt · Index: https://blink.izt.app/llms.txt · JSON: https://blink.izt.app/api/facts.json