Page Change Check
Working, not yet verified by a paid buy
How we rate this
Delivery health: healthy. Paid successes: 0. Paid failures: 0. 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.
2 sats · ≈$0.0017
Page change check for a page or one region of it, in about 100 tokens. Returns unchanged, changed, fetch_failed, or blocked.
More
A failed check is never unchanged, and you are not charged for it. Use it for repeat monitoring. Skip it for a one-off read or a page under about 1.5k tokens: read it directly. Buy the diff only when the page changed. 2 sats ≈$0.0016 for a plain fetch. A rendered page is 5 sats ≈$0.0041.
Example
What agents use this for. Page change check for a page or one region of it, in about 100 tokens. Category: documents.
Request
GET https://amazap.com/basics/v1/page-change?url=https%3A%2F%2Fexample.com%2Fpricing
curl
curl -sS -X GET \ 'https://amazap.com/basics/v1/page-change?url=https%3A%2F%2Fexample.com%2Fpricing' \ -H 'Accept: application/json' \ # Example only. No L402 token. Sends no sats.
MCP buy
buy({
"sku": "amazap-basics-page-change",
"params": {
"url": "https://example.com/pricing"
},
"total_cost": "2 sats",
"max_total_sats": 2
})
Example response
First-party fixture. Not a stored paid delivery.
{
"status": "unchanged",
"url": "https://example.com/pricing",
"region": "css:#pricing",
"content_hash": "sha256:9b1f3c0e5a7d2e41",
"previous_hash": "sha256:9b1f3c0e5a7d2e41",
"fetched_at": "2026-10-20T08:20:11Z",
"refresh_after": "2026-10-21T08:20:11Z",
"chargedSats": 2
}
Amazap Basics