# x402 Micro Pay — Keyword Extraction

> x402 Micro Pay — Keyword Extraction is a paid API for AI agents from x402-micro-pay.com, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-13).

Extracts keywords from a given text input via a pay-per-call HTTP microservice using x402/USDC micropayments.

## Facts

- Endpoint: POST https://x402-micro-pay.com/api/skills/keyword-extract?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-micro-pay-keyword-extraction-ea2c31f0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J2dFMoz9eVbxHj0mcVED5

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 x402-micro-pay-keyword-extraction-ea2c31f0 -d '<json body>'
```

Example prompt: Can you extract the main keywords from this product description: 'Lightweight running shoes with breathable mesh upper, responsive foam midsole, and durable rubber outsole, ideal for road and trail running'?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call keyword extraction service that works natively with AI agent workflows and x402 micropayment rails. Ideal when you want zero subscription overhead and only pay $0.008 USDC per extraction. Best for agents that process variable volumes of text and need on-demand NLP without managing API keys or monthly quotas.

## Known failure modes

- Payment not included or insufficient USDC balance — 402 Payment Required returned
- Malformed request body missing required 'type' or 'method' fields — 400 Bad Request
- Empty or null input text — may return empty keyword list or validation error
- Network timeout or service unavailability — 503 or connection error
- Unsupported bodyType field value — unexpected parsing behavior

## How this service works

Agent-ready microservices with x402 + Stripe rails, volume primitives, tutorials, and applet UI.

## Output

A JSON response containing extracted keywords or key phrases from the submitted text, along with a success status flag and the request path. The response follows the format {ok: true, path: '/api/skills/keyword-extract'} plus the keyword payload.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string"
  },
  "limit": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "path": "/api/skills/keyword-extract"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-micro-pay-keyword-extraction-ea2c31f0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-micro-pay.com](https://www.zero.xyz/host/x402-micro-pay.com/llms.txt)