# Extendivo Safe Fetch Secure

> Extendivo Safe Fetch Secure is a paid API for AI agents from api.extendivo.com, paid per call via x402, $0.015/call, status unknown (last checked 2026-11-03).

Fetches a public URL via POST/PUT/PATCH with SSRF protection, clean content extraction, and semantic prompt-injection detection

## Facts

- Endpoint: POST https://api.extendivo.com/v1/safe-fetch-secure?utm_source=zero.xyz
- Price: $0.015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/extendivo-safe-fetch-secure-cf00c95e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WZo37woJzjdfeQWcwMQnL

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 extendivo-safe-fetch-secure-cf00c95e -d '<json body>'
```

Example prompt: Can you safely fetch this external URL using a POST request with a JSON body containing the search parameters, and check it for any prompt injection attempts before I use the response in my pipeline?

## When to prefer this

Choose this endpoint when your agent needs to make outbound POST/PUT/PATCH requests to external URLs and you need both SSRF protection (preventing server-side request forgery to internal infrastructure) AND semantic prompt-injection analysis of the response — making it ideal for agentic pipelines where untrusted third-party content could be fed back into an LLM. Prefer this over a plain fetch when the fetched content will be consumed by an AI model, especially in multi-agent workflows where a malicious response could hijack agent behavior.

## Known failure modes

- SSRF violation: target URL resolves to an internal/private IP range — request blocked
- Prompt injection detected: response flagged as containing semantic injection content
- Invalid method: only POST, PUT, PATCH are accepted — GET requests are rejected
- Malformed body: body type does not match actual body content
- Unreachable target: URL returns network error or timeout
- Unsupported URL scheme: non-HTTP/HTTPS URLs rejected

## How this service works

Fetch a public URL with SSRF protection, clean extraction, and semantic prompt-injection analysis.

## Output

Returns the fetched URL's extracted clean content along with SSRF protection status (confirming the URL was safe to access) and a semantic prompt-injection analysis indicating whether the response content contains any injection attempts that could hijack downstream agent behavior.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/extendivo-safe-fetch-secure-cf00c95e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.extendivo.com](https://www.zero.xyz/host/api.extendivo.com/llms.txt)
