77trust / 100

Extract Url Metadata

by minifetch.com in Search & web

x402 APIPassing, checked 22 min ago

For pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy & extract same rich structured metadata as /extract/url-metadata (headers, favicons, title, description, canonical, meta tags, OG, JSON-LD, etc). No JS render; use /proxy/render for that. Optional ?country= (2-letter code). Same ?fields= and ?omitEmpty= params. Not cached. Supports GET & POST

POST
https://minifetch.com/api/v1/x402/proxy/extract/url-metadata
Price
$0.003
per call in USDC
Uptime
100%
last 30 days
Response time
625 ms
666 ms slowest 5%
Last check
Passed
22 min ago, next in 7 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://minifetch.com/api/v1/x402/proxy/extract/url-metadata

Each call costs $0.003 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://minifetch.com/api/v1/x402/proxy/extract/url-metadata
content-type: application/json

{
  "fields": "title,description,canonical,og:title",
  "url": "https://github.com"
}

Parameters

ParameterTypeRequiredDescription
countrystringNoOptional. 2-letter ISO 3166-1 country code (ex: de, mx) to fetch from. Invalid code returns 400.
fieldsstringNoOptional. Selection narrows response to only fields you need: comma-separated atomic field names (e.g. title, description), named groups (network, meta, og, twitter), and/or meta:tag-name for specific meta tag. Returns all fields when omitted; an unknown field returns 400.
includeResponseBodybooleanNoOptional. If true, includes full HTML response body as string in result.
omitEmptybooleanNoOptional. If true, drops empty fields (empty string, [], {}) from response.
urlstringYesThe target URL from which to extract metadata.

Example response

The provider's example. We can't check it without paying.

Example response, 32 lines
{
  "queryParameters": {
    "fields": "title,description,canonical,og:title",
    "includeResponseBody": false,
    "omitEmpty": false
  },
  "results": [
    {
      "data": {
        "canonical": "https://github.com",
        "description": "Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.",
        "minifetchCache": {
          "hit": false
        },
        "og:title": "GitHub · Change is constant. GitHub keeps you ahead.",
        "proxy": {
          "country": null,
          "provider": "webscrapingapi.com",
          "proxyType": "managed",
          "proxyUrl": "https://api.webscrapingapi.com/v2",
          "render": false,
          "robotsTxt": {
            "allowed": null
          },
          "userAgent": "unknown"
        },
        "title": "GitHub · Change is constant. GitHub keeps you ahead. · GitHub"
      }
    }
  ],
  "success": true
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.003.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://minifetch.com/api/v1/x402/proxy/extract/url-metadata' \
  -H 'content-type: application/json' \
  --data-raw '{"fields":"title,description,canonical,og:title","url":"https://github.com"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://minifetch.com/api/v1/x402/proxy/extract/url-metadata' \
  -H 'content-type: application/json' \
  --data-raw '{"fields":"title,description,canonical,og:title","url":"https://github.com"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fminifetch.com%2Fapi%2Fv1%2Fx402%2Fproxy%2Fextract%2Furl-metadata&method=POST
const res = await pay("https://minifetch.com/api/v1/x402/proxy/extract/url-metadata", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "fields": "title,description,canonical,og:title",
    "url": "https://github.com"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://minifetch.com/api/v1/x402/proxy/extract/url-metadata",
        json={
            "fields": "title,description,canonical,og:title",
            "url": "https://github.com",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
22 min agoPassed402571 ms$0.003
5 h agoPassed402635 ms$0.003
9 h agoPassed402660 ms$0.003
13 h agoPassed402656 ms$0.003
17 h agoPassed402650 ms$0.003
Show 7 older checks
21 h agoPassed402666 ms$0.003
26 h agoPassed402602 ms$0.003
30 h agoPassed402182 ms$0.003
34 h agoPassed402537 ms$0.003
38 h agoPassed402541 ms$0.003
42 h agoPassed402625 ms$0.003
46 h agoPassed402661 ms$0.003