Monitor a public JSON API hourly against explicit schema requirements for seven days
0.5 USDC per seven-day hourly monitoring term
Paid only. No free trial for this operation.
1. Give your assistant the service instructions.
Mekler works through tools your assistant can call. You can use any model with a compatible MCP client or an HTTP tool integration. A chat without those tools cannot run a service on its own.
Help me complete this task with Mekler: Monitor a public JSON API hourly against explicit schema requirements for seven days. Read the agent instructions at https://api.mekler.ai/llms.txt and the exact contract for operation createSchemaMonitor at https://api.mekler.ai/catalog.json. Human service details: https://mekler.ai/services/schema-drift-monitor/. Check current trial eligibility. Explain any required tools or wallet setup. Do not spend funds or accept referral terms without my explicit authorization. Preserve the original input, request ID and proof for retries and recovery.
Your assistant needs web access to read these instructions and execution tools to act on them. This handoff does not install a connection or authorize a purchase.
2. Choose how to connect.
Use an MCP connection
If your assistant supports remote MCP, add Mekler in its tool or connector settings. It can then find services and read their requirements.
This operation requires a paid execution client. Inspect its exact contract and quote first, set a spending limit, and keep the original proof for recovery. AgentCash discovery alone does not certify this operation’s complete execution or referral support.
After reviewing the exact quote and authorizing your wallet budget, this example caps one request at the displayed amount. Keep the final response headers and original payment proof private for recovery. The cap applies per request, not to a whole session.
Prepare your private monitor request.
Generate a fresh owner key locally. The example key is public and must never authorize a real monitor. This command creates an owner-only file and refuses to overwrite it; replace the target and schema with your own requirements before payment.
python3 - <<'PY'
import json, os, secrets, uuid
request = {"request_id": uuid.uuid4().hex, "owner_key": secrets.token_hex(32),
"url": "https://api.mekler.ai/health", "schema": {"type": "object",
"required": ["status"], "properties": {"status": {"type": "string", "const": "ok"}}}}
# Set the target and requirements for your own authorized API before buying.
# Create once; preserve this private file and the original payment proof.
fd = os.open("mekler-monitor-request.json", os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o600)
with os.fdopen(fd, "w") as output:
json.dump(request, output)
print("Saved private request to mekler-monitor-request.json. Keep it private.")
PY
After finalized payment, keep the monitor ID, original request file and payment proof. Retrieve current status and alerts using the monitor ID in JSON and your private owner key as an Authorization bearer value. These follow-up calls are free; no alert email or webhook is sent.
npx -y agentcash@0.17.1 fetch https://api.mekler.ai/v1/services/schema-monitors/create-monitor -m POST --payment-network base --max-amount 0.5 -b "$(cat mekler-monitor-request.json)"
Keep the result and recovery information.
Pending or interrupted paid work must be recovered with the original body and proof. Never create a replacement purchase to resolve uncertainty. For trials, retry the identical body and request ID; a completed result can be recovered for seven days.
Mekler AI