iatlas-browser

Hosted API for public-safe retrieval and hosted read-only site adapters

Use miaoda.vip for public retrieval. Use the local runtime for real browser control.

The hosted interface is designed for the narrow remote-safe part of the product: public URL retrieval, metadata extraction, and a curated subset of read-only hosted adapters. Register by email, get an API key, and call the server directly. If the task depends on your tabs, login state, cookies, or live page context, that still belongs to the local iatlas-browser runtime with extension, daemon, and MCP.

Public URLs only 1000 daily requests per email-bound key Hosted subset, not full browser automation
Open JSON docs Local runtime homepage Sites catalog
browser open api browser automation api url open api chrome automation api browser metadata api public api key access

Endpoint summary

One key model, multiple public endpoints

POST /v1/register

Create or rotate an email-bound API key.

curl -s https://miaoda.vip/v1/register \
  -H "Content-Type: application/json" \
  -d '{"email":"user@example.com"}'

GET /v1/usage

Check the current daily usage for the authenticated key.

curl -s https://miaoda.vip/v1/usage \
  -H "Authorization: Bearer $API_KEY"

POST /v1/open

Open a public URL and request metadata, text, or HTML.

curl -s https://miaoda.vip/v1/open \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","mode":"metadata"}'

GET /v1/catalog/sites

Browse the full `lao-s` adapter catalog through API form.

curl -s "https://miaoda.vip/v1/catalog/sites?q=github"

POST /v1/sites/run

Run the hosted subset of `lao-s` adapters directly on the remote server.

curl -s https://miaoda.vip/v1/sites/run \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"github/repo","args":{"repo":"miounet11/lao"}}'

Hosted adapters on miaoda.vip

The remote server now executes a curated, reliable subset of public read-only adapters directly. Use GET /v1/sites/hosted to discover what is currently available. 

curl -s https://miaoda.vip/v1/sites/hosted

What still stays local

Adapters that rely on a personal browser session, login, Pinia stores, tabs, or user-specific cookies remain local by design and should be used through CLI or MCP. That is the core mode of the product, not a fallback.

Browse the full sites page

Decision guide

Choose the hosted API only when the job is remote-safe

Task Hosted Open API Local iatlas-browser runtime
Fetch metadata or text from a public URL Use /v1/open Not required
Run a public read-only hosted adapter Use /v1/sites/run Optional only if you want local consistency
Work with your own login state or tabs Wrong boundary Use CLI, daemon, or MCP against your own Chrome
Inspect a live authenticated page Wrong boundary Use local runtime and browser snapshot/network tools

Request details

How the hosted browser-open interface behaves

Field Meaning
url Absolute public http or https URL.
mode metadata, text, or html.
timeoutMs Optional timeout, capped server-side.
Auth Authorization: Bearer <apiKey> or X-API-Key.
Quota 1000 requests per email-bound API key per day.

Mode examples

What you get back from /v1/open

metadata

Returns title, meta description, final URL, status, and a text excerpt.

text

Returns stripped text content for quick indexing or downstream processing.

html

Returns the response body for public textual pages within the server-side body limit.