Fund your AI agent

/api/v1/aso/diagnose is an x402-paywalled endpoint. The first request comes back as HTTP 402 Payment Required with the offer in the PAYMENT-REQUIRED header. The client (your agent, via the SDK / CLI / MCP) signs an EIP-3009 authorization, retries with PAYMENT-SIGNATURE, and receives the diagnosis plus a settled receipt.

The signing wallet lives on your side. Sniffy never holds your key. Payment is on-chain and non-refundable, so the wallet should be a dedicated agent EOA — not your personal hot wallet.

Spin up a brand-new private key with viem. Don't reuse a wallet you keep meaningful balances in.

import { generatePrivateKey, privateKeyToAccount } from "viem/accounts";

const privateKey = generatePrivateKey();
const account = privateKeyToAccount(privateKey);

console.log("address:    ", account.address);
console.log("privateKey: ", privateKey);  // testnet-only, never commit

Mainnet is the path that actually settles today. $0.50 of USDC on Morph covers dozens of diagnose calls.

Fastest path: buy USDC on Bitget

Bitget lists Morph natively, so USDC withdrawals land directly on your agent's Morph Mainnet address — no L1↔L2 bridging required.

1. Sign up or log in to Bitget.
2. Buy USDC on the Bitget spot market.
3. Withdraw → pick Morph Mainnet as the network → paste your agent EOA address → confirm. The withdrawal will show up on the Morph explorer once it settles.

Or bridge from L1

• Bridge: https://bridge.morphl2.io
• Payment token: USDC (Bridged Standard) at 0xCfb1186F4e93D60E60a8bDd997427D1F33bc372B · 6 decimals
• Explorer: https://explorer.morphl2.io

You also need a tiny amount of ETH on Morph Mainnet for gas if the facilitator falls back to a user-signed settlement path — the official relayer normally sponsors gas, but having $0.10 of ETH bridged is good hygiene.

How much per call?

Five keywords + one country + shallow trail ≈ $0.10. Always quote the exact charge from pricing.estimatedTotal returned by sniffy_quote — the breakdown above is the source-of-truth recipe, not a fixed total.

The same key works across all three Sniffy surfaces.

MCP

Add it to the host config you set up in the Setup MCP guide:

{
  "mcpServers": {
    "sniffy": {
      "command": "npx",
      "args": ["-y", "@gosniffy/mcp"],
      "env": {
        "SNIFFY_PRIVATE_KEY": "0x...your fresh key..."
      }
    }
  }
}

CLI

export SNIFFY_PRIVATE_KEY=0x...your fresh key...
npx @gosniffy/cli diagnose --app 1234567890 --keywords "pickleball,tracker"

SDK

import { createSniffy } from "@gosniffy/sdk";
import { privateKeyToAccount } from "viem/accounts";

const sniffy = createSniffy({
  signer: privateKeyToAccount(process.env.SNIFFY_PRIVATE_KEY as `0x${string}`),
});

const quote = await sniffy.quote({ store: "ios", app: "1234567890", country: "US", keywords: ["pickleball"] });
const report = await sniffy.diagnose({ ...quote.input, sniffId: quote.sniffId });

The signature is an EIP-3009 transferWithAuthorization — a one-time, off-chain authorization for a specific (from, to, value, validAfter, validBefore, nonce) tuple. It is not a generic ERC-20 approval.

• value is in atomic token units (USDC: 6 decimals → 50000 = $0.05). The SDK does the unit math.
• nonce is a random 32-byte hex string — scopes the signature to a single call, prevents replay.
• The facilitator can't pull more than value with this signature. If you ever see a UI asking you to approve unlimited spend, you're on the wrong endpoint.