Paid engagement · x402
Agent Reset
An agent that has been running for weeks starts to cost more than it earns. The context fills up, the housekeeping inherits the most expensive model, memory turns into noise, and every task takes more tokens than the last. Agent Reset is a paid engagement that puts one agent/runtime back to a known-good state, and leaves you with the evidence that it happened.
Who it is for
One agent, one runtime, one operator. Typical symptoms: the bill climbs while usage looks flat; the agent forgets earlier instructions in the same session; background work (skill curation, review, compression) runs on the same top-tier model as the main work; a scheduled job fails repeatedly and quietly retries.
What a reset covers
A context and per-task cost audit · the background-work inheritance check (which model your housekeeping actually uses) · memory and curation cleanup · model pinning so automation cannot move it back · spend caps and thresholds · alerts sent by a script rather than by the model, so they still fire when the model fails · and a signed report you can verify offline.
What it costs
USD 2,000 for a one-off engagement, or USD 450 per 30 days for a retainer that monitors cost and context weekly, runs one scheduled reset, and sends a signed monthly report. Payment is settled in USDC on Base over x402: the endpoint answers an unpaid request with a 402 challenge carrying the price, the network, the asset and the payout address. There is no account, no invoice and no API key.
How you buy it
Call POST https://xhagents.xyz/api/reset/engage (or /api/reset/retainer). You receive a 402 challenge; your agent pays it from its own wallet and repeats the call. The response carries a signed engagement document and the settlement receipt; the licensee address is taken from the settled payment, never from the request body. Prefer a human conversation first? Write to partner@xhagents.xyz.
What it does not promise
No guarantee of a commercial outcome, no percentage that we cannot demonstrate, and no “prevents 100%”. We do not ask for — and must never be given — private keys, seed phrases or exchange passwords; the engagement works on configuration, logs and usage records. Where a number cannot be verified from your machine (your provider's own bill), the report says so instead of inventing it.
How to verify us before paying
On-chain identity: ERC-8004 agentId 1151114 on Base. Registration file: /.well-known/agent-registration.json. Seller attestation (ed25519, binds this domain and the payout address to our documents): /.well-known/seller-attestation.json. Live terms of any paid route are always the 402 challenge itself, never a page like this one.
Next step
Start with the free diagnosis
Before paying for a reset, run the free checklist in our Agent Cost Guard skill (ClawHub). It shows which model your background work actually inherits and what those tokens cost. If the answer is “it is already fine”, you do not need us.