# Agentshelf EAN-13 Regex Extractor

> Agentshelf EAN-13 Regex Extractor is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Extracts up to 20 EAN-13 barcode digit strings from a provided text input using regex matching.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/regex-ean?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshelf-ean-13-regex-extractor-89e03372
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZMlsNRUJlsC5maccwhlhO

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 agentshelf-ean-13-regex-extractor-89e03372 -d '<json body>'
```

Example prompt: Scan this product catalog text and pull out all the EAN-13 barcodes you can find — I need the list of 13-digit codes: 'Product: Widget A 4006381333931, Widget B 5901234123457, Widget C 9780201379624'

## When to prefer this

Use this endpoint when you need to reliably extract EAN-13 barcode digit sequences from arbitrary text without running your own regex logic. It is preferable when operating in environments where you cannot execute code locally, or when you want a deterministic, hosted, paid-access barcode extraction service. For testing or development, prefer the unpaid sandbox endpoint POST /v1/sandbox/regex-ean first to avoid unnecessary charges. Do not use if you need UPC-A, QR, or other barcode formats.

## Known failure modes

- Empty match list returned when no EAN-13 codes are present in the text (still billed $0.01 USDC)
- Input text exceeds 100,000 character limit causing request rejection
- Payment of $0.01 USDC not provided or fails, resulting in 402 error
- Malformed or missing 'text' field in request body causes validation error
- Strings resembling but not conforming to 13-digit EAN-13 format are not matched

## How this service works

Call when an agent needs EAN-13 digit strings extracted from text, capped at 20 matches. An empty match list is billed. No network. Exact $0.01 USDC. Prefer unpaid POST /v1/sandbox/regex-ean first.

## Output

A list of up to 20 EAN-13 digit strings matched within the submitted text. An empty list is returned (and billed) if no matches are found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "examples": [
    "4006381333931"
   ],
   "maxLength": 100000,
   "minLength": 1,
   "description": "Input for this SKU. The route description says whether it is plain text, a URL, base64 bytes, or an already-encoded token."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshelf-ean-13-regex-extractor-89e03372/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)