# DESK LEAD x402 – Desk Pack 50

> DESK LEAD x402 – Desk Pack 50 is a paid API for AI agents from desk-x402.desk-x402-gh.workers.dev, paid per call via x402, $50/call, status unknown (last checked 2026-09-15).

Returns a $50 USDC micropayment-gated research data pack (desk-pack-50) via x402 protocol, delivering a pin universe and product metadata upon successful on-chain payment.

## Facts

- Endpoint: GET https://desk-x402.desk-x402-gh.workers.dev/v1/desk-pack-50
- Price: $50/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/desk-lead-x402-desk-pack-50-f63583a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_szxAAkghjEwK_D-BJKqv2

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 desk-lead-x402-desk-pack-50-f63583a9
```

Example prompt: Fetch me the desk-pack-50 research bundle from DESK LEAD — I want to pay the $50 USDC via x402 on Base network and get back the pin universe data.

## When to prefer this

Choose this endpoint when an agent needs to access the DESK LEAD desk-pack-50 research data bundle and is prepared to execute a $50 USDC micropayment via the x402 v2 protocol on the Base blockchain. Prefer this over free or lower-tier endpoints when the full pin_universe dataset is required. Use this over legacy v1 endpoints when transacting strictly on Base (eip155:8453).

## Known failure modes

- Payment not provided or invalid — returns 402 Payment Required
- Wrong network used (not Base eip155:8453 for v2) — payment rejected
- Invalid X-PAYMENT-TX or PAYMENT-SIGNATURE header — authentication failure
- Insufficient USDC balance — transaction fails on-chain
- Legacy BSC/Base v1 payment attempted on v2 endpoint — network mismatch error
- Malformed payment header format — 400 Bad Request

## How this service works

Micropay research APIs (x402 v2 + bazaar). Free catalog at /.well-known/x402.json. Primary v2 accepts: Base eip155:8453 only. Legacy X-PAYMENT-TX still supports bsc|base via acceptsV1. Headers: X-PAYMENT-TX, X-PAYMENT-NETWORK, PAYMENT-SIGNATURE. No financial advice.

## Output

Returns a JSON object with ok:true, tier set to 'pack-50', product identifier 'desk_pack_50', priceUsdc of 50, and a pin_universe object containing the research dataset unlocked by the micropayment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tier": "pack-50",
  "product": "desk_pack_50",
  "priceUsdc": 50,
  "pin_universe": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/desk-lead-x402-desk-pack-50-f63583a9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from desk-x402.desk-x402-gh.workers.dev](https://www.zero.xyz/host/desk-x402.desk-x402-gh.workers.dev/llms.txt)