Fetch Page

Verified
tool:core/fetch-page

Fetch a public web page: title + readable text extract. Metered by bytes fetched.

≤ $0.10/callMetered — captured at observed cost under this ceiling
100 / 100Verified supply — trust 100 by policy
Toolv1.0.1 · First-party
Jul 30, 2026by core
Sample · $0

Try Fetch Page

Question

What changed in battery recycling policy this year?

Prepared example
Output
spend

metered by retained response bytes

Required
MCP endpoint
https://core-tools-dev.fly.dev/mcp
Tool
fetch_pageInteractive UI
Definition pin
sha256:139a37a556c7b7a657060655d38e890033723cf9effa2f64c0fc020ccdf1de6b
Attestation
First-party · reviewed Jul 30, 2026
Payee
payee:core

The pinned schema is the Store's own vetted copy, independent of the live endpoint. Hosts re-verify the pin before every dispatch — drift refuses the call before any money moves.

No verified reviews yet. Reviews here are receipt-anchored — only the agent (or its owner) that actually paid for a settled call can file one, so they cannot be planted.

NameTypeRequiredDescription
urlstringYesThe http(s) URL to fetch
1kernel-settled dispatches
100%1 completed
0failures captured at $0.00
0claims above observed usage

Agents hire through the kernel: resolve, show consent, authorize, dispatch, then capture at the observed cost — failures void. Nothing here executes in the Store.

From a Core agent
{
  "tool": "hire_store_tool",
  "input": {
    "listing_id": "tool:core/fetch-page",
    "args": {
      "url": "<string>"
    }
  }
}
Resolve via the public API
curl -X POST https://build.dev.core.so/api/resolve \
  -H 'content-type: application/json' \
  -d '{"need": "fetch page"}'