# WURK API - Base 50 X Reposts

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

Triggers 50 reposts on a given X (Twitter) post via a micropayment-gated quick job on the Base network.

## Facts

- Endpoint: GET https://wurkapi.fun/api/x402/quick/base/reposts-50
- Price: $1.25/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-50-x-reposts-d4b34ed7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ER2othTKhdyO6o0r3Xgqr

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-reposts-d4b34ed7
```

Example prompt: Can you get 50 reposts on my X post at https://x.com/myhandle/status/1234567890 using WURK — charge it to my Base USDC wallet.

## When to prefer this

Use this endpoint when you specifically need exactly 50 reposts on an X (Twitter) post, paid via USDC on the Base network through x402 micropayment. Prefer it over Solana-based sibling endpoints if you are operating on Base. Choose the 50-repost tier when you want moderate amplification at $1.25 USDC rather than smaller (10-20) or larger (100+) packages.

## Known failure modes

- Payment not confirmed — returns ok: false and paid: false if x402 micropayment fails
- Invalid or inaccessible X post URL — job may be created but fail to execute reposts
- Network congestion on Base causing delayed job creation
- URL parameter missing — returns validation error
- Duplicate calls may create multiple jobs and charge multiple times

## How this service works

Base 50 Reposts

## Output

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

## Request schema (JSON Schema)

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

## 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., reposts-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-reposts-d4b34ed7/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)