> For clean Markdown of any page, append `.md` to the page URL.
> Documentation index: https://you.com/docs/llms.txt (section indexes: append `/llms.txt` to any section URL).
> Search these docs: Docs MCP at https://you.com/docs/_mcp/server (`searchDocs`, no API key).
> Call live You.com APIs: Product MCP at https://api.you.com/mcp (keyless `?profile=free` exposes `you-search` and `you-discover`. Research and finance use `/mcp/research`, `/mcp/finance`, or `?tools=` on `/mcp`). To pick an API or integration path, call `you-discover` on that server instead of guessing.
> OpenAPI: https://you.com/docs/openapi.json—auth header `X-API-Key`, env `YDC_API_KEY`.

## Machine Payments for the Web Search and Finance Research APIs

`GET /v1/search` and `POST /v1/finance_research` now accept machine payments, so an agent with a funded wallet can call either one without an API key, an account, or a prepaid credit balance. Payment settles inside the same HTTP exchange that requests the data.

Two protocols are advertised on both routes, and a single unpaid request returns terms for each:

| Endpoint                       | x402, USDC on Base or Solana | MPP, USDC on Tempo |
| ------------------------------ | ---------------------------- | ------------------ |
| Web Search                     | \$0.005                      | \$0.01             |
| Finance Research, `deep`       | \$0.11                       | \$0.11             |
| Finance Research, `exhaustive` | \$0.50                       | \$0.50             |

Both protocols match the standard credit prices. They diverge on Web Search only, because MPP settles through Stripe, where one cent is the smallest chargeable amount, so a half-cent call rounds up. Adding `livecrawl` raises the Web Search quote by \$0.001 per result on both protocols.

Watch the HTTP method. Each endpoint offers terms on one verb, and the other returns `401` — Web Search on GET, Finance Research on POST. [Zero Data Retention](/docs/administration/zero-data-retention) does not apply to keyless requests, since it is enforced against a specific organization's API keys and these requests carry no account.

Read the machine payments overview

## Machine Payments on /v1/agents/search

The agent search endpoint, `/v1/agents/search`, accepts machine payments on both GET and POST, with the same pricing as `/v1/search`. Send a payment header to trigger the `402` challenge and settle the call through [x402](/docs/administration/machine-payments/x402) or [MPP](/docs/administration/machine-payments/mpp).

x402 gating is endpoint-scoped, not method-scoped: when x402 is enabled for an endpoint, it is available on every method that endpoint offers for machine payments. That is why `/v1/agents/search` accepts x402 on both verbs while `/v1/search` accepts it on GET only.

The full endpoint and method table is on the [Machine Payments overview](/docs/administration/machine-payments#supported-endpoints).

Read the machine payments overview