# GEDX402 Firecrawl – Crawl Params Preview

> GEDX402 Firecrawl – Crawl Params Preview is a paid API for AI agents from browser.gedx402.com, paid per call via x402, $0.018/call, status unknown (last checked 2026-09-13).

Preview and validate the parameters that would be used for a Firecrawl crawl job before executing it

## Facts

- Endpoint: GET https://browser.gedx402.com/v1/firecrawl/crawl/params-preview
- Price: $0.018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gedx402-firecrawl-crawl-params-preview-4e4235b9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZBGg-Wf4eU27MQABfYl3w

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-firecrawl-crawl-params-preview-4e4235b9
```

Example prompt: Before I kick off that crawl, can you show me a preview of the crawl parameters that Firecrawl would use — I want to make sure the config looks right without actually starting the job?

## When to prefer this

Use this endpoint when you need to validate or inspect crawl parameters before committing to a full crawl job. It is a cheap dry-run step ($0.018 USDC) that lets you confirm configuration correctness before invoking more expensive crawl or batch operations on the same service.

## Known failure modes

- Invalid parameter types return 400 error
- Missing required fields in request body cause validation failure
- Payment not processed (402) if x402 payment header is absent or insufficient
- Malformed messages array causes request rejection
- Service unavailable returns 503

## How this service works

Firecrawl v2 on x402 — scrape, search, crawl, map, batch, extract, agent, parse, interact, monitor at /v1/firecrawl/*.

## Output

Returns a JSON object showing the resolved crawl parameters and configuration that would be applied if a crawl job were actually executed, allowing the agent to inspect settings before committing to the full crawl operation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "messages": {
   "type": "array",
   "items": {
    "type": "object"
   }
  },
  "max_tokens": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "model": "firecrawl",
  "response": "Hello!"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gedx402-firecrawl-crawl-params-preview-4e4235b9/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)