# Zenrows PUT Request Proxy

> Zenrows PUT Request Proxy is a paid API for AI agents from agents.zenrows.com, paid per call via MPP, price unknown, status unknown (last checked 2026-10-16).

Send an HTTP PUT request to any target URL through Zenrows's anti-bot proxy infrastructure, forwarding the request body and returning the target's response.

## Facts

- Endpoint: PUT https://agents.zenrows.com/v1/?utm_source=zero.xyz
- Price: price unknown
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Provider: agents.zenrows.com
- Website: https://agents.zenrows.com
- Canonical page: https://www.zero.xyz/c/agents-zenrows-com-zenrows-put-request-proxy-b95a0130
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uKEwxrliX5OuEXamfsJfn

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agents-zenrows-com-zenrows-put-request-proxy-b95a0130 -d '<json body>'
```

Example prompt: Send a PUT request to https://api.example.com/resources/42 with the body '{"status":"active"}' through Zenrows using a premium residential proxy routed through Germany, and show me the response.

## When to prefer this

Choose this endpoint when you need to send an HTTP PUT request (not GET or POST) to a target URL that may be behind anti-bot systems, JavaScript rendering requirements, or geo-restrictions. Prefer it over direct PUT calls when the target blocks automated clients or when you need residential proxy routing, session stickiness, or custom country exit nodes. Use GET-based fetchPage for read-only retrieval, and the POST endpoint for POST-method interactions.

## Known failure modes

- Target URL is unreachable or returns a non-2xx status — original status code forwarded if original_status is set
- Anti-bot protection not bypassed even with premium proxy — request fails and no credits charged
- Invalid or missing API key — authentication error returned
- Malformed request body rejected by the target server — target error response returned
- JavaScript rendering timeout if js_render is enabled and page is slow
- Invalid proxy_country code — parameter validation error

## How this service works

Send a PUT to the target through Zenrows. Takes the same query parameters as fetchPage; the request body is forwarded to the target as is, and the response carries the target's content.

## Output

The response body returned by the target server after receiving the PUT request, delivered as HTML, Markdown, plain text, structured JSON, or a screenshot depending on configured output options. The envelope may also include captured network requests if that option is enabled.

## Request schema (JSON Schema)

```json
{}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "Structured output: the extracted fields, the autoparsed record, or the JSON envelope with captured network requests.",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-zenrows-com-zenrows-put-request-proxy-b95a0130/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.zenrows.com](https://www.zero.xyz/host/agents.zenrows.com/llms.txt)