TOON anonymous fetch (l402-door)

Verified: delivered 3 times

How we rate this

Delivery health: healthy. Paid successes: 3. Paid failures: 0. Last successful delivery: 2026-10-15. Schema confidence: high.

Verified means the listing is healthy, the schema confidence is medium or high, and paid deliveries outnumber paid failures. Working means it is healthy with that same schema confidence, and no paid buy has verified it yet. Limited track record means the health, the paid history, or the schema confidence is still thin. Having trouble means the listing is paused or failing, or it is degraded and paid failures are at least as common as paid successes.

11 sats · ≈$0.009

Anonymous web fetch for AI agents, via L402. The page is fetched through the Anyone network and returned as markdown with a content hash.

More

Backed by a TOON mainnet node: Lightning in, ILP routing and x402 settlement behind it.

Example

What agents use this for. Anonymous web fetch for AI agents, via L402. Category: search.

Request

GET https://l402.mainnet.toonprotocol.dev/extract?url=https%3A%2F%2Fexample.com

curl

curl -sS -X GET \
  'https://l402.mainnet.toonprotocol.dev/extract?url=https%3A%2F%2Fexample.com' \
  -H 'Accept: application/json' \
  # Example only. No L402 token. Sends no sats.

MCP buy

buy({
  "sku": "4b1a7eb4-7f28-481b-b175-c2e69c3693d6",
  "params": {
    "url": "https://example.com"
  },
  "total_cost": "11 sats",
  "max_total_sats": 11
})

Example response

Stored from a successful paid delivery. Truncated to a size cap.

{"ok":true,"url":"https://www.rfc-editor.org/rfc/rfc791","final_url":"https://www.rfc-editor.org/info/rfc791/","status":200,"headers":{"content-type":"text/html;charset=utf-8","server":"cloudflare","date":"Thu, 15 Oct 2026 07:27:10 GMT","cache-control":"public, max-age=600, stale-while-revalidate=600"},"title":"RFC 791: Internet Protocol | RFC Editor","content":"RFC:  791\n\n                           INTERNET PROTOCOL\n\n                         DARPA INTERNET PROGRAM\n\n                         PROTOCOL SPECIFICATION\n\n                             September 1981\n\n                              prepared for\n\n               Defense Advanced Research Projects Agency\n                Information Processing Techniques Office\n                         1400 Wilson Boulevard\n                       Arlington, Virginia  22209\n\n                                   by\n\n                     Information Sciences Institute\n                   University of Southern California\n                           4676 Admiralty Way\n                   Marina del Rey, California  90291\n\n* * *\n\n* * *\n\nSeptember 1981\n                                                       Internet Protocol\n\n                           TABLE OF CONTENTS\n\n    PREFACE ........................................................ [iii](#page-iii)\n\n[1](#section-1).  INTRODUCTION ..................................................... [1](#page-1)\n\n  [1.1](#section-1.1)  Motivation .................................................... [1](#page-1)\n  [1.2](#section-1.2)  Scope ......................................................... [1](#page-1)\n  [1.3](#section-1.3)  Interfaces .................................................... [1](#page-1)\n  [1.4](#section-1.4)  Operation ..................................................... [2](#page-2)\n\n[2](#section-2).  OVERVIEW ......................................................... [5](#page-5)\n\n  [2.1](#section-2.1)  Relation to Other Protocols ................................... [9](#page-9)\n  [

Drew Pierson / TOON Protocol