canonical: https://jentic.com/apis/multion.ai/multion

# MultiOn Web API

The MultiOn Web API drives an autonomous browser that acts on live websites from natural-language instructions. It starts a browsing session, issues a browse command that navigates and interacts with a page, retrieves structured data from the current page, and captures a screenshot. Each session keeps browsing state, and the API can list active sessions or close one when a task is finished.

## For AI agents

Drive an autonomous browser: start a session, browse and act on live web pages from natural-language instructions, retrieve page data, capture screenshots, and manage sessions.

## Scope

Does not host models or provide standalone LLM inference. Use it to drive a browsing session, act on live pages, retrieve page data, and capture screenshots only.

## Capabilities

- Start a browsing session that keeps page state across steps
- Issue a browse command that navigates and acts on a live web page from a natural-language instruction
- Retrieve structured data from the page the session is on
- Capture a screenshot of the current session
- List active sessions or close one when the task is done

## Use cases

### AI Agent Web Automation

Give an AI agent hands on the live web. The agent discovers the browse and session operations through Jentic, stores the MultiOn key once, and sends natural-language instructions that navigate and act on real pages, without scripting selectors. Session state carries the task across several steps.

Example prompt: Start a session, instruct the agent to complete a multi-step task on a target site, and return the outcome

### Web Data Extraction

Pull structured data from pages that need interaction to reach. After a browse command navigates to the right view, the retrieve operation returns structured content from the current page, so an agent can gather data behind logins, forms, or dynamic navigation.

Example prompt: Browse to a target page, then retrieve the structured data the workflow needs from the current view

### Session-Based Browsing Workflows

Run long tasks that span several page interactions. A session preserves browsing state, so an agent can issue successive browse commands, check progress, and close the session when finished, keeping each task isolated.

Example prompt: Open a session, run a sequence of browse steps toward a goal, and close the session once the task completes

### Visual Verification

Confirm what the agent is seeing. The screenshot operation captures the current state of a session, so a workflow can log a visual record or verify a page rendered as expected before acting.

Example prompt: Capture a screenshot of the active session and attach it to the task log for verification

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/browse` | Navigate and act on a web page |
| POST | `/retrieve` | Retrieve structured data from the current page |
| POST | `/session` | Start a browsing session |
| GET | `/sessions` | List active sessions |
| GET | `/screenshot/{session_id}` | Capture a session screenshot |

## Key resources

- **Browse** — Navigate and act on a live web page from a natural-language instruction.
- **Retrieve** — Return structured data from the current page.
- **Sessions** — Start, list, and close browsing sessions that keep page state.
- **Screenshot** — Capture the current state of a session as an image.

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 84 / 100
- **View full report:** https://jentic.com/apis/multion.ai/multion/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the MultiOn Web API by hand means learning its header-key auth and managing browsing sessions and their state yourself. Through Jentic you install once, import the API from the API Directory, store the key, and your agent calls the browse or retrieve operation it needs.
- **Permission scoping:** You decide which MultiOn operations your agent may call. A rule can grant browsing and retrieval while withholding session deletion, so the agent works pages without tearing down state, and the rule bounds operations rather than a single session.
- **Credential handling:** Your MultiOn API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'browse a website and complete a task', and Jentic returns the matching MultiOn operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Browserless** — Runs headless Chrome for scripted browser automation.
- **Apify** — Runs web scrapers and browser automation actors at scale.
- **Firecrawl** — Crawls sites and returns clean page content for models.
- **OpenAI** — Provides language models for reasoning and generation.

## FAQ

### What authentication does the MultiOn Web API use?

The MultiOn Web API expects an API key sent in a request header, as declared by its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when a call runs, so it never enters the agent's prompt or logs.

### Can the MultiOn Web API act on pages, not just read them?

Yes. A browse command navigates and interacts with a live page from a natural-language instruction, so the agent can click, type, and move through a flow, then use the retrieve operation to read structured data from the resulting page.

### What are the rate limits for the MultiOn Web API?

The OpenAPI spec does not publish specific rate limits. Check the MultiOn documentation for current limits, and have your agent back off and retry when it receives a throttling response.

### How do I automate a web task with the MultiOn Web API through Jentic?

Search Jentic for an intent like 'browse a website and complete a task', and it returns the matching MultiOn operation with its input schema. Import the connector once, store your key, and your agent drives the browser without hand-written HTTP code. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a MultiOn MCP server?

You don't need an MCP server to give your agent the MultiOn Web API. Jentic connects it directly from the Jentic API Directory: import the API, store your key once, and your agent calls the browse, retrieve, and session operations. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.

### Can I limit what my agent is allowed to do with the MultiOn Web API?

Yes. You choose the operations the agent may call, so a rule can allow browsing and data retrieval while withholding session deletion unless you add it. A rule bounds which operations run rather than which individual session is affected, and every call is logged.
