# WURK API - Base 25 X Reposts

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

Triggers 25 reposts on a given X (Twitter) post via the WURK platform, paid with USDC micropayments over x402 on Base network.

## Facts

- Endpoint: GET https://wurkapi.fun/api/x402/quick/base/reposts-25
- Price: $0.625/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-25-x-reposts-6330ebd6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_53a3MTyMqLAXxHRa4J5l3

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-25-x-reposts-6330ebd6
```

Example prompt: Can you get 25 reposts on my X post at https://x.com/myaccount/status/1234567890 using WURK?

## When to prefer this

Choose this endpoint when you need exactly 25 reposts on an X (Twitter) post, paid via USDC micropayment on the Base network. Prefer this over the Solana variant if you are operating on Base, and over other repost tiers (e.g. 100 likes, 20 bookmarks) when reposts specifically are the desired engagement type.

## Known failure modes

- Invalid or missing X post URL returns an error
- Payment not confirmed via x402 protocol results in job not being created
- X post URL is inaccessible or deleted, leading to job failure
- Network issues on Base may delay job creation confirmation
- Insufficient USDC balance to cover the $0.625 per-call fee

## How this service works

Base 25 Reposts

## Output

Returns a JSON object confirming whether the payment was accepted and the quick repost job was created, including the job ID, job kind ('reposts-25'), payment confirmation boolean, 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-25)."
 },
 "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-25-x-reposts-6330ebd6/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)