You.com + Agent Safe: web search for agents, inside a budget

You.com serves LLM-ready web search to agents over x402, paid per query in USDC on Base. Agent Safe adds the guardrail people need before leaving an agent running: payments go only to You.com's address, never above your per-call cap, never past the budget, whatever the agent was told.

Tested live on Base mainnet (2026-10-08): an agent paid You.com 0.005 USDC for GET /v1/search?query=base%20l2&count=5 and got five live web results for "base l2". Transaction. The same 402 checked against a different payee was refused with zero signatures.

1. Add You.com as a merchant

import { createAgentPay, MerchantRegistry } from "@deepfirstsearch/agent-pay";

const registry = new MerchantRegistry([{
  origin: "https://api.you.com",
  payTo: "0xc327D0aEb5f65B514b193b5e5A95cC6F4060815f", // You.com's Base address, as in its 402
  network: "eip155:8453",
  maxPerTx: 10_000n, // never more than 0.01 USDC per call
  pricePin: 5_000n, // 0.005 USDC, the published price
  label: "You.com",
}]);

2. Pay per call

const pay = createAgentPay({
  registry,
  policy: { allowedNetworks: ["eip155:8453"], periodBudget: { amount: 1_000_000n, periodMs: 86_400_000 }, timeoutBounds: { min: 10, max: 600 } }, // You.com asks for 10-minute authorizations
  payer: () => yourWallet, // any viem account: local key, Turnkey, Privy, CDP, KMS
  session: { readsUntrustedInput: true, accessesSensitiveData: false, canPay: true },
});
const plan = pay.commitPlan([{ origin: "https://api.you.com", maxSpend: 100_000n }], 60 * 60_000);

const res = await pay.fetch("https://api.you.com/v1/search?query=base%20l2&count=5", { method: "GET" }, { plan });
console.log(res.status, res.payment?.settlement.transaction);

A 402 that asks for a different payee, a higher price or a different network is refused before anything is signed. Requires @deepfirstsearch/agent-pay 0.5.3 or later.

If You.com changes its price or address

The pins are deliberate. The 402 is written by the server, and a 402 that suddenly names another address or a higher price is exactly what a redirected or hijacked payment looks like. So when You.com reprices or rotates its wallet, Agent Safe refuses and nothing is signed:

• a higher price gives price_changed (action ask_owner), or over_cap if it is also above your per-call cap;
• a different address gives payee_mismatch (action report).

Confirm the change through You.com's own channels (its site, docs or announcement), then update pricePin or payTo in the registry, or price or payTo in the MCP config. To absorb small price changes without a prompt, allow a tolerance instead of removing the pin: toleranceBps in the registry (1000 = up to 10% over the pin) or tolerancePct in the MCP config.

Agent Safe is an independent open-source project (MIT), live on Base mainnet as an unaudited beta. Not affiliated with You.com.