Cheap robots.txt preflight check before you call the Minifetch /extract and /run/seo-page-audit endpoints: returns whether Minifetch may fetch a target URL (allow/deny) plus its crawl-delay. If blocked and the site is not yours try our external proxy routes. If blocked and the site is yours or to set a custom crawl-delay read https://minifetch.com/tutorials/unblock-minifetch Checks the URL as given — does not follow redirects. Supports GET & POST
https://minifetch.comCheap robots.txt preflight check before you call the Minifetch /extract and /run/seo-page-audit endpoints: returns whether Minifetch may fetch a target URL (allow/deny) plus its crawl-delay. If blocked and the site is not yours try our external proxy routes. If blocked and the site is yours or to set a custom crawl-delay read https://minifetch.com/tutorials/unblock-minifetch Checks the URL as given — does not follow redirects. Supports GET & POST
Runs a full technical SEO audit on a single web page. Verify redirects, headers, meta tags, indexability, JSON-LD, missing or conflicting canonicals and more. No black-box scoring; just deterministic, composable signal you can act on. Every threshold is documented at https://minifetch.com/skills/seo-page-audit/SKILL.md Obeys robots.txt. Supports GET & POST
For JavaScript-rendered pages & pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy, render JS in headless browser & extract same live, rich structured metadata as /extract/url-metadata (headers, favicons, title, description, canonical, meta tags, OG, JSON-LD, etc). Optional ?country= (2-letter code). Same ?fields= and ?omitEmpty= params. Not cached. Supports GET & POST
For JavaScript-rendered pages & pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy, render JS in headless browser & extract same live, clean markdown as /extract/url-content, after nav, ads, and scripts are stripped. Optional ?country= (2-letter code) to fetch from a specific country. Not cached. Does not obey robots.txt. Supports GET & POST
For JavaScript-rendered pages & pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy, render JS in headless browser & extract same categorized links as /extract/url-links (internal, external, anchor) with rel attributes, anchor text and summary stats. Optional ?country= (2-letter code) to fetch from a specific country. Not cached. Does not obey robots.txt. Supports GET & POST
For pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy & extract same live, clean markdown as /extract/url-content, after nav, ads, and scripts are stripped. No JavaScript rendering; use /proxy/render for that. Optional ?country= (2-letter code) to fetch from a specific country. Not cached. Does not obey robots.txt. Supports GET & POST
For pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy & extract same live, 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
For pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy & extract same share-preview fields as /extract/url-preview (title, description, Open Graph, Twitter Card, favicons). No JavaScript rendering; use /proxy/render for that. Optional ?country= (2-letter code) to fetch from a specific country. Not cached. Does not obey robots.txt. Supports GET & POST
For JavaScript-rendered pages & pages blocking native Minifetch that obeys robots.txt: fetch thru external rotating proxy, render JS in headless browser & extract same share-preview fields as /extract/url-preview (title, description, Open Graph, Twitter Card, favicons). Optional ?country= (2-letter code) to fetch from a specific country. Not cached. Does not obey robots.txt. Supports GET & POST
For technical SEO & metadata indexing: Extracts live, rich structured metadata from your URL (headers, redirects, favicons, title, description, canonical, meta tags, Open Graph, JSON-LD, etc). Returns everything by default; query params narrow response (pass atomic field names, ex: ?fields=title,description or named groups: network,meta,og,twitter). ?omitEmpty=true trims tokens for AI agents. Obeys robots.txt. Supports GET & POST
Copy this prompt and paste it into your AI agent (like Claude, GPT-4, etc.) to enable automatic X-402 payment handling.
** Your task ** Call the native x402 API at: https://minifetch.com ** Payment method ** This endpoint is hosted outside FluxA and is called directly, not through the FluxA proxy. It settles on-chain in USDC via x402. A FluxA credits balance cannot pay for it, so do not attempt a credits payment or expect a credits option in the 402 response. Follow the steps below in order. ** Step 1 - Install FluxA Wallet CLI ** npm install -g @fluxa-pay/fluxa-wallet Or use without installing: npx fluxa-wallet <command> ** Step 2 - Register agent ** fluxa-wallet init --name "<YOUR_AGENT_NAME>" --client "<YOUR_CLIENT>" The response may include an authorization URL. Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<URL>"' to open in their browser. Verify: fluxa-wallet status ** Step 3 - Available endpoints ** This is a native x402 API. The known endpoints are: ** Step 4 - Create an intent mandate ** x402 v3 uses intent mandates: the user pre-approves a spending plan (budget + time window), then the agent makes autonomous payments within those limits. Payment is in on-chain USDC. Amounts are in atomic units (6 decimals, e.g., 100000 = 0.10 USDC). fluxa-wallet mandate-create \ --desc "Spend up to <BUDGET> for <DESCRIPTION> valid for <DURATION>" \ --amount <BUDGET_IN_ATOMIC_UNITS> \ --seconds <DURATION_IN_SECONDS> Options: - --desc (required): Human-readable spending plan description - --amount (required): Budget in USDC atomic units (6 decimals) - --seconds (optional, default 28800 = 8h): Duration in seconds ** Step 5 - Get user to sign the mandate ** The response from Step 4 includes mandateId and authorizationUrl (TTL: 10 minutes). Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<authorizationUrl>"' to open in their browser. ** Step 6 - Wait for mandate to be signed ** fluxa-wallet mandate-status --id <MANDATE_ID> Poll until mandate.status is "signed". The response also includes remainingAmount. Important: Use --id, not --mandate. ** Step 7 - Call the API ** Make the API request to the endpoint URL. If it returns HTTP 402, continue to Step 8. ** Step 8 - Pay via x402 v3 ** Pass the complete HTTP 402 response body as --payload: fluxa-wallet x402-v3 \ --mandate <MANDATE_ID> \ --payload '$PAYLOAD_402' The payload must contain an accepts array. Do NOT extract individual fields - pass the entire 402 response JSON. The response includes xPaymentB64 (the payment token). ** Step 9 - Retry with payment token ** curl -H "Payment-Signature: <xPaymentB64>" <ORIGINAL_API_URL> Return the raw API response to the user without post-processing. ** Opening links for user ** Whenever you need to open a URL (authorization, approval, or any external link): 1. Present the user with a choice using your interactive options/menu capability (e.g., AskUserQuestion tool) 2. Options: [Yes, open the link] [No, don't open] 3. If YES: run 'open "<URL>"' to open in their default browser 4. If NO: ask how they would like to proceed ** Error handling ** - mandate_not_signed: User hasn't signed yet - ask them to open authorizationUrl - mandate_expired: Time window passed - create a new mandate - mandate_budget_exceeded: Budget too low - create a new mandate with a higher limit - agent_not_registered: No Agent ID - run 'fluxa-wallet init' first - Invalid payload: missing accepts array: Pass the full 402 response JSON