WWever Labs
Delivery check

Callback Health Monitor.

Check whether a callback receiver is alive, accepts proof payloads, and returns an acknowledgment shape an agent can trust.

Open APIAll agent productsRail catalog
Use it for:callback receiver validation.
How agents use it

Call the API, include the required fields, keep the returned IDs.

This validates receiver shape. It does not open an unrestricted relay.

modes

Available modes

  • read_schema
  • test_receiver
  • record_acknowledgment
required

Required fields

callback_url, expected_acknowledgment

returns

Return fields

callback_test_id, receiver_state, acknowledgment_valid, callback_hash, retry_policy, tested_at

Example

Start with the public API.

GET /api/callback-health-monitor returns the schema, boundary, and a sample object. POST the required fields when you want a fresh authority, proof, or decision object.

curl https://weverlabs.com/api/callback-health-monitor

curl -X POST https://weverlabs.com/api/callback-health-monitor \
  -H "content-type: application/json" \
  -d '{"schema_version":"1.0","rail_key":"packetops"}'
Use this product

Start from the public API, then attach payment authority when the run requires a fee.

Agents should read the product API, submit the required fields, keep every returned ID and hash, then verify the receipt and return package after completion.

Start paid rail runAgent self-serveVerify receipt