Agentic Portal

URL Fetch Markdown

web
Serving

Fetch a URL and return its title and readable body text, with navigation and boilerplate stripped. POST /v1/url with {url} and get one JSON object back. The text is flattened: headings, links and lists are not kept as markdown structure. Responses may be served from cache. Pay per request in USDC; no account, no API key.

Endpoint
POST https://test.agent.pocket.network/v1/url-fetch-markdown/v1/url
Price per call
$0.005 USD
Networks payable on
Base Sepolia (eip155:84532)
Protocol
rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://test.agent.pocket.network/v1/url-fetch-markdown/v1/url \
  -H 'content-type: application/json' \
  -d '{"url":"https://example.com"}'
Example response

The response this call returned, captured 2026-09-25 15:53:34 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "url-fetch-markdown",
    "schemaCheck": "unchecked"
  },
  "data": {
    "url": "https://example.com",
    "title": "Example Domain",
    "markdown": "# Example Domain\n\nThis domain is for use in documentation examples without needing permission. Avoid use in operations.\n\n[Learn more](https://iana.org/domains/example)",
    "chars": 167,
    "truncated": false,
    "format": "markdown",
    "cached": true,
    "source": "cache",
    "service": "url-fetch-markdown"
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base Sepolia (eip155:84532). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods URL Fetch Markdown accepts, and whether each reads or writes.
MethodEffect
GET /v1/healthread
GET /v1/versionread
POST /v1/urlread

Schemas

Published by the service itself. The example above is generated from these.

Request schema
{
  "type": "object",
  "description": "The request body for POST /v1/url.",
  "properties": {
    "url": {
      "type": "string",
      "description": "The page URL to fetch."
    }
  },
  "required": [
    "url"
  ]
}
Response schema
{
  "type": "object",
  "description": "For POST /v1/url, a JSON object with url, title, markdown (flattened text), chars and a cache flag. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field."
}