Wever Watch · Standing instructions
Set it once. Hear back when it happens.
Tell Wever Watch what to keep an eye on and what you are waiting for. The service checks it on a schedule and sends a signed report to your agent when a check finds your condition met.
- Tool access
- 0.10 USDC / call
- Watches
- Up to 30 days
- Connection
- /mcp
- Result
- Signed fire report
Three steps.
- Set the instruction once.Choose what to watch, the number that matters and where the report should go. One call registers it for your wallet.
- The service checks it.On a schedule you choose, from every minute to once a day, Wever reads the value and compares it with your threshold.
- You hear back when it fires.When the condition is met, a signed report goes to your callback URL and stays on record for you to read later.
What it can watch.
- A data endpoint. Any public HTTPS URL that returns JSON. Point at the field you care about, such as
/data/price. - A prediction market. A Kalshi ticker or a Polymarket market, watched by its Yes price, bid, ask or last trade.
- A Base wallet. The USDC or ETH balance of any address on Base.
A condition is a field, a direction and a number: above, below, at or above, or at or below. Each fire marks one crossing. After a fire the watch waits for the value to move back before it can fire again, and it finishes after the number of fires you set, up to five. Every watch has an end date you choose, up to 30 days out. You can cancel it at any time and checks stop right away.
Version 1 sends reports. It reads public values and tells you what it saw. Your agent decides what to do next.
A short worked example
Waiting for a market to reach 75 cents.
The instruction
{
"name": "wever_watch-create",
"arguments": {
"target": {
"type": "prediction_market",
"market": "kalshi:EXAMPLE-MARKET-26NOV"
},
"condition": {
"field": "yes_price",
"operator": "at_or_above",
"threshold": "0.75"
},
"callback_url": "https://your-agent.example.com/hooks/watch",
"expires_at": "2026-11-28T17:00:00Z",
"check_interval_seconds": 300
}
}The report your agent receives
{
"type": "wever.watch-fire.v1",
"report": {
"watch_id": "wat_…",
"fire_id": "fir_…",
"fire_index": 1,
"description": "Fire when yes_price of kalshi:EXAMPLE-MARKET-26NOV is at or above 0.75.",
"observation": {
"observed_at": "2026-11-20T14:05:02.118Z",
"value": "0.77",
"met": true
},
"previous_observation": {
"observed_at": "2026-11-20T14:00:01.904Z",
"value": "0.72",
"met": false
},
"action": "report_only"
},
"receipt": {
"type": "wever.watch-fire.v1",
"algorithm": "Ed25519",
"token": "eyJ…"
}
}The report carries the value that met the condition, the value from the check before it, the time of each check and an Ed25519 receipt your agent can verify against the published key.
Call it from your agent.
Connect to https://weverlabs.com/mcp. Four tools manage your watches:
wever_watch-createregisters a watch for your wallet. One call covers every check until the watch ends.wever_watch-listlists your watches with their state, checks run and fires.wever_watch-statusshows one watch in detail, including every signed fire report and how its delivery went.wever_watch-cancelends a watch and stops its checks.
Each call costs 0.10 USDC on Base. Eligible calls share 10 free calls per wallet over a rolling 30 days with the other paid tools. Every call carries X-Wever-Wallet-Proof signed over the exact JSON arguments and the tool route, which is how Wever knows the watch is yours. A paid call adds the x402 payment from the same wallet.
Fire reports arrive as a JSON POST with an Idempotency-Key equal to the fire ID. The contract lists the target rules, scheduler, delivery format, limits and the public verification key.