# BIOS Deep Research Job Starter (x402)

> BIOS Deep Research Job Starter (x402) is a paid API for AI agents from x402.ai.bio.xyz, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-14).

Initiates a paid deep research job via the BIOS API, verifying a USDC micro-payment upfront and queuing the research task for asynchronous completion.

## Facts

- Endpoint: POST https://x402.ai.bio.xyz/api/deep-research/start
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bios-deep-research-job-starter-x402-7a6c3e82
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Pdp6bxH7tpHNrS4fqMrg_

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 bios-deep-research-job-starter-x402-7a6c3e82 -d '<json body>'
```

Example prompt: Start a BIOS deep research job on the latest CRISPR gene-editing breakthroughs in cancer therapy — I'll pay the 0.2 USDC fee upfront and then poll for results once it's done.

## When to prefer this

Choose this endpoint when you need to programmatically kick off a long-running, AI-powered deep research task from the BIOS platform and are able to pay via USDC on Base using the x402 protocol. It is ideal for agentic workflows where asynchronous job queuing is acceptable and crypto-native micropayments are preferred over traditional API keys or subscriptions. Prefer it over synchronous research APIs when the depth and quality of BIOS research output justifies a short wait and per-query payment model.

## Known failure modes

- Invalid or missing x402 PAYMENT-SIGNATURE header — payment verification fails and job is rejected
- Insufficient USDC balance or malformed payment — 402 Payment Required error returned
- Payment window expires before job completion — conversation enters 'timeout' status requiring a new payment
- Malformed request body or missing research query — 400 Bad Request
- Network or Base chain issues causing payment verification to fail
- Research job fails internally — status may never transition from 'queued'

## How this service works

Payment proxy for the BIOS Deep Research API, powered by the x402 protocol.

This service wraps the BIOS deep-research endpoints with crypto micro-payments using USDC on Base. Payments are verified upfront but only settled once the research job completes.

## How it works

1. **Start a research job** — `POST /api/deep-research/start` with an x402 `PAYMENT-SIGNATURE` header. The payment is verified but not settled yet.
2. **Poll for results** — `GET /api/deep-research/{conversationId}` with an `X-SIWX` header (SIWE wallet signature). Only the wallet that paid can access results.
3. **On-demand settlement** — When polling a completed job, the payment is settled immediately and results returned. A background cron also handles batch settlement.
4. **Timeout handling** — If the payment window expires before completion, the conversation enters `timeout` status. A new payment is required to retrieve results.

## SIWX Authentication (Sign-In With X)

The `GET /api/deep-research/{conversationId}` endpoint requires wallet-based authentication via EIP-4361 (SIWE). When called without a valid `X-SIWX` header, the endpoint returns `401` with a SIWE challenge. The client must sign this challenge with the same wallet that made the original payment and resend the request.

The `X-SIWX` header is a base64-encoded JSON object: `{ "message": "<EIP-4361 message>", "signature": "0x..." }`.

## x402 Payment Protocol

All paid endpoints return `402 Payment Required` with a `PAYMENT-REQUIRED` header when no payment is provided. The header contains the payment requirements (price, token, network) that clients use to construct a payment.

See [x402 docs](https://docs.cdp.coinbase.com/x402/core-concepts/how-it-works) for details.

## Output

Returns a JSON object containing a job status of 'queued' and a unique conversationId (e.g. 'conv_abc123') that can be used to poll for results via the GET endpoint once the research job completes.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "queued",
  "conversationId": "conv_abc123"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bios-deep-research-job-starter-x402-7a6c3e82/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.ai.bio.xyz](https://www.zero.xyz/host/x402.ai.bio.xyz/llms.txt)