---
title: "Read a web page as clean text from an AI agent – superbot.gg"
canonical_url: "https://superbot.gg/use-cases/read-a-web-page-as-clean-text"
summary: "Paste a link and your agent reads the page and returns its readable text. A page that refuses comes back with the reason."
---

> Markdown of https://superbot.gg/use-cases/read-a-web-page-as-clean-text. Site index: /llms.txt.

# Read a web page as clean text

Give your agent a link.
It reads the page and returns the text.

[Get the app](https://superbot.gg/download?cta%5Fid=page%5Finstall) [see the real call](https://superbot.gg/use-cases/read-a-web-page-as-clean-text#call)

## What you get

- The readable text of a public page you paste.
- The reason, when a page will not open: a sign-in wall, a paywall, a bot or region wall, or a rate limit.
- A page that refused a plain fetch can be opened in a real browser, with an account.

## Ask your agent

Connect superbot once.
Other clients are on [the install page](https://superbot.gg/add).

```sh
claude mcp add --transport http superbot https://api.superbot.gg/mcp -s user
```

With no browser, post to the install route instead.

```sh
curl -fsS -X POST https://api.superbot.gg/mcp/install -d client=claude-code
```

Then ask in plain words.

```
superbot({"intent": "Read https://nodejs.org/en/about and give me the page as clean text."})
```

This needs an account.
An agent with none signs you in through [/auth.md](https://superbot.gg/auth.md).
You read back one emailed code.

## One real call

A real call, run on 2026-10-18 from a test account.
The reply is the agent's own, with its heading and sources line cut.

call

```
superbot({"intent": "Read https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle as clean text and show me the first twelve lines."})
```

reply

```
First twelve clean lines of the MCP lifecycle page are below.

1. Lifecycle
2. The Model Context Protocol (MCP) defines a rigorous lifecycle for client-server connections that ensures proper capability negotiation and state management.
3. Initialization: Capability negotiation and protocol version agreement
4. Operation: Normal protocol communication
5. Shutdown: Graceful termination of the connection
6. Lifecycle Phases
7. Initialization
8. The initialization phase MUST be the first interaction between client and server. During this phase, the client and server:
9. Establish protocol version compatibility
10. Exchange and negotiate capabilities
11. Share implementation details
12. The client MUST initiate this phase by sending an initialize request containing:
```

A page read, run live. The first twelve lines of the page text.

## Limits

Pages

Public pages only.

Refusals

A page that still refuses returns the reason, such as a sign-in wall, a paywall or a rate limit. A 401 sign-in refusal and a plain rate limit are not retried in a browser, and a browser can be refused too.

Needs

A superbot account.

## Related

- [Fetch a page that needs JavaScript](https://superbot.gg/use-cases/read-a-page-that-needs-javascript)
- [Crawl a site and list its URLs](https://superbot.gg/use-cases/crawl-a-site-and-list-its-urls)
- [Web search for an agent, with no API key](https://superbot.gg/use-cases/web-search-for-agents-without-an-api-key)
- [All use cases](https://superbot.gg/use-cases)

The page read is the Model Context Protocol lifecycle page. Read on 2026-10-18.