# WURK API - Base 100 X Likes

> WURK API - Base 100 X Likes is a paid API for AI agents from wurkapi.fun, paid per call via x402, $2.5/call, status unknown (last checked 2026-09-14).

Triggers a paid WURK job to deliver 100 likes on a specified X (Twitter) post, settled via x402 micropayment on Base network in USDC.

## Facts

- Endpoint: GET https://wurkapi.fun/api/x402/quick/base/xlikes-100
- Price: $2.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wurk-api-base-100-x-likes-b4b79ac3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4EOv2R9ao2-jBmu8QRwEE

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-100-x-likes-b4b79ac3
```

Example prompt: Get me 100 likes on this X post — https://x.com/example/status/123456789 — using WURK's Base network micropayment.

## When to prefer this

Use this endpoint when you want to deliver exactly 100 likes to a specific X (Twitter) post using a one-shot x402 micropayment on the Base network in USDC. Prefer this over Solana equivalents when operating on Base chain, and over the 50-likes variant when a larger like volume is needed in a single call.

## Known failure modes

- Payment not confirmed — returns ok: false if x402 payment settlement fails
- Invalid or malformed X post URL — job may not be created
- Post is private or deleted — job created but likes may not be deliverable
- Insufficient USDC balance for the $2.50 micropayment — payment rejected
- Network error on Base — transaction may time out

## How this service works

Base 100 X Likes

## Output

Returns a JSON object confirming payment and job creation, including: ok (boolean indicating success), kind (xlikes-100), paid (alias for ok), jobId (internal WURK job identifier for tracking), and network (base).

## Request schema (JSON Schema)

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

## 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., xlikes-100)."
 },
 "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-100-x-likes-b4b79ac3/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)