Your browser agent wastes tokens and time every time it asks an LLM what to click. AIR SDK replaces guessing with knowing. This is an early research preview.
Up to 7,000x cost reduction and 280x faster vs frontier models. One function call. Zero code changes.
Benchmarks
Measured across 8 major domains, 40 cold API calls, cache disabled. LLM baseline priced at Frontier Model ($15/$75 per M tokens). AIR SDK at Scale tier ($149/mo, 250K executions).
Collective intelligence for browser automation agents. Site capabilities, selectors, and extraction.
AIR_API_KEY
Última verificação
2026-11-08
Estrelas
—
Ferramentas
—
Disponibilidade
—
Scenario
LLM DOM Reasoning (Frontier Model)
AIR SDK (Macro Path)
Savings
1 browser action
~$0.24, ~4s, ~10K tokens (2 LLM round trips to inspect DOM and act)
$0.0006, 178ms, 0 tokens
400x cost reduction, 22x faster
10 browser actions
Up to ~$4, ~50s, ~175K tokens (25 LLM round trips as context grows)
$0.0006, 178ms, 0 tokens
Up to 7,000x cost reduction, 280x faster
The more complex the workflow, the more you save. LLM costs compound — every action adds to the conversation context, making each subsequent round trip more expensive. AIR's macro path is always one API call, regardless of how many steps the workflow has.
LLM baseline: Agent inspects page DOM, reasons about which elements to interact with, generates tool calls. Frontier Model pricing ($15/M input, $75/M output).
10 actions: Context grows with each action (conversation history accumulates). Average ~6,000 input + 1,000 output tokens x 2.5 round trips per action = 25 total LLM calls, ~175,000 tokens, ~$4.13, ~50s reasoning time.
Sonnet 4 comparison: 5x cheaper per token — 1 action: ~$0.05, 10 actions: ~$0.83. Still 80–1,400x more expensive than AIR at Scale.
AIR SDK macro path: Pre-verified CSS selectors returned via API. Agent executes directly — no DOM inspection, no LLM reasoning. Cost = plan price / included executions.
Raw API latency (40 measurements, cache disabled):
Browser automation is fragile. Selectors break. Sites change. Your agent has no idea what's possible until it's already on the page.
AIR SDK gives your agent three things:
What
How
Site intelligence
Know what actions are possible on any website — search, purchase, login, browse — before your agent navigates there.
Resilient selectors
When a selector fails, the SDK automatically resolves fallback alternatives so your automation doesn't break.
Continuous learning
The platform gets smarter over time, improving reliability and coverage across the web.
How it works: Wrap your page with withAIR(). The SDK observes actions, resolves selectors, and preloads site capabilities. Your code doesn't change — it just works better.
API keys are stored at ~/.config/air/credentials.json with 0600 permissions (owner read/write only).
npx @arcede/air-sdk init # Save your key (opens dashboard)
npx @arcede/air-sdk whoami # Show current key, source, and agent status
npx @arcede/air-sdk logout # Remove key from all locations
Key resolution order: AIR_API_KEY env var → ~/.config/air/credentials.json → .env in current directory.
Agent Skill
Give your coding agent site intelligence with one command:
npx @arcede/air-sdk install-skill
This auto-detects Claude Desktop, Claude Code, Cursor, Windsurf, and OpenClaw, writes the MCP server config, and injects your API key. It installs @arcede/air-sdk globally for fast agent startup (~2s instead of ~60s with npx) and writes the absolute binary path to each config to avoid npx version caching issues. Restart your agent and it instantly has new tools.
Requires global install: npm install -g @arcede/air-sdk. If not installed globally, replace "command": "air-sdk" with "command": "npx" and "args": ["--mcp"] with "args": ["-y", "@arcede/air-sdk", "--mcp"].
Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo AIR SDK?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
AIR SDK precisa de uma chave de API?
O publicador lista estas variáveis de ambiente: AIR_API_KEY.
Qual transporte AIR SDK usa?
AIR SDK roda localmente via stdio.
Quando AIR SDK foi verificado pela última vez?
Última verificação: 2026-11-08. Collective intelligence for browser automation agents. Site capabilities, selectors, and extraction.