# WURK API - Base 10 X Bookmarks (x402)

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

Creates a paid WURK job that delivers 10 bookmarks to a specified X (Twitter) post, settled via x402 micropayment on Base network.

## Facts

- Endpoint: GET https://wurkapi.fun/api/x402/quick/base/xbookmarks-10
- Price: $0.250000/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-10-x-bookmarks-x402-896c25d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eEnhqr2kgAK6BuMUr77mw

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-10-x-bookmarks-x402-896c25d6
```

Example prompt: Use WURK to add 10 bookmarks to this tweet: https://x.com/example/status/123456789 — pay with USDC on Base via x402.

## When to prefer this

Use this endpoint when you want to deliver exactly 10 bookmarks to an X (Twitter) post using a USDC micropayment on the Base network via the x402 protocol. Prefer this over Solana variants when Base is the target chain, and over the 20-bookmark variant when a smaller, cheaper boost is sufficient.

## Known failure modes

- Payment not confirmed — ok/paid returns false, job not created
- Invalid or malformed X post URL — request rejected
- x402 payment flow fails or times out — no job created
- Network congestion on Base causing payment settlement delay

## How this service works

Base 10 X Bookmarks

## Output

Returns a JSON object confirming payment and job creation, including a boolean 'ok' (true if successful), the job kind ('xbookmarks-10'), a unique jobId for tracking, and the network ('base') where the job is running.

## Example request

```json
{
 "url": "https://x.com/example/status/1234567890123456789"
}
```

## 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-10)."
 },
 "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-10-x-bookmarks-x402-896c25d6/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)