> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/09-11-2026-x402-one-request-per-wallet.md).

# 09-11-2026: x402 Search and Agent Endpoints Run One Request per Wallet at a Time

Requests paid with x402 on `/api/v1/search/web-fetch`, `/api/v1/search/web-search`, `/api/v1/agent/fast` and `/api/v1/agent/expert` now allow one request in progress per wallet. A second request from the same wallet while the first is still running returns HTTP 429 with `"code": "rate_limit_exceeded"`, `"reason": "payer_request_in_flight"`, `"charged": false` and a `Retry-After` header, and is not charged. Send these calls one after another, or pay from separate wallets to run them in parallel. If the per-wallet check is briefly unavailable, these endpoints return HTTP 503 with `"reason": "payer_lease_unavailable"`, `"charged": false` and a `Retry-After` header, and the request is not charged.

x402 payments on EVM networks, such as Base and Monad, now need an authorization that is still valid for at least 150 seconds once the payment has been verified, with its expiry written as a decimal integer of unix seconds. Standard x402 clients sign for the advertised `maxTimeoutSeconds` of 300 seconds and are not affected. Other authorizations return HTTP 402 with `invalidReason` set to `authorization_window_too_short` or `authorization_deadline_unreadable`, before any work is done, and are not charged.

`/api/v1/agent/fast` and `/api/v1/agent/expert` now advertise a `maxTimeoutSeconds` of 900 seconds for x402 payments. On EVM networks their authorization must still be valid for at least 600 seconds once verified, and a paid agent run is stopped 90 seconds before its authorization expires (at most 810 seconds after verification), ending with an `error` event (`"status_code": 504`) instead of `finish`. A run stopped this way is charged.

Requests made with an API key are unchanged. x402 requests on other endpoints are unchanged apart from the authorization validity rule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/api/changelog/09-11-2026-x402-one-request-per-wallet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
