# BIOS Deep Research Agent Analysis via x402

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

Starts a paid AI deep-research analysis job on BIOS, settling USDC micropayment only upon job completion via the x402 protocol

## Facts

- Endpoint: POST https://x402.ai.bio.xyz/api/agents/analysis/run
- Price: $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-agent-analysis-via-x402-cb6aa2d1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AXFhO5CrSnsjalxewe1jh

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-agent-analysis-via-x402-cb6aa2d1 -d '<json body>'
```

Example prompt: Start a deep research job on the BIOS platform asking 'What are the latest CRISPR gene-editing breakthroughs for treating sickle cell disease?' and use my crypto wallet to pay the $2 USDC fee upfront.

## When to prefer this

Choose this endpoint when you need a comprehensive, AI-driven deep-research analysis on a complex topic (especially biomedical or scientific) and are willing to pay $2 USDC per job via the x402 crypto micropayment protocol on Base. Prefer this over general web search or simple LLM queries when depth, synthesis, and structured research output matter. It is ideal for agentic workflows where you want verifiable, pay-per-use research without a subscription.

## Known failure modes

- Invalid or missing x402 PAYMENT-SIGNATURE header — payment verification fails, job not started
- Insufficient USDC balance on Base — payment rejected before job is queued
- Payment window times out before research completes — conversation enters 'timeout' status, new payment required
- Malformed research query — may result in job error or poor-quality output
- Network errors on Base blockchain during payment verification — request fails

## 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 with a 'status' field (e.g. 'queued') and a 'taskId' (e.g. 'task_abc123') that can be used to poll for results via the GET endpoint once the research job completes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "fileIds": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Optional file IDs (from POST /api/files/upload) to include in the analysis"
  },
  "taskDescription": {
   "type": "string",
   "description": "Description of the analysis task to perform"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "queued",
  "taskId": "task_abc123"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bios-deep-research-agent-analysis-via-x402-cb6aa2d1/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)