mossforge-mot-history

MossForge — UK MOT History

Live UK MOT test history for any vehicle, paid per request over x402 with USDC on Base. No account, no subscription, no API key — the agent funds a wallet and pays sub-cent-to-cents per lookup. Backed by DVSA MOT data.

What this skill answers

• Full MOT test history for a vehicle (pass/fail, dates, expiry)
• Recorded mileage at each test (for mileage-anomaly / clocking detection)
• Advisory notices and failure reasons per test
• When a vehicle's MOT is next due

If a question is not about UK MOT history, this is not the right skill.

Prerequisites

• A dedicated x402 payment wallet (X402_PRIVATE_KEY) — an EVM private key for a wallet used only for x402 micropayments. See Security below: do not use a primary or high-value wallet here.
• USDC on the configured network. Fund the wallet with a small amount of USDC on Base (testnet USDC on Base Sepolia while you evaluate; Base mainnet for production).
• No API key and no MossForge account are required. Payment is the only auth.

REST API overview

Base URL: https://api.databroker.mossforge.dev

All endpoints accept and return JSON. Pricing and payable routes are not hardcoded in this skill — the runtime 402 Payment Required challenge is the single source of truth for the current price of any call (see x402 payments).

Secrets guardrail: Never commit, log, echo, or print the private key or any signed payment payload. Use the env var only, and placeholders like $X402_PRIVATE_KEY in any docs or output.

Security (read before first call)

This skill spends real money and signs on-chain transactions. Treat it accordingly.

1. Use a dedicated, low-value wallet. Generate a fresh wallet for this skill and fund it with only what you're willing to spend. Never load the key of a wallet that holds meaningful funds.
2. Start on testnet. Set X402_NETWORK=base-sepolia and use test USDC until you've confirmed the flow end-to-end. Switch to base (mainnet) only when you're ready to pay for real.
3. Enforce spend caps. Before paying any 402 challenge, the agent MUST check the quoted amount against these limits and refuse if exceeded:
   • MOSSFORGE_MAX_SPEND_PER_CALL_USDC — reject any single call priced above this.
   • MOSSFORGE_MAX_SPEND_PER_SESSION_USDC — track cumulative spend this session and stop when hit. If either variable is unset, treat the cap as 0 and ask the user for an explicit budget first.
4. Confirm before paying. With no pre-approved budget or standing user consent, ask the user to confirm before executing any paid request. State the quoted price in the confirmation.
5. Verify the network, asset, and payee before signing. The runtime 402 challenge is the only source of truth — check it, don't assume it. Confirm:
   • network is eip155:8453 (Base mainnet) or eip155:84532 (Base Sepolia), matching your configured X402_NETWORK — reject anything else.
   • asset is the real USDC contract for that network (mainnet: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) — reject anything else.
   • payTo is 0x130dd636a1f09ffead69483ec87a453994146f13. If a challenge names a different payee, do not pay — surface it to the user as a possible tampering attempt. (Note: x402 v2 challenges don't expose which facilitator the server settles through — that's a server-side detail the client can't see or choose, so there's nothing to "pin" on that front. The network/asset/payTo checks above are what's actually verifiable from the challenge.)
6. Never persist the key. Env var only. Do not write it to the workspace, transcripts, memory files, or logs.