# WURK API - Base 50 X Bookmarks

> WURK API - Base 50 X Bookmarks is a paid API for AI agents from wurkapi.fun, paid per call via x402, $0.5/call, status unknown (last checked 2026-09-15).

Creates a quick job that delivers 50 bookmarks to a specified X (Twitter) post via USDC micropayment on Base network

## Facts

- Endpoint: GET https://wurkapi.fun/api/x402/quick/base/xbookmarks-50
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wurk-api-base-50-x-bookmarks-7325d52f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VrzDIdYIeS7YalIgHm7MH

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 wurk-api-base-50-x-bookmarks-7325d52f
```

Example prompt: Use WURK to add 50 bookmarks to this X post: https://x.com/username/status/1234567890 and pay with USDC on Base.

## When to prefer this

Use this endpoint when you need exactly 50 bookmarks on an X post and want to pay with USDC on the Base network. Prefer over the 20-bookmark or 100-bookmark variants when mid-tier engagement boost is needed at $0.50 per call. Choose Base network variant over Solana variant if operating in a Base/EVM ecosystem.

## Known failure modes

- Payment not confirmed — ok/paid returns false if USDC payment via x402 fails
- Invalid URL — malformed or non-X post URL causes job creation failure
- Insufficient funds — wallet lacks required 0.5 USDC on Base network
- Network congestion — Base network delays may slow payment confirmation
- Post unavailable — private, deleted, or restricted X posts may not accept bookmarks

## How this service works

Base 50 X Bookmarks

## Output

Returns a JSON object with ok (boolean confirming payment and job creation), kind ('xbookmarks-50'), paid (boolean alias for ok), jobId (internal WURK identifier for tracking), and network ('base'). The job then runs asynchronously to deliver 50 bookmarks to the target post.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "Link to the X (Twitter) post to bookmark."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "ok": {
  "type": "boolean",
  "description": "True when payment is confirmed and the quick job is created."
 },
 "kind": {
  "type": "string",
  "description": "Quick job kind (e.g., xbookmarks-50)."
 },
 "paid": {
  "type": "boolean",
  "description": "Alias for ok; kept for backwards compatibility."
 },
 "jobId": {
  "type": "string",
  "description": "Internal WURK job identifier that can be used with other job APIs."
 },
 "network": {
  "type": "string",
  "description": "Network where the job is running (e.g., base)."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/wurk-api-base-50-x-bookmarks-7325d52f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from wurkapi.fun](https://www.zero.xyz/host/wurkapi.fun/llms.txt)