# GEDX402 Browser Outcome Persist

> GEDX402 Browser Outcome Persist is a paid API for AI agents from browser.gedx402.com, paid per call via x402, $0.24/call, status unknown (last checked 2026-09-16).

Loads a URL in a headless browser, extracts content using a named recipe, persists the result to cloud storage, and returns a stable retrieval URL

## Facts

- Endpoint: GET https://browser.gedx402.com/v1/browser/outcome/persist
- Price: $0.24/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gedx402-browser-outcome-persist-6314eefc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NmjCvhFiOSDnxk8zDwHgW

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 gedx402-browser-outcome-persist-6314eefc
```

Example prompt: Load https://techcrunch.com/2024/05/10/openai-gpt-update/ in a headless browser, extract the article as markdown, and save it to storage so I have a persistent link I can retrieve later.

## When to prefer this

Use this endpoint when you need to both extract web content AND persist it durably for later retrieval — the key differentiator is the automatic cloud storage step that returns a stable get_url, making it ideal for pipelines that need to reference extracted content later. Prefer over ephemeral scrape-only endpoints when downstream steps need a stable file URL. Choose the 'article' recipe for news/blog pages and 'product' for e-commerce listings.

## Known failure modes

- Invalid or unreachable URL returns an error response
- Non-HTTPS URL rejected by schema validation
- Unsupported recipe value (not article or product) causes validation failure
- Payment not received or insufficient USDC causes 402 rejection
- Page load timeout if the target URL is slow to respond
- R2 storage write failure prevents persistence and get_url generation

## How this service works

Extract & persist — one x402 payment extracts article or product from a URL, persists markdown to artifact storage, and returns { key, get_url, markdown }. POST { url, recipe: article|product, key? } on browser.gedx402.com. x402 settlement $0.24. Hero: GET /heroes/extract-persist.

## Output

A JSON object containing: the R2 storage key under which the result was persisted, the recipe used (article or product), a direct HTTPS get_url for retrieving the stored file from storage.gedx402.com, and the extracted markdown content of the page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string"
  },
  "url": {
   "type": "string"
  },
  "recipe": {
   "enum": [
    "article",
    "product"
   ],
   "type": "string"
  },
  "options": {
   "type": "object",
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gedx402-browser-outcome-persist-6314eefc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from browser.gedx402.com](https://www.zero.xyz/host/browser.gedx402.com/llms.txt)