AION Browser
region eu-pl Request access
Agent browser infrastructure · EU self-host

AION
{{ goldTitle }}

Stealth browser for AI agents — an eye that sees on your behalf, measures what blocks you, then calls the web like an API.

MCP + Clearcote Chromium + durable Action Packs for services without a usable API.

Przeglądarka stealth dla agentów AI — evidence-first + Action Packs.
{{ glyphRing }}
udjat · sight, not surveillanceeye restored · now guards
{{ w.tag }}

{{ w.title }}

{{ w.body }}

  • {{ pt }}
01 — Architecture

Separation architecture

Your agent runtime stays where it runs. The browser, the fingerprint and the egress live on AION, in the EU, behind one authenticated endpoint.

Every hop is attributable: token → session → profile → proxy → target, with the evidence report attached to the run.

{{ l.n }} {{ l.title }}

{{ l.body }}

{{ ch }}
02 — Connect

How agents connect

One remote endpoint over HTTPS with a bearer token. The same transport carries browser tools and pack.invoke, so an agent learns one surface.

{{ codeText }}
browser.aionflow.pl/mcp/ · /health · bearer per tenant
MCP tool surface
{{ tl.sig }} {{ tl.body }}
03 — Evidence

What we measure

Identity, geo and TLS are asserted per session, then the block is classified. You get a verdict — POLICY or STACK — instead of a success percentage.

session pl-warsaw-01 · profile geo PL · proxy pl-resi-04
LayerSignalAssertionResult
{{ r.layer }}
{{ r.signal }}
{{ r.assertion }}
{{ r.status }}
Fallback When endpoint policy forbids automation, the run switches to the legal data path — research and ops keep their result set instead of dying on the challenge.
Imperva ladder
{{ s.stage }} {{ s.body }}
Reported as a classification, never as a percentage. If the wall is policy, we say so.
04 — Platform

Platform capabilities

Full capability surface for agents, research, QA and authorized operations — shipped today, or on the roadmap with a stated priority and the surface it lands on.

PhaseCapabilityValueSurface
{{ c.phase }} {{ c.title }} {{ c.value }} {{ c.surface }}
05 — UI-as-API

Service
Action Packs

No API, or an API priced out of the workflow — but the UI works. Map the service once, compile it into a durable pack, then invoke it through MCP like REST.

A pack is a versioned artifact, not a prompt: typed inputs, named actions, expected output shapes, guardrails attached.

{{ s.n }} · {{ s.name }}

{{ s.body }}

  • {{ d }}
Compile once, invoke cheap

A pack is compiled from a mapping run and replayed deterministically. The model is not in the loop for every click, so cost per invocation stays flat as volume grows.

  • {{ co }}
    •
Agent-per-click alternative

Generic web agents re-reason the same screen on every run — variable latency, variable output shape, model spend on every step of a task you already solved.

  • {{ pc }}
    •
Example packs
pack.invoke · via MCP {{ packVersion }} 
{{ packSnippet }}
{{ packResult }}
Actions
  • {{ a }}
    •
Guardrails
  • {{ g }}
    •

Prefer the official API when one is available. Action Packs run on an authorized account, read-only by default, with human approval required for any submit.

06 — Scope

Not an antidetect farm

Same power surface as the antidetect category — profiles, proxies, fingerprints, mobile, RPA — pointed at a different job. AION is built for agent runs you can explain to an auditor.

Built for
  • {{ b }}
    •
Out of scope
  • {{ o }}
    •
How it is enforced
  • {{ e }}
    •