COMPATIBILITY

Compatibility across protected sites.

Karon API supports common protected-site access workflows. Results vary by target site, configuration, and account policy.

Compatibility Matrix

Protection type	Coverage	API Access	Notes
Common protected sites	Varies	Varies	Test your target URL and chosen payload
CDN-backed public pages	Varies	Varies	Behavior depends on site configuration
Managed challenge workflows	Varies	Varies	Behavior depends on site configuration
High-friction product catalogs	Varies	Limited	Compatibility varies by endpoint
Request-rate sensitive sites	Varies	Varies	Test before production use
Form-heavy public pages	Varies	Varies	Test before production use
Captcha-gated pages	Limited	Limited	Some cases require alternate user workflows
Login-gated services	Restricted	Policy review	Some categories are blocked under the AUP

Performance Profile

The API offers multiple access modes so you can balance latency and compatibility for each target.

Cached Access

Low-latency repeat access
Best fit for already-established sessions
Typical response time around 60ms

Full Access

Higher latency, broader site coverage
Used automatically when stricter protections are detected
Typical response time around 3 seconds

Cached access can respond quickly after an access session exists. Full access adds latency but improves compatibility. The default managed access path prioritizes compatibility.

Karon API works natively from MCP-compatible agents (Claude Code, Cursor, Codex). See MCP Clients.

How It Works

1st request: Full access — establishes access state, caches session
cost: 10 credits · 3-10 sec

2nd+ request: Cached access — reuses session
cost: 1 credit · 45-250 ms