Monitor Keyword
by page-keyword-monitor in Developer tools
Keyword monitor: fetches a page and reports, for each keyword you give (comma-separated after the URL), whether it is present in the readable text, how many times, and a context snippet; also remembers the previous result per URL so it can tell you which keywords appeared or disappeared since your last call. 'Sold out', 'in stock', price wording, name mentions. $0.01 per check.
https://intel.rallylive.ca/monitor/keyword- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 51 ms
- 482 ms slowest 5%
- Last check
- Passed
- 41 min ago, next in 6 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://intel.rallylive.ca/monitor/keyword
Each call costs $0.01 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://intel.rallylive.ca/monitor/keyword
content-type: application/json
{
"query": "https://example.com/ | illustrative"
}Example response
The provider's example. We can't check it without paying.
{
"appeared": [],
"disappeared": [],
"keywords": {
"illustrative": {
"count": 1,
"found": true,
"snippet": "…for use in illustrative examples…"
}
},
"previous_check": null,
"url": "https://example.com/"
}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.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://intel.rallylive.ca/monitor/keyword' \
-H 'content-type: application/json' \
--data-raw '{"query":"https://example.com/ | illustrative"}'
# 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://intel.rallylive.ca/monitor/keyword' \
-H 'content-type: application/json' \
--data-raw '{"query":"https://example.com/ | illustrative"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fintel.rallylive.ca%2Fmonitor%2Fkeyword&method=POST
const res = await pay("https://intel.rallylive.ca/monitor/keyword", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"query": "https://example.com/ | illustrative"
}),
});
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://intel.rallylive.ca/monitor/keyword",
json={
"query": "https://example.com/ | illustrative",
},
)
print(res.status_code, res.text)Security scan
1 finding
- Payment address changed recently in payment
Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 41 min ago | Passed | 402 | 83 ms | $0.01 |
| 11 h ago | Passed | 402 | 404 ms | $0.01 |
| 22 h ago | Passed | 402 | 80 ms | $0.01 |
| 31 h ago | Passed | 402 | 112 ms | $0.01 |
| 41 h ago | Passed | 402 | 76 ms | $0.01 |
Show 10 older checks
| 45 h ago | Passed | 402 | 76 ms | $0.01 |
| 2 days ago | Passed | 402 | 39 ms | $0.01 |
| 2 days ago | Passed | 402 | 45 ms | $0.01 |
| 2 days ago | Passed | 402 | 48 ms | $0.01 |
| 3 days ago | Passed | 402 | 52 ms | $0.01 |
| 3 days ago | Passed | 402 | 47 ms | $0.01 |
| 3 days ago | Passed | 402 | 126 ms | $0.01 |
| 3 days ago | Passed | 402 | 48 ms | $0.01 |
| 3 days ago | Passed | 402 | 43 ms | $0.01 |
| 3 days ago | Passed | 402 | 47 ms | $0.01 |
History
| 11 Oct 2026 | Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3 |