HTML links

Enumerate every <a href> in an HTML string with its anchor text and rel attribute. Send POST /api/html-links with the required field html and pay $0.001 per call over x402 or MPP, or call it free by solving a proof-of-work challenge. It returns a JSON object with count and links.

Optionally resolves relative hrefs against a base URL and filters by a regex on the href. The deterministic way to crawl a page's outlinks without writing a regex.

Try in playground →

Parameters

Example request

curl -i -X POST https://agent402.tools/api/html-links \
  -H "Content-Type: application/json" \
  -d '{"html":"<a href=\"/about\">About</a><a href=\"https://example.com\">External</a>","base":"https://agent402.tools"}'

Without payment this returns HTTP 402 Payment Required with the exact price for html-links; any x402 v2 or MPP client pays it and retries.

Example response

{
  "count": 2,
  "links": [
    {
      "href": "https://agent402.tools/about",
      "text": "About",
      "rel": ""
    },
    {
      "href": "https://example.com/",
      "text": "External",
      "rel": ""
    }
  ]
}

From an MCP client

catalog.call {
  "slug": "html-links",
  "params": {
    "html": "<a href=\"/about\">About</a><a href=\"https://example.com\">External</a>",
    "base": "https://agent402.tools"
  }
}

On the hosted connector at https://agent402.tools/mcp, catalog.call runs html-links free (rate-limited, no wallet). Local install: npx -y [email protected].

Errors and behavior

• html is required. An input the tool rejects returns an HTTP 4xx whose body carries error, tool, expected, required and example, so the caller can correct it.
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is canceled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Free tier: no outbound network call leaves the server for this tool, so proof-of-work (16 leading zero bits of sha256) pays for it.
• A GET or HEAD to /api/html-links returns the same 402 quote, so the price can be read without a body.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.({ maxAmountPerPayment: "$0.001" }); // refuse any quote above this tool's price
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/html-links", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "html": "<a href=\"/about\">About</a><a href=\"https://example.com\">External</a>",
    "base": "https://agent402.tools"
  }),
});

No wallet? Pay with compute

Fetch a challenge, solve the sha256 puzzle (16 leading zero bits, a fraction of a second of CPU), and resend with the X-Pow-Solution header:

import { createHash } from "node:crypto";
const lz = (b) => { let t = 0; for (const x of b) { if (!x) { t += 8; continue; } t += Math.clz32(x) - 24; break; } return t; };
const c = await (await fetch("https://agent402.tools/api/pow/challenge?slug=html-links")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/html-links", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"html":"<a href=\"/about\">About</a><a href=\"https://example.com\">External</a>","base":"https://agent402.tools"}) });

Part of these workflows

HTML links is one step in these 2 skill packs, each sold as a single call:

• Structured scrape - Pull structured data out of any web page deterministically - articles to clean text, tables to JSON rows, specific elements via CSS selector - without writing regex against raw HTML.
• API investigation - Point at an unknown API endpoint and figure out how to use it: auth scheme, content type, version, rate limits, OpenAPI/Swagger spec discovery, and JSON response structure. The deterministic recon workflow before writing a single line of integration code.

Related tools